LinkedIn
Copied!

Table of Contents

Making custom Strategy Result properties available for real-time container data flows

Version:

Only available versions of this content are shown in the dropdown

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.

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.
@PegaMKTUtilities.IsValueInContext("Intent","IntentName","CloseAccount",Primary.ContainerPayload.Contexts)

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.
@PegaMKTUtilities.GetContextValue("Intent","IntentName",Primary.ContainerPayload.Contexts)

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.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.