Can this action be performed as part of configuring an application definition in IdentityIQ?

Yes. This is exactly what the Managed property on an application schema attribute is designed to accomplish. During application configuration, an engineer can mark an account attribute as Managed. When IdentityIQ subsequently aggregates accounts, the distinct values of that attribute can be promoted into ManagedAttribute objects. Those objects are the records represented and governed through the Entitlement Catalog.

SailPoint documentation explicitly states that attributes designated as Managed can be viewed and managed from the Entitlement Catalog . Managed attributes can also receive governance metadata such as an owner, description, display name, and requestable status, and can participate in policies and risk calculations. For example, if an account attribute such as memberOf or groups is managed, the aggregated group values can become individual ManagedAttribute records.

The Entitlement flag and the Managed flag are related but distinct. Entitlement indicates that the attribute represents access that IdentityIQ should track. Managed promotes its values into first-class managed objects and makes them available through the Entitlement Catalog. Therefore the proposed action is valid application-definition configuration.

References/topics: IdentityIQ Engineer — Application Schema, Managed attributes, ManagedAttribute object, Entitlement Catalog, account aggregation.

=======