TimeElapsed_UCA
#An example of time elapsed UCA
- It is an UCA that runs regularly at pre-defined times of the day.
- Let us consider a simple example where the customer fills in the order entry form and is displayed to him to confirm before submission.
- As seen in the following screen shots, 2 activities are used:
(i) Order Entry Activity: allows the customer to provide his details.
(ii) Results Activity: displays the customer-entered information to the customer before submitting.
The following screenshot shows the process constructed:
The following screenshot describes creation of business object:
The following screenshot describes construction of variables:
The following shows the construction of human coaches for each of the above mentioned activity.
(i) Order Entry:
(ii) Results:
Output:
-
Now, to start this process at 10:00AM and 2:00PM on Wednesdays and Fridays, we need to use Timed-UCA. This is illustrated in the following section:
-
Step 1: Create a General System Service from 'Implementation' tab. Also create an output variable(say, message)
-
Step 2: Create a new Undercoverage Agent from 'Implementation' tab.Attach the above created General System Service to it.
-
Step 3: For this created UCA, select the time schedule as shown in the screenshot.
-
Step 4: Change the Start Event type in the process from 'None' to 'Message Start Event' as seen in the screen shot. And attach the above created UCA to this message trigger. Also, create a variable in the main process that accepts the variable:message passed in through the UCA.
Thus, the process is now started by the UCA event on every wednesdays and fridays at 10:00AM and 2:00PM.
Note: A process can have only 1 start event of type 'None'. But, there can be many message start events that use UCAs.
For example:
In the screenshot shown in step 4, there can be another UCA that directly passes the data to the Results service.
