Info message is not shown when action to add user to group is aborted.

[Kalyani35]

Hi all,

we want to restrict the users to be added to group if certain conditions are met. we also want to show error message when that happens. 

With the before insert business rule we have written, it does not allow user to get added to that group however that info message is not displayed. This happens only in case when we are trying to add user to group by using edit button on User related list on Group form. Please see screenshot below

If we try to create group-user relationship on sys_user_grmember table directly then the BR runs as expected and info message is also shown. 

How this can be solved. Anyone faced issue like this?

if (condition) {

     gs.addErrorMessage("User is not allowed to be added to this Group");

     current.setAbortAction(true);

    }

Thanks!

[Brad Bowman]

One thing that jumps out from your screenshots is that the New button is usually not displayed on this Related List as it will create a new user, which is not the usually how that should be done.  Right-click the Related List column headers and choose Configure > List Control, then check the box for Omit new button.  While you're in there notice the script field for Omit edit condition, or add it to this form via Form Layout.  Depending on your conditions, this is the first choice of where to add them, so that the user doesn't even see the Edit button.  If you are unable to do this for your conditions / use case, your Business Rule to show the error message is fine.  What's preventing the message from being displayed back on the Group form is the info message that tells you (erroneously in this case) that the "job to add or remove role(s) from user(s) of group has been queued".  In lieu of finding whatever it is that is generating this message and changing it to not show the message (I couldn't find it) you can turn off the process that it is referring to - something that was added a few releases ago to run the job in the background instead of the foreground.  Set the value of the system property named glide.ui.schedule_slushbucket_save_for_group_roles to false and the same job will still run, it just won't display that message telling you it's running (because it's not really anyway since the add was aborted) and that means that your Business Rule error message will be displayed!

[Prabhu9]

Hi @Kalyani35 ,

I've a similar requirement! Was this solved ? Could you please share the solution here if it had worked ? 

[Sourabh Tarlekr]

Hi @Kalyani35 

Make glide.ui.schedule_slushbucket_save_for_group_roles property as false on sys_properties form and then try again.

When this property is true, job runs in the background to add or remove users hence preventing to run the BR.

Please refer How to adjust granting of roles and groups for detailed explanation.

Regards,
Sourabh

[Sourabh Tarlekr]

Hi @Kalyani35 

Checking if you got a chance to work on the solution given?

Regards,

Sourabh