Process Modeling in Sterling Order Management Software is the set up of business process workflow through a pipeline.
Within your business, process modeling is the tool used to configure the flow of business documents, such as orders or shipments based on your business requirements. Pipelines represent the actual end-to-end process that your business goes through and are a series of transactions and statuses that guide document types. You can set up transactions consisting of events, actions and conditions, as they pertain to the pipeline you are configuring. Process modeling enables you to set up your business workflow for the various business entities, such as orders and shipments.
- Base document types
Base document types are used to represent types of business orders such as sales order, return order, or purchase order, and so on. and document types carry information through a configured workflow process. A base document type defines the business documents that Sterling Order Management Softwarehandles and defines a common storage structure for all derived document types.
For example, Order is a base document type and is used as the document type for sales orders, returns, and purchase orders. It is this document that is carried through a configured workflow process.
- Process type and pipelines
A Pipeline is a series of transactions and statuses that guide a document through its process type. A business document, such as an order, goes through a series of defined processes.
For example, the Order base document type has the following defined types: Fulfillment, Negotiation, and Delivery.
You can configure the flow of these processes in the Process Modeling by creating process type pipelines. A process type pipeline is a series of transactions and statuses that can be turned on or off and that guide document types, such as Sales Order and Purchase Order, through a related process. A pipeline consists of the different statuses a document goes through during fulfillment. You can also set up transactions consisting of events, actions, and conditions, as they pertain to the pipeline you are configuring. Each step is considered to be a transaction, which is provided out of the box or custom ones can be added. Transactions can be stringed together conditionally, based on the criteria that on order or shipment does or does not meet. For each transaction that takes place, you can configure the system to perform a specific action or service. For example, if a transaction is successful or a transaction fails, you can configure an event that will take place and the configured action or service will react to the event accordingly. Transactions have an associated event and the events enable you to configure it a particular reaction to a transaction.
For example, a simple pipeline.
|If you are...||See this topic|
|A system administrator configuring process modeling to set up your business workflow||Configuring process modeling|