You can easily achieve this by populating the attribute to the default value using Account Customization rule. Create a customization rule and map it to your application with a code similar to this, this ensures your resourceObject(account) is updated with the STATUS attribute as part of the aggregation task
If you have created a status schema attribute then you can create a customization rule and set the status value to be NA irrespective of any condition. This will set the status as NA for all the resourceobject.
Hi all, it does set a status attribute as NA in my schema but it does not reflect in this column in the Accounts tab in my application. Am I missing something? Or this status is controlled by iiqDisabled attribute and it cannot be NA?
Yes, the status(active/inactive) of the account is completely determined by IIQDisabled attribute for LDAP connector.
Customization rule can also be used to populate IIQDisabled attribute based on your logic, when the value is true, the account will be displayed as disabled(inactive)
Yes, that’s correct. Purpose of IIQDisabled attribute to display the status of the account on the UI, which can be only two possibilities i.e., Active (Green), Disabled (Red).
Though your actual status attribute can be more than one value, logic on IIQDisabled should only be leading to either true or false based on the status attributes.