When you are working with an Action, you may have come across Owner and Origin Contexts. This article highlights the difference between these two important attributes of an Action.
Owner Context indicates the Context which actually owns the Action. This essentially means the Elements and Views required for the Action are managed by this Context.
You select the Owner Context of an Action when you create the Action. However, if necessary, you can change the Owner Context later as well.
Origin Context refers to the set of Contexts in which this Action is applicable. For example, if you consider a typical Logout Action in many applications, it may be possible to logout of the application from multiple pages. Even though the Logout Action may have been defined (owned) by one of those Contexts, it is "applicable" in all these given Origin Contexts.
Here is more about sharing an Action with other Contexts and setting applicability.
Owner Context is always one of the Origin Contexts.
You will have only one Owner Context for an Action, but there could be multiple Origin Contexts.
Changing Owner Context
You can accomplish the change of Owner Context in the following ways:
1. From the Action, by clicking on "Owner Context" in the Info sidebar.
2. From the current Owner Context, by clicking on "Move Actions/Views".
If you need to change the Owner Context of an Action, all the dependencies must be taken care of. As discussed before, Owner Context provides all the Elements, Views, and other dependencies required for the Action. Hence moving an Action to another Context's ownership means that these dependencies must be moved along as well. Here is an article with details on how to address this change-impact.