XMOM Object
Objects composing an XMOM are called XMOM Objects. To watch all XMOM Objects contained in an XMOM, use the Factory Navigation of the Xyna Process Modeller and choose the Runtime Context of the desired XMOM.
| Name | Description | Example |
|---|---|---|
| Workflow | Composition of Process Steps | Workflow |
| Data Type | Declaration of properties and actions |
|
| Exception Type | Declaration of properties and actions to classify errors |
|
| Service Group | Group of related Coded Services | Service Group |
| Coded Service | Service as Java implementation | Coded Service |
| Instance Service | Service as constituent of a Data Type | Instance Service |
XMOM Objects have to be created inside of the Xyna Process Modeller. There are several kinds of XMOM Objects (see above) while each has to be created in its own special way. For this, see the respective article.
Once saved, an XMOM Object is part of the XMOM belonging to the current Workspace. Everyone can use and edit it by working with this Workspace.
To edit an XMOM Object, open its context menu and select Open in new Tab. You can open an XMOM Object from nearly wherever it is displayed, e.g. from inside of a Workflow, out of the Factory Navigation or the Search.
If someone is editing an XMOM Object, everyone else can just watch this object without being able to edit it (cf. Collaborative Modeling).
The Deployment of an XMOM Object means that it is prepared for execution within the Xyna Factory. For some XMOM Objects you have the option to save them without deploying them. Only deployed objects can be used by executed Workflows. So if you created an XMOM Object and saved it without deploying it, there will be an error while using it during execution.
If you edit an already deployed XMOM Object and only save your changes without deploying the object again, the last deployed state of the object will be used during execution. To cope with this kind of problems all deployable items are monitored inside the Deployment State overview of the Xyna Process Modeller or the Deployment Items section of the Xyna Factory Manager.
If you don't know the exact name of the object but you know it is part of a specific Runtime Context, use the Factory Navigation and explore all XMOM Objects inside.
If you only know parts of the fully qualified name of the desired XMOM Object (such as the name), use the Search to find all XMOM Objects matching your input.
If you know there is an XMOM Object and you know its name or its path but you don't know the Runtime Context, it is part of, you can use the Search while trying different Runtime Contexts or do the following: Create a Runtime Context that includes all other Runtime Contexts as a Requirement. Select this Runtime Context for the Factory Navigation or the Search. Open the found XMOM Object with Details to see its Runtime Context.
A good way to export an XMOM Object from out of a Workspace is to create an Application Definition only containing this XMOM Object (and thus all of its dependencies). Go to the Workspaces section in the Xyna Factory Manager to do this. Check and, if necessary, fix the Runtime Context Problems in the details of the Application Definition and the Deployment State of each contained XMOM Object inside of the Deployment Items section in the Xyna Factory Manager, before you continue. Create an Application out of the Application Definition and export it.
To import an XMOM Object the same way, import the Application containing the XMOM Object and add it to a Workspace as a Requirement. This Workspace can use the XMOM Object now.
To remove an XMOM Object, you have to select the desired object inside of the Factory Navigation or Search and select Delete from XMOM from its context menu (open with double or right click). For more detailed information see the Remove ... section inside of each respective XMOM Object.