Case Action Properties

Case Action Reference
Tab Property Description
General Label Label associated with the case action. You can change the label if necessary.
Case Action

Select Case class that this action applies to...: Case Class: Allows you to select the case class to which the case action applies.

Select Case States that this action is visible for...: Once a case class has been selected this provides selection of the case state attribute values that the case action should be visible for at runtime. All States switches off the case state value filter. Specific States enables selection of case states using checkboxes.
  • No Case State Set means that the case action will be visible when none of the defined case states are set for a particular case.
  • Other states displayed are the values defined for the Case State enumeration for the selected class.

Select the privileges required to use this action... Provides selection of one or more organization model privileges that a resource must have to be able to see and use the case action at runtime. If no privileges are selected then all resources can see and use the case action.

  Process Interface Lists the location and name of the process interface implemented by the selected case action. Specifying a process interface allows the dynamic selection of sub-processes at runtime. For more information, see Process Interfaces .
  References Lists any processes or tasks that use the selected case action, and the contexts in which the data is used. Click Go To to display the referencing object. This field helps prevent deleting a case action that is used elsewhere. Note, however that a case action may be used by other packages, and these references cannot be displayed in this field.
Description   Optional textual description of the activity.
  Documentation URL The Documentation URL controls allow you to launch a web browser for the given URL (you can use the actual Documentation URL: label or the browser button).

The browser is opened either in TIBCO Business Studio (in the editor pane) or in an external browser according to the user defined settings (Preferences > General > General).

Destinations   Enter the target environment for the case action. When you save the case action, validation is performed according to this setting:
  • All case actions are validated for BPMN - additionally, other destinations can be selected to validate the case action for use in specific environments
  • If you select BPM, the case action will be validated against TIBCO ActiveMatrix BPM 3.x.
  • If you select Simulation, case actions created under this project will be validated for simulation in TIBCO Business Studio as well as for BPMN correctness.
  • If you do not select a destination environment, basic BPMN validation will be performed.
Participants   Provides the Label, Name, Type, and External Reference for all participants used in the case action.
Parameters   Provides information about all parameters defined in the case action.
Note: When a case action is auto-generated from a case class, then you auto-create a case reference parameter with the mode set to IN.
Data Fields   Provides information about all data fields defined in the case action.
Note: When a case action is auto-generated from a case class, you auto-create some data fields.
Appearance Connection Routing The connection routing style is used to change the appearance of entry and exit connections on activities such as events and gateways.

The connection routing style can be one of the following:

  • MultiEntry/Exit Point(default). This means that connection points are to/from the same activity side, and are automatically spaced out from the centre of that side.
  • Single Entry/Exit Point.This means that all extry and exit points are amalgamated into one entry point and one exit point on each side of an activity.
  • Uncentered On Tasks. This means that entry and exit points on task activities are automatically positioned towards the corners when the source/target object is not in-line. This is the equivalent default from earlier versions of TIBCO Business Studio.

With all the above styles, it is still possible to manually set a specific entry / exit point by dragging the end of a connection to the required position on an activity's border (rather than the center of the object).

Extended   Extended attributes can be used to add extra information to the schema. Click Add to add a new extended attribute.

Modify the following:

  • Name - provide a name for the attribute (you cannot include spaces in the name).
  • Value- add any text for the value.
  • Escape Body- Select this checkbox if you want the parser to interpret the contents of the body attribute as text rather than XML (you do not want the parser to interpret symbols such as < or >). If you are entering XML, do not select this checkbox so the parser can validate the body attribute.
  • Body- enter whatever text or XML you want to make up the body of attribute.
Resource BPM Fault Configuration

System Error Action

BPM only:

This configures how an instance of this case action behaves at runtime if an executing activity encounters an unexpected error condition:

  • (server defined default)- use system wide default behavior (see "Configuring Error Handling Behavior for Process Instances" in the TIBCO ActiveMatrix BPM Administrator’s Guide for how to define this).
  • Halt- process instance halts. You can then use Openspace, Workspace or the BPM API to investigate/fix the problem.
  • Error- process instance fails immediately and cannot be resumed.