Best practices when using Containers

Question

I'm would like to understand better how I can use the Containers. I haven't found much in the documentation.

For most roles it seems like a place to categorize items.

I'm interested in the Custom Commands location mostly.

I'm wondering if it is useful to use containers for specific instances. When I put a custom command in a container in the web interface it shows the name of the container as well.

Example: Custom Command (folder name)

In my case I was thinking of the Deprovision custom action. In general I can use it for most of my locations but I might want to create two instances of the Deprovision command. To do that I'd need to create a container to copy the command into. I'd like to keep the name Deprovision without the additional folder name. Is that possible?

Is it possible to use the container to give permissions to all the command inside? (what I know so far probably not)

So in general a best practices for containers would be helpful.

Thank you

Answer 1

Hello,

I 'd like to keep the name Deprovision without the additional folder name. Is that possible?

Whenever a Web Interface action executing a Custom Command is created, the action name can be anything you need. It can even be not related to the command name itself. At the same time, if you have two Custom Commands with the same name, their container name will be present in the brackets after the command name when the command is displayed in the left pane. In the example below, Custom Commands Deprovision (My Container) and My Command are both located in the same container, but only the Deprovision one has the container name displayed. This works only for Custom Commands with same names. If a command name is unique the container name is not displayed.

Is it possible to use the container to give permissions to all the command inside?

Unfortunately, there is no such possibility.