Actions

To my knowledge, there is no limit.

I have yet to hit a limit. I often create an app container that holds a lot of actions. Current app working on has almost 40.
I do like to split them up though, if you have users that have access to a lot because then they can use the application names on the left as filters. So I will name my applications for the type of activities (I.e. System Administration, advanced Reporting, etc. )

There are no such limit, but if we have multiple actions for a particular user or group then it's a good idea to have the filter, and this we can achieve by segregating Actions into multiple Applications.

There is no limit to the number of actions. If your application is having multiple actions and you want to restrict the view of actions to defined set of users. I would suggest to do so in the process model security.

yes, mariod , i also think, this is right way to segregate different actions to defined set of users.and there is no limit for defining actions in an application.

Is there a way to use a rule instead of user group to control the access to the action?

Hello ,

We can't use the rules for the actions. Only way is the Group security
Thanks
Sahil

Hi,

I think, there is no limitations for use of actions in application

Hi Mario -

There's a flexibility trade-off to consider here if you have Tempo users.
Having different application-specific "navigation" applications provides greater flexibility than what you are proposing, (again for Tempo):

Two things come to mind.
(1) Users won't be able to take advantage of application filtering on the Actions tab if all actions are contained in a single application.
(2) There's a loss of granularity to the benefit of un-publishing applications specifically for the purpose of hiding actions. If there were a need to hide actions associated with one and only business application, but all actions are in one application, your only option is to hide or show all actions.