CHIPSEnvelope Business Process

Edit online

The CHIPSEnvelope business process is initiated when it is called by another business process. The CHIPSEnvelope business process envelopes the CHIPS messages contained in the business process context with outbound CHIPS envelopes that you have preconfigured. You must have created one outbound CHIPS envelope for each CHIPS message that you are sending.

A typical scenario is one in which CHIPS data must be sent to the CHIPS Central Computer. The CHIPSEnvelope business process helps to provide these enveloping services.

The CHIPSEnvelope business process is initiated as part of the following outbound process flow:

You create a business process that calls the EDI Encoder service or Document Extraction service.
The EDI Encoder service or Document Extraction service looks up the envelope to apply and prepares the document to be enveloped.
Either the business process calls the EDI Enveloping service or the Document Extraction service is configured to perform enveloping.
The EDI Enveloping service or Document Extraction service starts the CHIPSEnvelope business process (which runs the Generic Envelope service as a subprocess to extract the name of the business process).
The CHIPSEnvelope business process searches the envelope definition to retrieve information to envelope each message.

This table lists the configuration parameters for the CHIPSEnvelope 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 the on-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.
Queue	4	Sterling B2B Integrator enables you to set performance optimizations by queue, defining queue levels to allocate resources. This number indicates that previously allocated queue level that you want for this business process model for processing.
Persistence Level	System Default	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.
Recovery Level	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.
Document Storage Type	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 inSterling B2B Integrator
Life Span	Life Span Days — 2 Life Span Hours — 0 Life Span Type — System Level Removal Method — Archive	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.
Complete by Deadline	None Available 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.
Event Reporting Level	Full	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 processes, and any resulting errors and exceptions.

The following BPML code makes up the CHIPSEnvelope business process:


<process name="CHIPSEnvelope">

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

  <sequence>
    <sequence>
      <operation>
        <participant name="EnvelopeGeneric" />
        <output message="Xout" >
          <assign to="." from="*"></assign>
        </output>
        <input message="Xin" >
          <assign to="." from="*"></assign>
        </input>
      </operation>
      <onFault code="Translation-Error-Some-Docs">
        <assign to="BREAK">YES</assign>
      </onFault>
      <onFault code="Envelope-Translation-Error-Some-Docs">
        <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>