Dynamic context scenario

The following example illustrates how data can be stored for a ticket in one process and retrieved using the ticket ID after an event triggers a second process.

When this process is run in your environment, the value of the dynamic context item is extracted by a transform expression from the event that triggered the process. You trigger the event by performing an intervening step. To clearly illustrate this point, the example depicts an input value that is a fixed value. In practice, this input value would create a context item populated by a preceding activity in the process.

1. In an Assign activity in a process in the

   WarningSome content is unavailable due to permissions.

   Development Studio application, assign the value CM0901 to the context item Ticket ID.
2. Compile the data associated with ticket CM0901.
3. Assign the data to an output with a parameter type dynamic context.
4. Use the Context Browser to select the TicketID context item.
    This assigns the data to a dynamic context named CM0901.
5. Create a second process.
6. In this process, populate a context item named EventIDs with the value CM0901.
7. Create an assign statement with an input of dynamic context, using the Context Browser to select the TicketID context item.
    The output should be a new context item, used to hold the data captured for the ticket in the previous process. This sample assigns the value of the dynamic context to a context item named EventIDs.

This EventIDs context item can be used by other activities in the process as needed to work with the stored ticket data.