Action Group and Action visible expressions

@Lisa Fields
There isn't a simple way of doing this, but I think you might be able to write an expression to handle this. There is a global function called ‘Globals.CurrentAppUserGrantedTask(taskID)’ which might be able to be used in the ‘visible' field under the actions group.

I've not tested this properly but I've been able to see that it returns a value when used in the caption so in theory this should work.

You'll need to start by finding the ID of as task which is in the action group and which the user group you want to hide the action group from does not have permissions to. To do this toggle page designed on and search for the name of the action. Once you have found it then copy the ID attribute > open the properties of the action group > open the expression window for the ‘visible’ field > then add this expression from the globals folder - = Globals.CurrentAppUserGrantedTask(taskID) > Replace taskID with the ID you copied (contained in “”) and then save.

If you can impersonate the user this should allow you to test it. This is a bit of a workaround so there might be an easier way of doing this. Hopefully this actually works.

@Lisa Fields it was hard to explain. But essentially you can't permission the action group like you can the actions. But if there is an action which uses a catalog object e.g. data form which as user does not have access to you can write an expression to hide the action group based on that.

In theory this would mean that instead of the user still seeing the action group without the task they do not have permission for, they would not see the actions group at all.

This expression - Globals.CurrentAppUserGrantedTask("332c66b6-11ac-49c9-9079-6ad0a21dce23") returns True or False depending on the permissions the current user has. If a True is returned then the action group should be visible and if a False is returned then it shouldn't be.

If you don't have any actions in the page users don't have permission to then you would need to find one being used in another page for the same purpose. Essentially I think you can use any task ID for this purpose. Hopefully that makes sense?

@Lisa Fields Yes I think so. I've not properly tested as I mentioned though so you'll need to give it a go