Web Services Workflow activity
SandraWeiss 060000BCJJ Visits (11008)
What does this all mean? One can construct a Workflow that is triggered by a Situation running at agentX and against tableA. The Workflow can then run a CT_Get activity targeting agentY and tableB and specify a filter on any of tableB's columns substituting into that filter an attribute that was returned by the triggering Situation.
The data from the CT_Get can then be used for a system command or displayed in a Universal Message Console via the "Take Action or Write Message" activity.
To enable this activity the dockib file must be edited. Make sure to make a copy of the file prior to editing. All entries starting with *ACTIVITY: CT_Get and ending just before the next *ACTIVITY need to have the *REM: removed. The TEPS must be restarted after the changes since this file is processed only during initialization. Now when creating a Workflow there will be an new entry under Extensions - "Get a Candle Report".
So PolicyX would have the following activities
1) "Wait until a situation is True" which would specify the Situation running at agentX against tableA.
2) "Get a Candle Report". This is where the information from agentY and tableB would be defined. The attribute(s) from the triggering Situation would be specified as the value for the filter(s). Since the value(s) is from the Situation, it would start with &Wai
3) "Take Action or Write Message" activity. This is where data from the CT_Get can be used by clicking on the XML button. In "Element substitution" enter the attribute in the "an tag element that" field. tag would be substituted with one of the attributes selected on the "Get a Candle Report" activity. Make sure to specify descendent in the "is a" dropdown. Then click on OK.
Connect the the activities and distribute, start the policy.