Conditional UI like Prashant mentions is how you can make specific fields visible based on a condition (site, work type, PM or not, etc.). Something to be aware of is the way conditional UI is evaluated, you still need to tie a signature option & reference a security group for the conditional UI. And the conditional UI for that group & option has to be consistent throughout that application. IE if you tie a condition to READ signature option on the ASSETNUM field and hide the ASSETNUM field for GROUP1, you can't later use the READ signature option on the LOCATION field and make the LOCATION field visible for GROUP1. The visible flag you set in the conditional UI would apply everywhere you have it referenced. This often leads to customers developing their own signature options for handling conditional UI sections which means you need to ensure you grant the new permissions you create to the necessary security groups or they'll never see it.
As you get to MAS and can start utilizing our new role-based applications, the configuration is significantly more flexible. You can still use signature options if you want (and can even use signature options from other applications), but you can also make it simple conditions that apply to everyone (no longer checking for specific security groups). For example, checking that the siteid is BEDFORD and conditionally showing or hiding based on that criteria alone.
------------------------------
Steven Shull
IBM
------------------------------
Original Message:
Sent: 10-15-2023 22:14
From: Danny Richardson
Subject: HIDE FIELD FOR CERTAIN SITES OR ORGANIZATIONS?
Hello all,
I believe you can hide fields for specific security groups, but is it possible to hide a field for a specific Site within an Organization, or for a specific Organization from other Organizations if the system is set up that way?
Thank you
#Administration
#Customizations
#EndUser
#EverythingMaximo
#Security
------------------------------
Danny Richardson
------------------------------