We have an extended attribute in ManagedAttribute ObjectConfig and its allowed values and the values should be dynamically displayed based on the entitlement application attributes

In New Entitlement Creation or Existing Entitlement Modification the above attribute should be displayed value2 and value3 based on the application that entitlement contains but not all the allowed values

ObjectConfig attribute

While Creating Entitlements

the drop down should be populated bases on application selected

@gsomaraju Could you please provide more details? If i understood your query right, you want to set an extended attribute as value2/value3 based on application name. If yes, you can achieve this using following ways:

  1. If you have aggregation, you can handle this in group refresh rule.
  2. You can modify the Entitlement Update workflow to set this attribute based on the application name.
  3. If you want to do it in UI, you need to modify the xhtml page. (not recommended),

My recommendation would be to go with #2 to use Entitlement Update workflow to set attributes.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

@gsomaraju I’m not seeing any support for dynamic allowed values for object attributes.

Possibly you could to define a different extended attribute for each application needing one.

SailPoint supports “Allowed values” on forms, but they are not supported on extended attributes. you can customize “Entitlement update” workflow to have an approval step. This will add a check for the approvers to see if values are correct.

you can also use “Group aggregation rule” to auto populate the values on group aggregation.