Dropdown Auto-population Failing Due to Field Order - Identity Manager

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal

Issue/Introduction

This article explains a known limitation in CA Identity Manager where configuring a "Dropdown Combo" style attribute above dependent attributes causes auto-population scripts to fail. To ensure JavaScript-based auto-population functions correctly, the control attribute must be placed appropriately within the screen configuration.

Environment

Identity Manager 14.5

Cause

In Identity Manager, form attributes are initialized based on their order in the screen definition. If a dependent attribute is initialized before the trigger attribute (the dropdown) has provided a value, the auto-population script cannot successfully reference the trigger attribute's selection.

Resolution

1. Navigate to Admin Task > Tabs > Profile.
2. Click Browse next to the Screen field and select Edit.
3. Identify the dependent attributes that need to be populated by the dropdown selection.
4. Rearrange the attributes such that the trigger attribute (the Dropdown Combo) is placed below the dependent attributes in the screen list.
5. Ensure Validate On Change is set to Yes for the dropdown attribute.
6. Add the appropriate validation script to the dependent attribute's Validation JavaScript field:

function validate(FieldContext, attributeValue, changedValue, errorMessage) {    changedValue.reference = FieldContext.getFieldValue("Title");    return true;}

Note: If using a shared Corporate and Provisioning store, ensure field references in the script are updated (e.g., eTTitle instead of Title).

7. Submit the task to apply changes.