Configuring process modeling
Process modeling in Sterling™ Order Management System Software enables you to set up your business workflow of orders, inventory changes, returns, payment authorizations, or many other system events.
The workflow consists of the entire set of business logic that defines how Sterling Order Management System Software 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.
- Base Document Types and Document Types
- Process Type Pipelines
- Repositories
- Transactions
- Conditions
- Actions
- Services
- Process Modeling Tasks
You should not modify the application-provided configurations like Agent Criteria, Flows and Conditions.
- 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. You should not modify these services. Additionally, their behaviour may be enhanced over the releases and documentation would be updated accordingly.
- 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, you 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, you can easily duplicate a component and use it in the required configuration.