To add or remove a processor for a resolver, within the resolver definition, click the hamburger menu in the upper-right corner and choose Add Processing or Remove Processing.

For information about how to define a processor, see Value processing.

The following examples show how you might use these resolvers.

If you expect responses from different resolved sources to vary, you can add a processor to the resolvers to normalize the output. In this example, the attribute's value can come from one of the following resolvers:

  • A service named GET User Profile

    With this resolver, if the Cache is Valid attribute is false, the resolver calls the GET User Profile service and uses a JSON Path processor to extract the key from the profile JSON.

  • An attribute named Key

    In the second resolver, the attribute value comes from the Key attribute, and the value requires no processing.

The following image shows the resolvers. The resolvers apply in the order shown.

Screen capture of two resolvers. The first is a service with a condition and a post-resolution value process that outputs a value. The second is an attribute that captures and stores a value without conditions or processing.

This example uses a condition and a processor together to resolve an attribute that might have a prefix. The attribute has two resolvers:
  • The first resolver has a condition to check whether the Client ID attribute has a prefix of 002. If so, the value processor removes the prefix.
  • The second resolver has no condition and passes the Client ID attribute value through with no processing.

The following image shows the resolvers. The resolvers apply in the order shown.

Screen capture of two resolvers. The first is an attribute with a condition and a post-resolution value process that outputs a value. The second is an attribute that captures and stores a value without conditions or processing.