Symptom
UI rule configured to prevent users from editing the fields is working for some users and as expected and others not.
Environment
SAP SuccessFactors HCM Core
Reproducing the Issue
- Create or use an MDF object with a UI rule that sets fields to read-only based on a condition (for example, a status value).
- Ensure the rule’s condition references a specific MDF field..
- Assign role-based permissions (RBP) so that some users do not have permission to view the field referenced by the UI rule.
- As a user without permission to the referenced field, open the MDF object in People Profile and attempt to edit.
- Observe that the fields remain editable for these users, while users with permission to the referenced field see the fields as read-only.
Cause
The field referenced in the UI rule is not present on the UI for affected users due to RBP overrides. Because the referenced field is not available, the rule condition is not met and the UI rule does not run as expected.
Resolution
- Identify the field(s) referenced in the UI rule conditions.
- Update role-based permissions so affected users have at least view access to the referenced field(s), ensuring the field is available on the UI for those users.
- Save permissions, run an MDF object definition to database sync if applicable, and clear browser cache or reload the page.
- Re-test as the affected users to confirm the UI rule now applies and fields are read-only as intended.
See Also
KBA 3669922 - UI rules are not working properly on a custom MDF object with a high number of fields
Keywords
mdf, ui rule, business rule, read-only fields, editable fields, role-based permissions, rbp, field-level permission, field visibility, people profile, mdf ui, rule condition, configure object definitions, ui group, visible fields count , KBA , LOD-SF-MDF-UI , UI Config, Layout & Rules , LOD-SF-MDF-PPX , MDF on New People Profile , LOD-SF-MDF-RBP , RBP Permissions on Objects , Problem
SAP Knowledge Base Article - Public