TRADACOMSDeenvelope Business Process

Edit online

The TRADACOMS Deenvelope business process includes the Generic Deenveloping service to support non-printable characters as EDI delimiters and perform the following steps:

Puts delimiters sent in the message into process data.
Starts the TRADACOMS Enveloping or TRADACOMS Deenveloping business processes, as appropriate.

If exceptions occur when running a TRADACOMS Deenvelope business process, Sterling B2B Integrator generates an EDI Compliance Report.

This table lists the configuration parameters for the TRADACOMSDeenvelope business process:

Parameter	Default	Description
Document Tracking	False	When document tracking is enabled for a business process, tracking information is carried with the message throughout the process, and the tracking information is persisted about the message regardless of the persistence level you configured globally for Sterling B2B Integrator.
Set onfault processing	False	Onfault processing allows the process to immediately execute Sterling B2B Integrator fault activity specified in the process, even if the process has not yet reached that step in the process. For example, if a process fails at step 3, but the on-fault activity is specified in step 7, if onfault processing is enabled, the process proceeds to the step 7 on-fault rather than halting at step 3.
Set Queue	4	Sterling B2B Integrator enables you to set performance optimizations by queue, defining queue levels to allocate resources. This number indicates the previously allocated queue level that you selected for this business process model for processing.
Use BP Queuing (recommended)	True	Enable business processes to execute in a sequence. It is possible to queue business processes such that one executes after one business process ends.
Enable Transaction	False	This option instructs Sterling B2B Integrator to treat the entire process as a single transaction so that either all of the steps complete, or, in the event of an error, none of them complete. When an error occurs, no data is committed; data returns to its pre-process state. By default, this transaction mode is not enabled.
Commit All steps when there is error	False	This option enables you to have the business process commit all work to the database, at the time an error is generated. With this option you can either rollback or commit all work prior to the error before the onfault block is called.
Category	N/A	A category name to which this business process belongs.
Set the Persistence Level to	Full	The level of data to retain for generating a status report that describes each step that the business process completes. System default indicates that, for the data, configuration is already defined in Sterling B2B Integrator to retain data.
Set the Event Reporting Level to	None	The level of event reporting that is retrieved for this business process when it runs. Full specifies to generate events for the business process, including the business process start and end time, start and end times for all services or services running as a result of this business process, and any resulting errors and exceptions.
Set the Recovery Level to	Manual	The level of recovery for this business process if the business process should halt during execution. Manual requires you to resume or restart the business process manually.
Set the Document Storage to	System Default	The level of document storage for messages that process when the business process runs. System Default specifies to store messages in the file system or database, according to how you configured archiving and purging in Sterling B2B Integrator.
Deadline Settings	Do not set deadline Note: To set a deadline you must change it in the business process.	Complete by – The deadline time, in hours and minutes, by which the business process must complete process once it starts. First Notification: Hours and Minutes – Whether to receive notification before a business process deadline. Second Notification: Hours and Minutes – Whether to receive another notification before a business process deadline.
Life Span	System Default	The length of time, in days and hours, to retain the data in Sterling B2B Integrator, along with the life span type and removal method. If you select Process Specific, then you can select the number of days and hours for the life span. Also, you can select if you want Sterling B2B Integrator to archive or purge a business process after its life span is over.

The following BPML code makes up the TRADACOMSDeenvelope business process:


<process name="TRADACOMSDeenvelope">

  <rule name="contract">
    <condition>CONTRACT_FOUND = "YES"</condition>
  </rule>

  <sequence>
   <sequence>
    <operation>
      <participant name="DeenvelopeGeneric" />
      <output message="Xout" >
        <assign to="map_name">TRADACOMS_Deenvelope</assign>
        <assign to="." from="*"></assign>
      </output>
      <input message="Xin" >
        <assign to="." from="*"></assign>
      </input>
    </operation>
    <onFault code="Interchange-Non-Compliant">
      <!-- Just catch the error, so that the BP will continue. -->
      <!-- Dummy assign, since we need something here. -->
      <assign to="BREAK">YES</assign>
    </onFault>
    <onFault code="Transaction-Non-Compliant">
      <!-- Just catch the error, so that the BP will continue. -->
      <!-- Dummy assign, since we need something here. -->
      <assign to="BREAK">YES</assign>
    </onFault>
    <onFault>
      <operation>
        <participant name="BPExceptionService"/>
        <output message="Xout" >
          <assign to="exceptionCode" from="Prev_NotSuccess_Adv_Status/text()"/>
        </output>
        <input message="Xin"/>
      </operation>
    </onFault>
   </sequence>
    <choice>
      <select>
        <case ref="contract" activity="invoke_contract_workflow" />
      </select>
      <sequence name="invoke_contract_workflow">
        <operation>
          <participant name="InvokeBusinessProcessService" />
          <output message="Xout">
            <assign to="INVOKE_MODE">ASYNC</assign>
            <assign to="." from="*"></assign>
          </output>
          <input message="Xin" >
            <assign to="." from="*"></assign>
          </input>
        </operation>
      </sequence>
    </choice>

  </sequence>
</process>

The following scenario shows how the TRADACOMSDeenvelope business process can deenvelope TRADACOMS documents:

The File System adapter collects a file from a TRADACOMS collection folder and invokes the EDIDeenvelope business process.
The EDI Deenvelope service determines that the file contains a TRADACOMS document and starts the TRADACOMSDeenvelope business process.
The TRADACOMSDeenvelope business process removes the envelopes to make available the transaction set envelope for the TRADACOMS document and determine the next action to perform.
Note: If the TRADACOMSDeenvelope business process does not locate a matching envelope, the business process stops. Sterling B2B Integrator generates an EDI Compliance Report that describes the reason that the TRADACOMSDeenvelope business process could not locate the envelope.

Before Using TRADACOMSDeenvelope

Before you use the TRADACOMSDeenvelope business process, you must complete the following tasks:

Create the trading profile, including a contract.
Create necessary envelopes.
Create a business process that initiates the TRADACOMSDeenvelope business processes.
When creating a business process that enables inbound STX envelopes to translate transactions when running TRADACOMSDeenvelope business processes, consider the following:
- Delimiters are placed into process data in Sterling B2B Integrator.
- The GPM makes available parameters that represent the delimiters, which you must configure to enable the envelopes to translate transaction.
- You must create an XPath expression that describes the location of envelopes and apply it to the Translation service.