ObjectConfig - ManagedAttribute Extended Attribute allowed values in Dropdown

Hi All,
We are working on 8.3p3 and we have a extended attribute in Managed Attributes.

We have an extended attribute in ManagedAttribute ObjectConfig, which is created something like mentioned below:

<ObjectAttribute displayName="Test" name="Test" namedColumn="true">
   <AllowedValues>
     <String>TRUE</String>
     <String>FALSE</String>
   </AllowedValues>
 </ObjectAttribute>

In Entitlement Catalog this attribute is coming as radio button but we want to display this as dropdown.
Is it possible to do that and If Yes, please help us knowing how we can achieve that.

Hello @nkishor1995

Welcome to Sailpoint Developer Community for your use case. Try to update objectattribute as below:-


<ObjectAttribute displayName="Test" name="Test" namedColumn="true" type="string">
   <AllowedValues>
     <String>Select</String>
     <String>TRUE</String>
     <String>FALSE</String>
   </AllowedValues>
</ObjectAttribute>

Let me know if it worked as solution.

Thanks
Ashish Sharma

1 Like

Hi @nkishor1995 if you have 2 values in allowed values by default it displays as radio buttons, in order to display it as drop down you need to have more than 2 values.

2 Likes

Yes, If we have more than two values then by default it will take it as drop down but then it will show “Select” also an available option which is not a preferable option from a user experience perspective.

1 Like

Hi @nkishor1995

user experience:

When user experience matters, I agree that having an additional selectable value can be problematic.

While you can set a default value, like
<DefaultValue>TRUE</DefaultValue>
and make the third value meaningful (e.g., none, N/A, or --), it’s important to make a note of its purpose.

However, I would like to persuade you to consider using radio buttons when you have only two values. A dropdown with an additional, potentially unnecessary, value can negatively impact user experience.

1 Like