A customer wants to make changes in their IdentityIQ user interface.

No. Updating the original shipped HTML file is not the general IdentityIQ configuration mechanism for changing UI settings or branding. IdentityIQ exposes different customization mechanisms depending on what the engineer needs to modify. For example, table presentation can be controlled through UIConfig and ColumnConfig, login-page text can be driven through message-catalog keys, and styling or branding can be implemented through supported CSS or branding mechanisms. The existing question bank itself distinguishes these configuration mechanisms: it identifies ColumnConfig for table display and message-catalog keys for login-page text.

The bank also notes that primary and secondary color behavior is associated with custom CSS/branding rather than the IdentityIQ Configuration > Miscellaneous page.

Direct modification of original product HTML/XHTML resources is also poor upgrade practice because shipped web resources can be replaced during patches and version upgrades. Supported configuration objects, message catalogs, CSS customization, or plugin UI mechanisms provide safer and more maintainable extension points.

References/topics: IdentityIQ Engineer — UIConfig, ColumnConfig, message catalogs, CSS, branding, upgrade-safe UI customization.