Are mapping rules allowed on calculated fields in identity management?

In identity management within the context of SailPoint Identity Security Cloud, calculated fields are derived from other attributes and are not treated as standard attributes. Due to their nature, mapping rules—which are typically used to correlate data from various sources with attributes in the identity model—cannot be applied to calculated fields. This is because calculated fields rely on dynamic data processing rather than directly corresponding to a static value or attribute that can be mapped.

Understanding this distinction is vital for constructing identity governance frameworks properly, as it ensures that configurations are done only on attributes that support mapping rules, thereby maintaining the integrity and accuracy of identity data management processes.