Hello DIPAKPATEL,

As per my knowledge It is not possible to disable a navigator option based on permission sets. But we can prevent the user from doing any configuration/change to the navigator by not giving him/her the “EE_NAV_CONFIG” permission set.

But this completely locks the navigator for that user so revoking this means that the user cannot perform any other changes to the navigator either. You can create a dummy user on a test environment and verify whether this allowed to achieve what you trying to do.

Best Regards,

Dasun

HI Dasun,

Thank you for this reply. It’s helpful to me.

Thank you.

Hi Dipak!

Instead of hiding the whole navigator config, you could just deal with the change after it has happened.

You could schedule a custom database task to periodically remove the Hidden entries from every profile - but will restore every single hidden item for all users unless you modify the query

DECLARE

CURSOR get_Hidden_Values IS
select a.profile_id, a.profile_section, a.profile_entry
from ifsapp.fndrr_client_profile_value a
where a.profile_entry = 'Hidden';

BEGIN
 FOR rec_ IN get_Hidden_Values LOOP 
 ifsapp.fndrr_client_profile_value_api.Delete_Value__(rec_.profile_id, rec_.profile_section, rec_.profile_entry);
 END LOOP;
 COMMIT;
END;

Another option would be to create an event for when the FNDRR_CLIENT_PROFILE_VALUE_TAB is updated with a new entry value of ‘Hidden’ and then rollback the transaction.

 

This table is only updated when the profile is saved - so will not actually trigger when the RMB is performed.

The issue is that this will rollback the entire profile save so if the user has made any other change in that session (such as moving a column or adding a shortcut) then these will not be saved either.

To top it off, an error message come ups when the user closes down the application (The user will only be able to Discard Changes as the Retry option fails and redisplays the prompt)

Regards, Callum

Hi Callum,

Thank you for your reply.