Business Process (object)

The Business Process (BP) object performs sequential tasks on your data in the CIC engine. Utilizing an internal document storage manager, this object temporarily holds data and then passes it between configurable tasks within a BP and throughout your integration.  Typical use cases include: 

• Manipulate data (strings and arrays)
• Import and export data
• Move or route data based on content
• Execute/launch other objects/resources that are part of your integrations (such as transformation Rulesets)
• Analyze documents
• Route envelopes

Sequencing, comparison, and iteration are the three main functions.

• Tasks execute one after the other (Sequencing).
• Results are defined in a comparison and then branched to alternate tasks (Comparison), or
  further used to activate/execute appropriate tasks or objects (including other BPs).
• Loop through data or repeating tasks (Iteration).

These functions allow the Business Process to handle processing flows as well as exceptions that occur. 

Creating, defining, and using in CIC Studio

The Business Process object is required for any transformation. It relates and activates in sequence all objects created for transformation. You will add objects (such as Cloud Monitor, Ruleset, etc.) to a Business Process, as well as any additional tasks used to manipulate data.

To use this object, you must:

• Create a Business Process.
• Add Tasks in its editor.
• Set parameters and define variables.
• Sequence the tasks.
• Create the method of execution.
  • Choose an Event, which can send data to a Business Process.
  • Execute a BP from another object such as a Ruleset or another Business Process.
  • Manually execute.

To create a Business Process:

1. Select File | New | Business Process from the main menu bar. <>

   Note: If you select the package in which the Business Process should reside before creating it, some parameters are automatically populated in the New Business Process window.

2. The New Business Process window appears. From the Templates section, choose a radio button to specify whether to use a template to create the new Business Process.

   

   Options are:

   • No Template: Creates a blank Business Process, with no initial parameters, variables, or tasks included. These will have to be added.
   • Inbound EDI Business Process: Creates a Business Process pre-populated with parameters and tasks designed to process inbound EDI documents.
   • Outbound EDI Business Process: Creates a Business Process pre-populated with parameters and tasks designed to process outbound EDI documents.
   • Application Route Business Process: Creates a Business Process with the parameters and tasks needed for application processing (non-EDI), and used in conjunction with a Data Analysis Ruleset.
   • Connection Business Process: Creates a Business Process pre-populated with parameters and tasks designed to output a complete, enveloped outbound EDI document. This type of Business Process is set in the EDI Enveloper object; that is, the Enveloper actually indicates the Connection Business Process to execute at runtime for each completed, enveloped EDI document.
   • Use another Business Process as a Template: Choose an existing Business Process as a template, thereby copying all tasks, references to objects, and parameters from the original Business Process.
3. Click Next.
4. Provide the Source folder, Package, and Name.
5. Click Finish. An editor appears.

Templates

Business Processes can be created using a Template. Templates are Business Processes that can be used as a foundation of a new Business Process with similar tasks and parameters. Templates are also used to group Business Processes that use the same parameters together. Any Business Process may be used as a Template.  Existing Business Processes can also be added to a Template, as long as it contains the same parameters.

The advantage is that any object that invokes a Business Process (primarily transformations or other Business Processes) can interface with the template, supplying the Business Process as a parameter. This increases re-usability and reduces the number of nearly-similar variations in transformations and Business Processes.

Tasks

The CIC Studio provides dozens of additional tasks to customize Business Processes, such as CompareFiles, FormatString, SendEmail, etc. A complete list of Business Process Tasks is provided in this help.

Related Topics

• Adding and defining tasks
• Pass or Fail Columns
• Using a Business Process within another Business Process
• Example: Use a Compare Task to branch from one Business Process to another