 Reviewing the process flow of the deployed template application The gadget spec URL could not be found
In the last section, we learned how to establish a workflow for a business process. In this section, we will review the process design implementation of the customer model in the template application. Since it is a master data, there is no specific workflow process for the customer model. However, we need to configure the user access privileges and access points. The customer details are maintained by the sales team. Any member of the sales team can edit the details of any existing customer or add a new customer.
 Review workflow implementation in process design perspective
The workflow is implemented using the visual modeling environment. Point-and-click selectors can be used to insert a workflow activity, which could be a manual task, automated task or control point for branching. The activity owners and access points (forms, queues) for each of the activities can be configured easily in the process design perspective.
|
|
|
|
Default workflow for a data model
|
| |
|
|
|
Open process design perspective. By default,
- All models have a "Start" and "End" workflow activity.
- The instances in the "Start" worflow activity can be accessed only by the creator. However, everyone can create a new instance, provided the user privileges have not been configured.
- The instances in the "End" workflow activity cannot be accessed by anyone.
|
| |
|
|
|
When a workflow activity is selected, it's name is displayed in the "Namebox' and user mail/user group id is displayed in "Formula bar".
Only the configured user or users belonging to the configured role (user group) can access the records in that workflow activity.
|
| |
|
|
By configuring the user/user roles for an activity, access to a functionality can be restricted.
|
|
|
|
|
|
User access privileges
|
| |
|
| |
The access to the create customer form has been configured by assigning the role "sales team" to the start workflow activity. |
| |
|
|
|
Select the "Start" workflow activity.
|
| |
|
|
|
Rename this workflow activity as "Customer Draft" by updating the value in the Namebox.
|
| |
|
 |
Only the sales team must be able to access customer menu i.e. create customer details.
Click on the role icon and enter the sales team role name in the formula bar.
|
| |
|
 |
The access points for an activity can be configured by updating the properties for the "Connect" option.
|
|
|
|
|
|
Customer List
|
| |
|
| |
Our requirement is that "any member of the sales team must be able to edit the details of any existing customer." Hence, the instances (new customer details added) must be moved to a new activity that |
| |
|
|
|
Insert a workflow activity between start (now "Draft") and end.
|
| |
|
|
|
Rename this workflow activity as "Customer List" by updating the value in the Namebox. |
| |
|
|
Only the sales team must be able to view/edit customer details.
Click on the role icon and enter the sales team role name in the formula bar. |
| |
|
|
The access points for an activity can be configured by updating the properties for the "Connect" option. |
|
|
|
|
|
|
|
|
Insert a goto activity between "customer list" workflow activity and end workflow activity.
|
| |
|
|
|
Rename this workflow activity as "GoTo List" by updating the value in the Namebox. |
| |
|
| |
The goto activity is used so as to keep the instances in the "customer list" workflow activity. When the sales team edits the customer details and submits the instance, it will be moved to the next workflow activity, which is a goto activity that moves the instance to the "customer list" activity. |
| |
|
|
|
What's the next step?
Exploring process design perspective
|
|
|
|
