Meteor graphical designers include map designer, Data, task, web form, and exception designer. The design involves two steps: computer-independent business process description; workflow Description: data, task: function, location, role, condition what, where, WHO, and when.
Map designer:N
Allows user to design workflow dimo-graphically.N
Hierarchical Design•
High level Business Process Modeling•
Low level workflow Specification•
Subworkflow/compound taskMeteor contains the following words:
MAP/workflow digoalN
Task/activity/step•
Simple task vs. Compound task•
Manual task vs. Automated taskN
Role/ParticipantN
Link/transitionN
Data
There are many tasks
Type:
Map designer
Function: N
Insert, delete, modify, and move tasks and/or linksN
Cut/copy/paste tasksN
UndoN
GrabN
Specify task dependencyN
Specify data transferThe screenshot of map designer: Details of task admit:
Data designerA bit like OO design:
Task designerThe specific screenshot of the "check_eligibility" task in map: multiple attributes of a task;
Summary:Meteor organizes processes by tasks, which can be seen in the map diagram. In this case, is the goal-based task? The tasks in meteor have sub-processes and activities. From the task type, you can see the worklist tasks and combined tasks. This should be a sub-process, you can also see an "admit" task from the first figure in the map example. Based on its icon, you can determine that the task is a non-transactional compound task ", next is the "subflow" of the task ". We can see that all the tasks in its subflow are "simple task" tasks, which cannot be further divided. Let's look at a task check_eligibility in the subflow, which can be viewed as an activity.
