-
Notifications
You must be signed in to change notification settings - Fork 0
Instance Service
Figure 1: Instance Service An Instance Service can be seen as an action of a Data Type. For that reason, Instance Services can only be defined as a part of a specific Data Type. Like any other Service an Instance Service can be used as Modeling Block inside of Workflows.
Instance Services can be realized as a Coded Service or as a Workflow. If realized as a Coded Service the modeling of the Instance Service leads to the modeling of a Coded Service. If realized as Workflow, the Instance Service simply references an existing Workflow with a matching signature.
If the Instance Service shall not or later (in an inheriting Data Type) be realized, it can be declared as Abstract. If the Data Type's Base Type already defines Instance Services, there is the possibility to override inherited Instance Services. This leads to Dynamic Polymorphism.
See Add an Instance Service to a Data Type
An Instance Service can be renamed from inside the Factory Navigation by using the Service's context menu and choosing Move/Rename. The following dialog will guide through this process.
With this action, all references to the moved object will be adjusted.
To remove an Instance Service, you have to open its Data Type and remove it from there.