If true, this instance results in an OCP editor sub space in the technical model which is registered in respective spaces via ocp.

Applies to

▸ Model level: ☐ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If provided, this property defines the name of a class complying to VUI space requirements which is used as the ADO space instance which defines the contents and subspaces of the main editor space in the UI.

If not provided, the class 'GeneralSpace' is used for that purpose. To implement your own space class, it might be easiest to derive that class from 'GeneralSpace'.

Applies to

▸ Model level: ☐ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If true, this instance results in an OCP singleton sub space in the technical model which is registered in respective spaces via ocp.

Applies to

▸ Model level: ☐ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

A list of spaces which contain the respective Editor- or SingletonSpace for this class. Defaults to "MainSpace" and "SubSpace".

See XMCoreOCPs/SubSpace how to configure which spaces are generated.

Applies to

▸ Model level: ☑ logical model ∙ ☑ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

An aggregate, which is inserted into the ObjectEditorSpace for each class as operations (or likewise frame items). Defaults to "BrowseTransactionStarter".

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to the elements in the browse table.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to transactions in the main editor transaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to the elements in the CreateTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to the elements in the EditTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to the elements in the DeleteTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a view, which is applied to the elements in the InstanceTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional style of InstanceTransaction itself.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a retriever filter, which is used in the browse table instead of the default retriever filter.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of a retriever configuration, which is used in the browse table to initialise the respective retriever filter.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional interface of an alternate retriever, which is used in the browse table instead of the default retriever. Must be used in conjunction with BrowserTableRetriever

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional name of an alternate retriever implementation, which is used in the browse table instead of the default retriever.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional expiry time in milliseconds, after which the result in a browser table is automatically re-retrieved when requested. Expiry '0' means no caching keeps place but result is always re-retrieved, expiry '-1' means the result is kept infinitely until the retrieve operations is executed explicitly. The default is '-1'.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional list of Toolkit factories to create tools that are attached to the browser.

See Stereotype

Toolkit

and JavaClass

Toolkit

.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Alternate Name in Browser for edit operation.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Alternate Icon in Browser for edit operation.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a browser transaction instantiates and starts if the edit button in the browser toolkit is pressed.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a browser transaction instantiates and starts if the move button in the browser toolkit is pressed.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Alternate Name in Browser for open operation.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Alternate Icon in Browser for open operation.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a browser transaction instantiates and starts if the open button in the browser toolkit is pressed.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a browser transaction instantiates and starts if the delete button in the browser toolkit is pressed.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optional list of Toolkit factories to create tools that are attached to the instance transaction.

See Stereotype

Toolkit

and JavaClass

Toolkit

.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If this class is a

Transaction

, an optional list of Toolkit factories to create tools that are attached it's instances, via the corresponding Transaction-OCP.

See Stereotype

Toolkit

and JavaClass

Toolkit

.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If this class is a

Transaction

, a

SelectionToolkit

(factory) is added via the corresponding Transaction-OCP.

See Stereotype

Toolkit

and JavaClass

Toolkit

and XMAssembly/SelectionClass.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Optionally specifies the class that a XMAssembly/SelectionToolkit matches to.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

In factories of toolkits, target instances are passed and checked whether a toolkit shall be created for these intances or whether not. In conjunction with stereotype "ToolkitForClass", this property here evaluates to a set of static class names suitable for an "instanceof" check and is used to match against those instances.

If a check against a dynamically obtained class is required, use XMAssembly/ToolkitClassesConstraint.

A toolkit is created, if the instances belong to the classes.

Note: normally, each entry evaluates to a static class name that is suitable for an "instanceof" check. In addition, the entries may contain a placeholder "${target}". If they do, this placeholder is replaced by the respective target instance and the entry then needs to evaluate to a complete condition to be checked, and no "instanceof" is prefixed.

E.g., an entry can contain "my.cool.Thing", which denotes some existing class. Alternatively, it can contain "${target} instanceof my.cool.Thing", which effectively specifies the same check. This second notation is useful if more than one class is allowed as a target, then, a more complex expression can be formed with "&&" and "||", like "${target} instanceof my.cool.ThingOne || ${target} instanceof my.cool.ThingTwo". Note that in this case the placeholder "${target}" can be used multiply in the expression. Note also, that the code than needs to supplied as "JavaCodeUsageContextTemplate", not just "JavaCodeTemplate", since the latter defaults to DeclarationContext.

XMAssembly/ToolkitClassesConstraint

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If provided, this is the minimum number of target instances that must be given to a toolkit for a match.

