Configuring process models

Process Modeling is the process for setting up the Sterling™ Order Management System business process workflow.

The Sterling Order Management System workflow consists of the entire set of business logic that defines how Sterling Order Management System handles business documents and transactions on those documents. A transaction is a logical unit of work that encapsulates certain business logic. Transactions can be related to orders, inventory changes, returns, payment authorizations, or many other system events. Order Create, Inventory Monitor, and Send Release are examples of transactions.

Business process workflow consists of:

  • Document types
  • Repositories
  • Process-type pipelines
  • Transactions
  • Conditions
  • Events
  • Statuses
  • Actions
  • Services
Important:

An implementer (SI) should not modify the application-provided configurations like Agent Criteria, Flows (Services), Conditions and Transactions.

  • The application-provided Agent criteria is a sample configuration, it belongs to the product and it may change across releases. The sample configuration is a way to expose the new parameters added for the agent.
  • The application-provided Services are published and their behaviour is documented. An SI should not modify these services. Additionally, their behaviour may be enhanced over the releases and documentation would be updated accordingly.
  • The application-provided Transactions are published and their behaviour is documented. Additionally, their behaviour may be enhanced over the releases and documentation would be updated accordingly. An SI should not modify the main transaction configurations. However, they can still change other configurations on the transaction screen such as enabling an event, enabling event handlers, activating actions and services, and so on.
  • The application-provided Conditions are also published and their behaviour is documented. Their behaviour may be enhanced over the releases. Additionally, an application-provided Condition may be used in some application-provided Services and Event handlers. Therefore, altering a condition could fail such services and event handlers.

Instead, an SI must create a new component by looking at the application-provided configuration. The Applications Manager provides a 'Save As' option as well. By using this option, the SI can easily duplicate a component and use it in the required configuration.