Configurable modifier

The configurable modifier is a plug-in that you can use to have WSRR create, modify, or delete objects automatically, in response to a user operation.

You configure the configurable modifier using XML; you do not have to write any Java™ code.

Note: You can use the UML modelling tools in WSRR Studio to edit some of the configurable modifier settings; the configurable modifier settings that you can edit in WSRR Studio are those that make an object governable at creation time. For more information, see Adding a lifecycle to the configurable modifier configuration.

There are two main components in the configurable modifier, action configurations and triggers.

Action configurations

An action configuration defines the actions that you want WSRR to perform automatically. You can define one or more of the following actions in an action configuration:
  • Create an object.
  • Delete an object.
  • Add, modify, or remove an object property.
  • Add, modify, or remove a relationship on an object.
  • Add or remove an object classification.
  • Make an object governable.
  • Apply a state transition to an object.
  • Remove governance from an object.

Triggers

A trigger identifies a type of user operation, as a result of which you want WSRR to perform the actions defined in a specified action configuration. The types of user operation that can automatically trigger the actions in an action configuration are as follows:
  • Creating an object.
  • Updating an object.
  • Deleting an object.
  • Making an object governable.
  • Applying a state transition to an object.
  • Removing governance from an object.
In addition, you can define further conditions, which the entity on which the user operation is performed must satisfy for the action configuration to be run. The types of condition that you can define are as follows:
  • The entity is of a specified object type.
  • The entity is of a specified business model type.
  • The entity has a property of a specified name, and, optionally, with a specified value.
  • The entity has a relationship of a specified name, and, optionally, with a specified set of relationship targets.
  • The entity has a specified classification.
  • The entity belongs to a set of objects defined by an XPath expression.

Example 1

Trigger conditions
  • A user creates a WSDL document object.
  • The name property of the WSDL document object contains the string "StockControl".
Resulting actions
WSRR automatically adds the "Logistics" classification to the WSDL document.

Example 2

Trigger conditions
  • A user applies the "Approve" transition to a WSDL service object.
  • The WSDL service object has a "cost_of_use" property with a value greater than 1000.
Resulting actions
WSRR automatically adds the WSDL service object to the targets of the "Owned Services" relationship on the "Finance Management" organization business object.

You define trigger conditions in a triggers file, and you define action configurations in an actions file. These files, and the ways in which you load and modify them, are described in the following subtopics:

Parent topic: Configuring the WSRR provided plug-ins