You can use the Assignment Service shape to send a request from a process to an external application, and wait for the application to respond. For example, in a mortgage case, a loan officer can assign a task to an external party to get the credit score for a customer, and proceed with reviewing a loan request from the customer only when the external party sends the credit score.
- Ensure that the process for which you want to use an Assignment Service shape already exists. For more information, see Creating a top-level case type.
- Build your own connect rule, and then build a connect activity that maps the data from the service that you call into your case. For more information, see Creating a REST integration.
The Assignment Service shape moves a case to the next step only after receiving a response from the external system. The Assignment Service tasks support asynchronous coordination with external systems, in contrast to Integrator tasks, which support synchronous connections.
- Add the Assignment Service shape to your process.
- In the navigation pane of Dev Studio, click App.
- On the Classes tab, expand the case type for which you want to add the assignment, and then click .
- In the list of Flow instances, double-click a flow that you want to open.
- On the Flow form, on the Diagram tab, click the Flow shapes icon, and then click .
- Drag the Assignment Service shape to a position on the flow diagram based on the order of events in the process.
- Connect the Assignment Service shape by dragging connector end points to connection points on different shapes in the process.
- Modify the Assignment Service shape to send a request from a process to an external
- Double-click the Assignment Service shape to open the property pane.
- In the Assignment Service field, enter a name for the
shape.Choose a name that is meaningful to users who see the name on the work object history display, the breadcrumbs control (for entry points), and inside the Assignment Service shape on the Diagram tab.
The task name does not affect run-time processing of the flow.
- In the Type field, press the Down arrow key, and then select the name of a connect activity.
- If the activity accepts input parameters, enter parameter values in the list that is displayed.
- Optional: To associate a service-level agreement with the Assignment Service shape that is
independent from service-level agreements set on a flow or case type, press the Down
arrow key, and then select the name of a service-level agreement that you want to
For example: You can set a service level for the task to begin escalation processing when the application fails to get a response from the external system after 60 seconds (which might indicate that the external system is unavailable or that other technical problems are present). For more information, see Errors returned by a connector and Handling connector exceptions.
- Optional: To control the text of instances that are added to the work item history when flow processing completes this shape, in the Audit Note field, enter or select the name of a Rule-Message rule.
- Optional: To update the status of a case on this shape, in the Work
status field, press the Down arrow key, and then select a value that you
want to apply.For more information, see Changing case statuses.
- Optional: To activate a ticket in a flow that detects an exception, error flow, or event, in
the Tickets section, in the Ticket name
and the Display name fields, press the Down arrow key, and then
provide values that you want to apply.
For more information, see Responding to business exceptions in a flow. Note: You can use more tickets by adding a row for each ticket. If a shape has more than one ticket associated with it, then the processing of the task continues only after all tickets are set.
- Click Submit.
- Click Save.
- Setting a service-level agreement for the Assignment Service shape
You can associate a service-level agreement with the Assignment Service shape in a flow. By defining goals and deadlines, you can set expectations for the time that it takes an external system to complete a single task in the process.