IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing monitor models > Create monitor models > Defining the visual model > Defining actions
Sending human task notifications
You can click an area in the diagram at run time and have it affect certain human task widgets on the same page of the Monitor dashboard space. The information in the human task widgets is based on the area that you selected in the diagram.
For example, if a process diagram shows a process consisting of several different human tasks, you can click a human task in the diagram and the human task widgets are updated to show instances of that task. In this example, if you have a process that is performing poorly and your diagram has indicated that it is performing poorly because a particular human task is taking longer than expected, you can identify the problem area and who is responsible.
To update a shape set so that clicking the associated shapes at run time affects human task widgets:
Procedure
- Place your mouse cursor on the diagram and find the shape set in the area of the diagram that you want to affect. The cursor changes to a hand when it is on the shape set. Click the diagram to highlight the corresponding shape set in the table at the bottom of the page.
- Right-click the shape set in the table and click Add Action > Send Human Task Notification When Clicked.
- To control when the area in the diagram can be clicked at run time (and will notify the human task widgets), add a condition in the Condition row. You can either type directly into the cell, or, for a large expression, click the button to open a resizable window. For help writing the expression, press Ctrl+Space.
Because you are creating expressions to be resolved at run time, you can only use the elements in the context that the diagram is attached to. If the diagram is attached to a monitoring context, you can use the metrics, keys, counters, and stopwatches in that context. If the diagram is attached to a KPI context, you can use the KPIs in that context.
- Specify the value for the name of the human task, or an expression that will dynamically resolve to a human task name value at run time. The name and the namespace together identify the human task. To find the name and namespace, click the human task in the process model in Integration Designer. The name and namespace are displayed in the Properties view. The display name for the human task is different from the human task name that is stored in the database. The human task name must be enclosed in single quotation marks to be a valid XPath string.
- Specify the value for the human task namespace, or an expression that will dynamically resolve to a human task namespace value at run time.
For example, you might have metrics that keep track of the name and the namespace for the human task that takes the longest time. To find the name and namespace, click the human task in the process model in Integration Designer. The name and namespace are displayed in the Properties view.
- Optional: Specify the value for the human task instance ID, or an expression that will dynamically resolve to a human task instance ID value at run time. Typically, you will leave this field blank so that when you click the human task representation in your diagram, you will see all the existing instances of that human task. Specify a value only if you want to filter for a particular human task instance.
If you generated the monitor model from a BPEL model using Generate Monitor Model, the default pattern places the human task instance in a nested monitoring context, instead of at the level that is needed for adding the action.
You might even have a separate monitoring context for each human task in the process. If you want to associate the process diagram SVG with the monitoring context that represents the process as a whole, and then enable each click of a human task in the diagram to filter the human task views in dashboard space, create metrics in the main monitoring context that hold the values of each of the human task instance IDs. Then write an expression for the human task instance ID in the process monitoring context that gets its values from those metrics.
What to do next
In the dashboard space, you must set up wired connections between the diagram widget and the human task widgets.