You can use an existing flow action to assign a task to a user. By reusing the forms and fields in your application, you can design case types more efficiently.
In the Explorer panel, click Cases, and then click the case type that you want to open.
On the Life cycle tab, hover on a process in a stage and click + Step.
In the palette that is displayed, click More.
Click User actions to display a list of flow actions.
Tip: To change which flow actions are displayed in this list, use the Relevant Records tab on the Application Inventory landing page.
Click the name of a flow action and review the description that is displayed.
Click Select to add an assignment to the process that displays the flow action to users at run time.
On the General tab of the contextual property panel, enter values in the fields to indicate how the assignment, or task, is routed.
In the Route to list, select Specific user.
In the autocomplete field that is displayed, press the Down Arrow key and select the name of a user.
In the Route to list, select Work queue.
In the autocomplete field that is displayed, press the Down Arrow key and select the name of a work queue.
In the Route to list, select Use business logic.
Click the Gear icon to configure the business logic.
In the Business logic dialog box, define a routing method:
In the Action list, select a routing method.
In the Value field, press the Down Arrow key and select the name of an operator or work queue, based on the routing method that you select.
In the When section, define the conditions that must be met before the routing method is selected:
In the Field list, select the name of a field in your data model.
In the Comparator list, select a function.
In the Value field, enter a value that is compared with the field at run time.
For example, you can test whether a case is older than five days or has an urgency that this greater than fifty.
Optional: To define more conditions, click the Add icon and repeat steps i through iii.
By default, all conditions in the When section must return a true value before the corresponding routing method is selected. You can change this behavior by selecting different Boolean operators from the list that is displayed next to each condition.
Optional: To define another routing method and corresponding conditions, click + Add condition and repeat steps c through d.
When you provide multiple sets of routing methods and conditions in your business logic, the first routing method to meet its conditions is selected at run time.
In the otherwise section, define a routing method to use when no conditions return a true value:
In the Action list, select a routing method.
In the Value field, press the Down Arrow key and select the name of an operator or work queue, based on the routing method that you select.
Click Done.
In the Route to list, select Custom.
In the Assignment type list, select an activity that creates an assignment.
Tip: To use a standard activity that is not in the list, configure the Assignment shape in Process Modeler. See: Routing an assignment in a flow.
In the Router field, press the Down Arrow key and select the name of an activity that determines how the assignment is routed.
For example, you can use the ToDecisionTree activity to route an assignment based on the value that is returned by a decision tree.
If the assignment is in a swimlane on the flow diagram, configure the assignment and the swimlane with the same router activity. You can access the swimlane by opening Process Modeler.
If the router activity accepts parameters, pass values for those parameters by entering values in the fields in the Parameters section.
Click Save.