Yes. Bundle is the IdentityIQ object model class used for roles, and it can be extended to store client-specific role metadata through the supported extended schema process. Custom role programs often require extra attributes on roles, such as risk category, ownership tier, regulatory classification, business unit, lifecycle state, approval model, or migration metadata. Updating the corresponding Hibernate mapping file is part of how persistent object extensions are introduced. However, the mapping update is only one step. The engineer must generate the database schema update script, apply it to the database in the correct operational state, and update ObjectConfig so IdentityIQ understands and exposes the custom attribute properly. The Word bank describes this same extension sequence: update the mapping layer, generate the schema script, run it on the IdentityIQ database, then update ObjectConfig after restart. Therefore, Bundle is a valid object for this type of client-specific data extension. References/topics: IdentityIQ Engineer — Bundle object, role extension, Hibernate mapping, extended schema, ObjectConfig, database schema update.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit