Process Input Payloads Structure

The structure of a payload that executes a component's Process method is shown below. The example is of a DaybookListing payload. For brevity, <ErrorContext>, <User> and <SunSystemsContext> are omitted:

<?xml version="1.0" encoding="UTF-8"?>
<SSC>
  <Payload>
      <Input>
          <DefinitiveRequest>1</DefinitiveRequest>
          <EntryDateFrom>01012004</EntryDateFrom>
          <EntryDateTo>01012004s</EntryDateTo>
          <Reprint>0</Reprint>
      </Input>
  </Payload>
</SSC>

The <Payload> element contains a single <Input> element. This is used to specify runtime parameters.

Remarque: Whether you are running the process from Transfer Desk, Automation Desk or Connect Portal, a component Process method must have a payload file as input. This is primarily so that the process can be (optionally) executed from Connect Portal. Connect Portal does not use a Transfer Desk Profile to hold the runtime parameters used to control the process, so the values must be present within the payload.