Flow form
Process Modeler — Editing Assignment Service shape properties
Flow form
|
|
Use the Assignment Service shape
in a flow to pass control to an external system using a connector (for example, Connect BPEL rule). Assignment Service shapes support asynchronous coordination with external systems.
Both Integrator shapes and Assignment Service shapes reference an activity of type Connect. For an Integrator shape, flow execution continues as soon as the activity completes. For an Assignment Service shape, flow execution pauses until PRPC receives a incoming service request of the appropriate type.
A clock shape 
indicates that an SLA is applied to the Assignment Service.
indicates that one or more tickets are defined on the Assignment Service shape. Assigned ticket names appear beside this icon on the flow.
On the flow Diagram tab, you can add a shape to a flow in one of three ways. Validation of the added shapes occurs when you save the flow.
to display a drop-down shapes menu that will remain open until you close it, facilitating the process of rapidly adding multiple shapes. Click the window title bar and drag the submenu to another area of the screen, as needed.
on the toolbar Flow Shape palette to display a drop-down shapes menu.
.
This name also appears inside the Assignment Service shape on the diagram. You can edit the name by double clicking the shape's label on the diagram. To change the name after you have exited from the properties panel, click the name, and type over the highlighted text.An assignment service shape may be deleted from the process flow. Right-click the assignment service, and select Delete from the drop-down menu.
You can also select the assignment service shape and do one of the following:
icon on the toolbar.
When a shape is deleted, the connectors to and from the shape are also deleted.
Complete the sections comprising the property panel as described below.
Field |
Description |
| Type |
Select an activity with an Activity Type of |
| Parameters |
The assignment activity you select may accept input parameters that will appear in the box below. Supply a value for each parameter. PRPC validates these parameter values when you save the flow. (unless the flow in is Draft mode). |
| Service Level |
Optional. Select a service-level agreement to apply to this shape. For example, a service-level agreement can cause escalation processing when no response is received from the external system after 60 seconds. This may indicate that the external system is unavailable or that other technical problems are present. See Handling connector exceptions. |
| Audit Note |
Optional. Select or enter the name of a Rule-Message rule to control the text of an instances added to the work item history (the "audit trail") when a flow execution completes this shape. PRPC includes a few dozen standard messages in the Work- class. (Through field value rules, the corresponding text on work item history displays can be localized.)
|
| Entry Point |
Select to indicate that this Assignment Service shape is an entry point, which a user can return to using the breadcrumbs control or the standard flow action Work-.Previous. The default is cleared. This check box works with Perform harnesses that include a breadcrumbs display and with assignments that offer the Work-.Previous flow action. In other cases, the check box has no effect. |
| Only Going Back |
This check box appears only when you select the Entry Point check box. Select to restrict users at runtime from jumping ahead to this step without having completed the preceding steps. After having completed this step, users may jump back to it from steps that follow it. Leave unselected to allow users to select this entry point from anywhere within the flow. They can complete or visit an earlier or later step.
|
| Post Action on Click Away |
This check box appears only when you select the Entry Point check box. Select to run flow action post-processing when you click away from this entry point. |
Field |
Description |
| Specification |
Enter a name to associate a specification with this shape. If you change the default shape name [Assignment Service], the system enters the name in this field. You can either:
Enter a description in the text area beneath the specification name. When you click OK on the Properties dialog, the system creates or updates the specification. See Working with specifications in Process Modeler and Case Designer. |
Complete the Status, Specification, and s sections as described below.
Field |
Description |
| Work Status |
Set the status for the work item. This allows you to easily change the status at multiple points in the life cycle of a work item without adding a Utility shape to the flow for each status change. Similar to setting work item status using a Utility shape, setting the status invokes the UpdateStatus activity. Any defined tickets dependent on the status are raised, as appropriate. The selected status updates .pyStatusWork when the flow execution reaches this assignment shape. A status indicator appears on connectors to shapes that change a work item status. For example, if the shape status is set to Pending-External, the connector to that shape displays a small red flag. All transitions connecting to the shape will display the status indicator. Following are the status indicators for the four status prefixes.
|
Add a Ticket Name to indicate the ticket(s) available at runtime. Use the Ticket to mark the starting point for exceptions that may arise at any point in the flow, such as a cancellation. The ticket is a label for a point in a flow, much like a programming "GOTO" destination.
An activity executing anywhere in your entire PRPC application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter. See Ticket help for other ways to raise a ticket.
The scope of a raised ticket includes all flows on the current work item that contain this ticket. If found, processing stops on that flow promptly, and resumes at the ticket point.
The system adds a ticket icon to the assignment service shape to indicate that one or more tickets are associated with this assignment service. Assigned ticket names appear beside this icon on the flow.
Field |
Description |
| Ticket Name |
ExampleProcessing is connected to a ticket to respond to an exception, error flow or event. For example, if a mortgage application is withdrawn after some, but not all, of the application processing is completed, a mortgage processing flow can:
|
| Display Name | Optional. The Ticket Name appears by default. Enter a name to display other than the ticket name. |
For maximum user flexibility, leave this check box unselected if your flow accepts inputs in any order. However, this approach is typically not workable for flows that contain decision shapes, or that have intermediate tasks that are not entry points.
New
Open
Pending
Resolved
Optional. Select one or more tickets that are to be available at runtime from this assignment service. Add a row for each ticket. Use SmartPrompt to display all tickets available to flows in this work type.