| # Business processes in the Modeler To start the Modeler and edit the business processes based on the Petri-net method: On the appropriate menu in the Business Processes (tgbrg5500m000) session Click the Editor icon, or the Business Process Editor... To graphically depict the business process, activities, states, control activities, conditions, and relationships must be defined. The basic data of the business process components can be modified by double-clicking a component; alternatively, right-click a component and selecting Properties from the shortcut menu. Depending on the type of business process component, this will activate one of the following sessions: The Business Process Activities (tgbrg5122s000) session. The Business Process States (tgbrg5130s000) session. The Condition (tgbrg5145s000) session The Dynamic Condition (tgbrg5146s000) session The Static Condition (tgbrg5147s000) session Before business process diagrams can be inserted into business process models that are part of a reference or project model, they must first be created in the repository. Activity An activity represents tasks that must be carried out.
Activity types
Alternative | Description
--- | ---
Business Process | A sub-process to break down complex processes into smaller, more manageable sub processes.
Manual Activity | Defines that the user must perform a task that is not automated.
File based (client) | Starts for a file the associated application on the client, based on the file extension.
Application | Lets you select a defined Component Application, which can be a reference to an ERP session, such as an LN session.
Control The control is the graphical representation of a decision moment in the business process. By linking static conditions to the arrows leaving the control, the path through the business process can be determined. A control can represent an AND, OR, XOR, or JOIN. State Represents the internal conditions defining the status of an activity at a particular time.
State types
Alternative | Description
--- | ---
Begin | Defines the beginning of a business process.
End | Defines the end of a business process.
Normal | A state between two or more activities.
Relationship A relationship is used to sequence the states, controls, and activities. Syntax Checker in the Modeler To check whether there are mistakes in the current business process, select the Check Query Syntax option from the Options menu You can select a Development or Run time check. Both options will start a check of the syntax according to the Petri-net method for the current business process only. The only checks that go beyond the level of the current business process are related to loops in lower sub processes. A Run time check carries out a complete check of the business process; however, the Development check carries out a partial check. Because the syntax is only checked for the current business process, no checks are carried out for sub processes that might be included, except for loop detection or for possible higher-level processes. |