Dynamic contexts

In addition to context items, processes can also use dynamic contexts to store values.

When you are creating a process with the  Development Studio application, you can use dynamic contexts to store data in a container that can have a variable name. With a context item, a value is assigned to a specifically named container. When using a dynamic context item, the name of the container is the value of a specific context item.

For example, if you need to store information about a help ticket and want to reference that ticket ID to retrieve the stored information, a dynamic context could be used. A one-time use context item would not be required to store the information, and the process can be reused many times.

A dynamic context is typically used to hold an XML document that contains multiple values used for reference in multiple processes that can be executed over time. These values can be used to cross-reference other systems or hold other data that cannot have a specific storage location in a database but would be valuable in subsequent processes.

Dynamic contexts are designed to hold small amounts of reference data. They are designed to be used when there is not a convenient location to store reference information. Using dynamic contexts increases disk and memory usage and increases network traffic.

Note

Dynamic contexts are created with a global scope, and they cannot be deleted.

Dynamic context sample data

Type of context

Name

Value

Context item

Ticket ID

CM0901

Dynamic context
CM0901
<event>
    <problem-id>P1234</problem-id>
    <cmr-id>C5678</cmr-id>
    <event-id>90745</event-id>
 </event>

This section contains the following topic:

Was this page helpful? Yes No Submitting... Thank you

Comments