Tip: Scope Action Namespaces

Actions in plugin elements are scoped by the name of the element in the app page that the developer specified. However, for bare client-side and server-side plugin actions it is easy to end up with name collisions across multiple plugins. To provide a partial alleviation of this difficulty for developers always make the first field of any bare action an information field that contains the full name of plugin. This way at the very least when the action is dropped into a workflow the developer can readily see which plugin it originated from.

1 Like