In the legacy Data Security Step (SME), we could construct filter expressions using multiple conditions, logical operators, functions, conditional logic, and session variables. We could also apply the same filter expression to multiple logical objects.
In the new interface, we would like to understand how the following scenarios can be implemented:
- Multiple conditions and conditional logic: How can we implement logic equivalent to CASE WHEN, nested conditions, and combinations of AND and OR?
- Session-dependent security: How can we dynamically filter data using the logged-in user’s person ID or other session variables, equivalent to VALUEOF(NQ_SESSION.HCM_PERSON_ID)?
- Department exclusions and role-based exceptions: How can we restrict records for specific departments while allowing exceptions for designated user roles?
- Multiple logical objects: How can we ensure consistent application of the same security rules across Worker dimensions, Assignment facts, and other relevant subject areas?
If certain expression capabilities available in the legacy approach are not supported in the new method, please clarify the recommended alternative architecture and any limitations we should consider.