If not provided, the number of XMAssembly/ToolkitClasses is used as the minimum number.

If the number of XMAssembly/ToolkitClasses is greater than this explicitly provided amount, the additional ones are considerd optional and the classes are only optionally checked.

If the number of XMAssembly/ToolkitClasses is lesser than this explicitly provided amount, the toolkit will never match.

XMAssembly/ToolkitClassesConstraint

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If present, this condition must be matched in addition to XMAssembly/ToolkitClasses to create a respective toolkit.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If present, this condition must be matched by the target if this toolkit is a selection toolkit. I.e., the condition is checked if and only if the target is an instance of class Selecion and in this case the check is required to be true.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

If present, this condition must be matched during toolkit check to create any toolkit at all for the examined objects.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a

ToolTransactionStarter

operation starts, if it is invoked on an instance of the XMAssembly/ToolkitClasses.

See also XMAssembly/ToolTransactionTargetAttribute and XMAssembly/MultiToolTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☑ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of an attribute in a XMAssembly/ToolTransaction. It is used by the

ToolTransactionStarter

operation if the transaction is instantiated. This attribute will be set to the target for which the Toolkit was created, which is an instance of the XMAssembly/ToolkitClasses. In other words, the toolkit is or is used as a plain Toolkit (in contrast to MultiToolkit).

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☑ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of the aggregate which a

ToolTransactionStarter

operation starts, if it is invoked on a

Selection

.

See also XMAssembly/MultiToolTransactionTargetAttribute and XMAssembly/ToolTransaction.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☑ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

Name of an attribute in a XMAssembly/ToolTransaction. It is used by the

ToolTransactionStarter

operation if the transaction is instantiated. This attribute will be set to the target for which the Toolkit was created, which is an instance of

Selection

. In other words, the toolkit is or is used as a MultiToolkit.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☑ operations ∙ ☐ association ends ∙ ☐ states

Name of a method of the (in this case) one and only member of the XMAssembly/ToolkitClasses list. This method acts as a factory and returns a transaction. Such newly created transactions are used by a

ToolTransactionStarter

operation, if it is invoked on an instance of the respective XMAssembly/ToolkitClasses list entry.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☑ operations ∙ ☐ association ends ∙ ☐ states

If defined, this attribute serves as a slot for items of this workspace, which are attached to the Workspace from it's Toolkits.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☑ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

If defined, this attribute serves as additional slot configuration, to enabled tools to setup more thant one parameters for example.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☐ classes ∙ ☑ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

A map of additional, optional, named regular expressions that must match against the classname of instances to enable the standard BrowseToolkit and it's various tool options.

Valid options are:

• OpenIncludedClasses
• OpenExcludedClasses
• EditIncludedClasses
• EditExcludedClasses
• DeleteIncludedClasses
• DeleteExcludedClasses
• MoveIncludedClasses
• MoveExcludedClasses

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Evaluation context: ---

A list of aggregates, which are inserted into the ObjectEditorSpace for each class as operations (or likewise frame items). Defaults to "CreateTransactionStarter".

Optionally, each starter aggregate is accompanied by a state condition, which must be true for the respective starter to be visible. If a XMAssembly/ObjectEditorTransactionStarterController is specified, the condition is checked against this controllers' state. If no controller is specified, the starter itself is expected to be stateful and it's state is used for the check.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

An aggregate, whose state is used to check whether a certain ObjectEditorTransactionStarters is currently visible.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

The name of the respective ObjectEditorSpace entry ("menu entry") specified as a dynamic string.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

The name of the respective ObjectEditorSpace entry icon ("menu entry icon").

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

A list of factories that can be used by the user to create instances of this class.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

A list of subspaces contained in the (optionally generated) MainSpace (OCP). If empty, as a default the editors of the respective bundle will be contained directly in the MainSpace.

Likely to be deprecated in the near future, use SubSpaces property instead.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Normally, if MainSubSpaces are defined, no editors are automatically included in the MainSpace. If this property is true, these editors will always be included, even if MainSubSpaces are defined.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☐ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

A list of superspace/subspace relations which determines which subspace is contained in which super space.

See XMCoreOCPs/SubSpace how to configure which spaces are generated.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Determines the content which is contained in the given space (i.e. a class with stereotype

ApplicationSpace

)

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Determines the items which are contained in the given space's frame

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Determines content which is placed at the head of the main editing page for the respective class (typically the "EditorTransaction" page for that class).

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states

Determines content which is placed at the tail of the main editing page for the respective class (typically the "EditorTransaction" page for that class).

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☐ packages ∙ ☑ classes ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states