I’m working on an entitlement request use case in IIQ and looking for a scalable and user-friendly way to capture multiple values in the request form and pass them through the provisioning plan. When a user requests a specific entitlement (e.g., Loan Approver) for an application, we want to capture additional details through a form:
-
Branch Name (dropdown with ~30 values)
-
Write-Off Limit (dropdown with values from 0 to 15)
Each selected pair should be concatenated as BranchName-WriteOffLimit
(e.g., AA-12
), and users may need to provide multiple such entries (e.g., AA-12, BB-09, CA-06
, etc.).
Predefining 450+ combinations (30 branches × 15 limits) in a single dropdown is not scalable or user-friendly.
At the same time, IIQ forms don’t support dynamic “Add Row” functionality (like in HTML/JS forms). I’m looking for a solution that:
Starts with only one set of Branch–WriteOff fields
Allows users to progressively add more sets only if needed
Passes the values as a concatenated string or list in the provisioning plan
Avoids overwhelming users with too many fields by default
Any best practices or smarter approaches to handle this kind of dynamic multi-entry form logic?