Triggering a Test Escalation Process
Prior to placing your escalation process into a production environment, you might want to run in your development environment to test its behavior.
To trigger a test escalation process
2. Build and upload the process to your targeted Integration Server.
3. In the Package Navigator view, in the WmClosedLoopAnalytics package, right-click wm > closedloopanalytics > docTypes > ProcessEscalation.
4. Click Run As > Publish as JMS Message.
5. In the Enter Input dialog box:
a. In the JMS connection name alias field, click the browse button and select PE_NONTRANSACTIONAL_ALIAS.
b. In the Destination name field, click the browse button and select projectName_processName_SUBQUEUE
c. In the Destination type list, make sure Queue is selected.
d. Select the Prepare message for BPM check box.
e. In the JMS Message Body section, type some test data to populate the document type, for example, originator, due date, task assignee, and so on.
f. Click OK.
Successful publication of the JMS message is shown in the Results view. The published document should trigger a new instance of the escalation process.
You can log into to My webMethods Server and browse to Navigate > Applications > Monitoring > Business > Process Instances to view the resulting process instance.
You can browse to Navigate > Applications > Monitoring > Business > Tasks > Task List Management to view the resulting task instance (assuming you have the correct permissions). You can also view the task in its own task type inbox, as well as in the My Inbox page for any assigned user.
Contact Support
|
Community
|
Feedback