AndroMDA JBPM Cartridge Profile

This profile contains all elements that can be applied on the model used as the MDA transformation process. These elements are specific to the AndroMDA JBPM Cartridge component.

Stereotypes
Stereotypes are the names you sometimes see appear in UML diagrams, they typically look like <<MyStereotype>> and can be applied on any type of UML model element.
Tagged Values
Sometimes it happens you want to add information to the model but there is no clean way of doing it. In those cases you may want to resort to tagged values, but these cases should be considered with caution. A tagged value is something extra, something optional, and the application should run fine without them.

Business Process(Back to Stereotypes)
Applied on: use-case
Instructs the jBpm cartridge to process the contents of this use-case.
Before Signal(Back to Stereotypes)
Applied on: call-event
Will specify that the event on which this stereotype has been modeled is of type before-signal.
After Signal(Back to Stereotypes)
Applied on: call-event
Will specify that the event on which this stereotype has been modeled is of type after-signal.
Node Enter(Back to Stereotypes)
Applied on: call-event
Will specify that the event on which this stereotype has been modeled is of type node-enter.
Node Leave(Back to Stereotypes)
Applied on: call-event
Will specify that the event on which this stereotype has been modeled is of type node-leave.
Task(Back to Stereotypes)
Applied on: call-event
Will specify that the event on which this stereotype is to be considered a task. The event on which this stereotype is placed usually is a state node (do not confuse with action state).
Timer(Back to Stereotypes)
Applied on: call-event
The underlying event will represent an action that will be executed on a timely basis. The usage of this stereotype is usually supported by means of a set of tagged values.
andromda_process_jbpm_assignment_expression(Back to Tagged Values)
Applied on: swimlane
Specifies an assignment expression as a bean-shell script.
Allowed values for this element:
  • Any valid bean-shell script
andromda_process_jbpm_timer_repeat(Back to Tagged Values)
Applied on: <<Timer>>
After a timer has been executed on the duedate, this tagged value specifies the duration between repeating timer executions until the node is left. If yes or true are specified then the value of duedate is used.
Allowed values for this element:
  • yes
  • true
  • a duration as defined by jBpm
andromda_process_jbpm_timer_duedate(Back to Tagged Values)
Applied on: <<Timer>>
The duration that specifies the time period between the creation of the timer and the execution of the timer. This can be expressed in business hours, minutes, etc...
Allowed values for this element:
  • a duration as defined by jBpm
andromda_process_jbpm_timer_transition(Back to Tagged Values)
Applied on: <<Timer>>
The transition to take once the timer finishes.
Allowed values for this element:
  • the name of one of the transition going out of the state onto which this timer has been modeled
andromda_process_jbpm_task_blocking(Back to Tagged Values)
Applied on: <<Task>>
Denotes whether or not this task should be blocking.
Allowed values for this element:
  • true (default)
  • false