Rules

Rules are Sterling B2B Integrator business processes used to perform specific business operations.

Create Rule

To create a rule, you must first develop a business process and deploy in Sterling B2B Integrator. Once created, the Create Rule option in PCM will display the business process name in the drop down for selection.

Specify the following fields for the rule:
  • Rule Details
    • Business Process: Business process names are derived from Sterling B2B Integrator, as PCM is integrated with it.
    • Rule Name: The name of a user-defined rule that describes the process.
  • Rule Property Details
    • Property Names: Property names are inputs into the business process; they have a key-value pair relationship. For example, the key is Date Time Format, which can be any user-defined value such as yyyyMMddHHmmss, yyyymmdd, and so on. You must specify the property names in accordance with the business process functionality.
Note:
  • The business process must be created in Sterling B2B Integrator. For more information, see Creating Business Process Models.
  • You can include any custom data as a property that has to be communicated to the business process. The property value can vary; the same rule applied to various partners may have different property values.
  • The Properties can be fetched from PCM Rule into the business process; The Out of Box CM_ProcessRules business process fetches the details from the Rules and passes it onto the business process of the appropriate rules.
    The Properties can be retrieved from the PCM Rule and entered into the business process; the Out of Box CM_ProcessRules business process retrieves the details from the Rules and forwards them to the relevant rules' business process. They are stored in XPATH XPATH /ProcessData/CM_FRAMEWORK/ExecRules/VALUE1/text( for Property1 Value, /ProcessData/CM_FRAMEWORK/ExecRules/VALUE2/text( for Property2 Value, and so on. For example, to construct a concatenation of two names supplied as properties, we define a rule called Concatenation with Property1 and Property2. In the business process, the concatenation logic is added as
    <assign to=”output” from=”concat(/ProcessData/CM_FRAMEWORK/ExecRules/VALUE1/text(),/ProcessData/CM_FRAMEWORK/ExecRules/VALUE2/text())”/>

Predefined File Processing Flow

The process is bootstrapped through scheduler or routing rule and is routed to the Core Process business process. Core Process finds if the file matches the MFT pattern or Doc Handling data and executes the appropriate file types' rules. Once all the rules are executed, the details are logged into the transfer tables.

In case of errors, the Error Handler business process is invoked to send email notification.

Customizing the Predefined File Processing Flow

The bootstrapping is performed through Scheduler or the Routing Rule. You can create your own custom business process and utilize it.

In the case of On Arrival polling interval, the custom business process can be utilized in the Routing Rule.

In case of any scheduler polling interval, the specific scheduler business process will have logic to invoke the GET business process for all the protocols. You can update your business process with its custom business process.

The processing rules can be customized as referred in Create Rule.

The Drop Process is the predefined business process, which invokes the respective protocol PUT process. You can create your own PUT business process and utilize it in the predefined Drop Process business process.