Changing Action's Owner Context
An Action belongs to the origin (or owner) context that you indicate while creating the action. What this means is that the views and elements required in the action logic are served by the origin context.
At times, as part of refactoring, you may need to move an action from one Context to another. Moving an Action involves addressing all its dependencies. An Action may typically have following dependencies on the Owner Context:
- Elements from the context's views
- Other actions from the context, which this action is calling
- Other actions in the context may be calling this action
When you try to move an Action, the system prompts for all these dependencies making sure the process is smooth and error free. Follow the alerts in the message and complete the process.
How to move an Action
You can accomplish this by clicking on the Owner Context name in the action sidebar.
You are presented with a screen to choose any other dependencies that you would like to move. Note that an Action can be moved to a different context, only if its dependencies are also moved to the new context at the same time.
In case there are unresolved dependencies, you are presented with a detailed error message. Review these dependencies and try the operation again.
Comments
1 comment
so far I found impossible to transfer actions between context when there are 'unresolved dependencies' regarding elements.
I tried to move the relevant views at the same time, created elements with the exact same properties. I think information is missing in this article
Please sign in to leave a comment.