Making custom Strategy Result properties available for real-time container data flows
Now that you have passed in Context data as part of the Container request, you will want to access this data within your decision strategies. There are two utility functions that allow you to access this data depending on your requirements.
Pega Customer Decision Hub
IsValueInContext
The IsValueInContext function checks if a value exists in the list of Contexts passed in the Container Request.
IsValueInContext function parameters:
| Name | Description |
| Type | This parameter identifies the type of context. |
| Key | This parameter identifies the name of context. |
| Value | This parameter contains the data to be evaluated. |
GetContextValue
The GetContextValue function returns the value for the specified Type and Key in the Container Contexts.
GetContextValue function parameters:
| Name | Description |
| Type | This parameter identifies the type of context. |
| Key | This parameter identifies the name of context. |
| Value | This parameter contains the data to be evaluated. |
Container settings
You can toggle the following additional settings for Context in Strategies:
- Identity matching - Enabled by default. To disable, toggle the MKTEnableIdentityMatching dynamic system setting.
- Customer lookup - Enabled by default. To disable, toggle the MKTEnableCustomerLookup dynamic system setting.
- Customer validation - Disabled by default. To enable, toggle the MKTEnableCustomerValidation dynamic system setting.
Previous topic Identity management for the Container REST service Next topic Capturing responses to actions triggered by a real-time container