SOA Compliance

As part of Service-Oriented Architecture (SOA), compliance can be integrated into ship shipment and create shipment messages. There is a compliance section at the bottom of these messages that triggers the workflow task Run Compliance (SOA), which contains details of the checks to run. Set up this task using the WF option in the Windows UI. The details are contained in SOA Compliance Task Fields. This task generally runs at the end of the process, so assign it a high sequence number.


Field	Run Compliance (SOA)
Task option	WFTCKR
Task program type	02
Program Parameters	Enter a semi-colon separated list of checks to run on the transaction. Each program parameter is then separated by a comma. For example, CHECKS=DPL;DATA-INTEG;EBC;ECLI;EXLI;KEY;CMKQ1,RESULT-TYPE=Complete,SET_TASK=CK_STAT,HIGHWAY_TARGET=SYNCH_IN,HIGHWAY_MESSAGE_ID=COMPLY_SYNCH,RESULT-TYPE=INTERMEDIATE To run all checks, enter: CHECKS=*ALL SET_TASK = Task Key ID identifies the task to set to indicate whether compliance passed or failed. HIGHWAY_TARGET=SYNCH_IN indicates which Highway endpoint to send the compliance XML request message to. HIGHWAY_MESSAGE_ID=COMPLY_SYNCH indicates the Highway message ID endpoint, which states that it is a synchronous message. RESULT-TYPE=INTERMEDIATE indicates the format of the response message containing compliance results. There are three possible formats for the compliance result message: • Short - Basic results of each check. • Intermediate - More detailed information on each check. • Complete - The intermediate check information plus a more detailed breakdown on the DPL check, including more information on percentages.
Task Type	Check
Repeatable task	Yes
Lock transaction	Yes