The Properties View shows you detailed information about the currently selected object and allows you to specify the characteristics of an object.
To see this view, select Window >
Show View >
Properties or
Window >
Show View >
Other, then expand the
General folder and select
Properties. To view property information, you must have an object selected.
|
|
|
|
|
|
|
|
|
|
|
Select the Inline sub-process during Process Package Optimization checkbox so that at runtime, the objects such as activities and events contained in the reusable sub-process are brought into the top-level process and executed there, rather than by making a call to the sub-process.
|
|
|
|
|
|
|
|
|
|
|
|
•
|
If you select BPM, the Process will be validated against TIBCO ActiveMatrix BPM 2.x.
|
•
|
If you select Simulation, processes created under this project will be validated for simulation in TIBCO Business Studio as well as for BPMN correctness.
|
|
|
|
|
|
|
|
|
Retain Familiar (Manual and user tasks)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
•
|
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.
|
|
|
|
•
|
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.
|
|
|
|
•
|
(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.
|
See the BPM Retry Action property on the Reference tab in Activity Properties for more information.
|
|
|
|
|
|
This is used to suppress problems markers for the ’No migration point activities in the process’ Problem. It gives you the choice of validation, suppressing the error until the next process flow change, or suppressing the error until a manual reactivation via Resource properties.
|
|
|
|
|
|
|
|
|
Select from Standard Loop, Multiple Instance Loop, or Ad-Hoc. For more information, see User Tasks and Pageflow Processes.
|
|
|
|
|
|
For example, Task, User Task, Service Task, and so on, (see Creating References). If you select Reusable Sub-Process, you must browse to locate the sub-process.
|
|
|
•
|
No Form URL Select this option if you do not want to display a form for the user task.
|
•
|
User Defined Form Select this option if you want to use the F orm Identifier field to point to a specific URI (for example, if you authored a form outside of TIBCO Business Studio). Manually enter the URI. TIBCO Business Studio cannot validate the URI, so ensure it is correct. If you select this option but do not specify a URI, upon export a standard form is created.
|
•
|
Form Use this option if you have created a form using TIBCO Business Studio Forms. Either automatically create a form (in which case the Form field is completed automatically) or browse to select a form from a Forms special folder.
|
•
|
Pageflow Select this option if you want the user task to call a pageflow. Browse to select a pageflow process. When deployed, the specified pageflow process is run when the work item associated with the user task is opened.
|
|
|
|
|
|
(Activities of type Embedded Sub-Process)
|
Select the New Sub-Process is a transaction checkbox if you want the new sub-process to become a transaction and therefore be under transaction control (see User Tasks and Pageflow Processes).
|
|
(Activities of type Independent or Embedded Sub-Process)
|
|
|
(Activities of type reusable sub-process)
|
Sub-Process location is populated with the path to the Sub-Process name that you select.
|
|
(Activities of type reusable sub-process)
|
|
|
(Activities of type reusable sub-process)
|
|
|
(Activities of type reusable sub-process)
|
If you select Schedule Start Request, then you set the initial priority for the sub-process start and the tasks within that using the options in the Priority drop-down.
If you select Start Immediately then you can still set the priority of the task within the process in the process Work Resource tab.
|
|
|
|
|
|
|
|
|
|
Interface (all task types except Reference)
|
|
|
|
|
Overwrite Data Already Modified In Work Item is unset by default. Check it to overwrite data already modified in a work item when you reschedule a user task.
|
|
|
Note that for user tasks, inbound and outbound parameters are from the perspective of the form, not the user. This means that inbound parameters are sent to the form by the process, not the user. outbound parameters are sent to the form by the user. For more information, see the appropriate implementation guide.
|
|
|
|
|
|
|
|
Initial Priority (Manual and user tasks only)
|
|
|
(Message events and user tasks only)
|
|
|
Piling (Manual and user tasks only)
|
|
|
|
|
|
Retain Familiar (Manual and user tasks)
|
|
|
|
|
(Activities of type reusable sub-process)
|
|
|
|
|
|
|
|
|
(Activities of type reusable sub-process)
|
|
|
|
|
Click the button next to Color to select the line color for the border of the selected activity. Click Set As Default For Type to apply your current color settings to any new activities of that type that you place on the process. You can revert to the default color settings by clicking Restore Factory Settings.
|
|
|
Click the button next to Color to select the fill color for the selected activity. Click Set As Default For Type to apply your current color settings to any new activities of that type that you place on the process. You can revert to the default color settings by clicking Restore Factory Settings.
|
|
|
|
|
|
|
|
|
|
|
|
Retry properties are not available for pageflow processes.
Maximum Number of Retries, Initial Retry Period and Retry Period Increment define the retry configuration on the following activity types: Service Task, Send Task (send one way, not reply), Throw Message Intermediate and End Events (send one way, not reply).
Maximum Retry Action defines the action to take when the maximum number of retries are reached.
•
|
process/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 - the process instance fails immedately and cannot be resumed. This value, if set, takes precedence over the System Error Action value set for the process. See the BPM Fault Configuration property on the Resource tab in Process Properties.
|
|
|
Correlation Timeout (for Receive task with incoming flow)
|
|
|
|
|
|
|
|
|
Trigger Type ( for Start or Intermediate events) or Result Type ( for End events)
|
|
|
Catch Action (for catch signal intermediate events only)
|
Select either Cancel task when signal caught or Continue task when signal caught. When you select the latter, you can select between the following Reschedule Task Timer Events:
•
|
None No timer events are rescheduled when signal arrives.
|
•
|
All All timer events attached to same task are rescheduled when signal arrives.
|
•
|
Deadline The timer event set as the activity deadline; note this is evaluated at runtime rather that statically when this option is selected (so that if the deadline timer event is changed, this still works).
|
•
|
Select... One or more timer events can be manually selected.
|
|
|
Catch Error Code (for catch error intermediate events only)
|
•
|
Catch All The event catches any error thrown by any event.
|
•
|
Catch By Name The event catches an error of the specified name, thrown by any activity.
|
•
|
Catch Specific The event catches a specific error thrown by a specific activity.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Map From Error (for catch error intermediate events only)
|
|
|
Map From Signal(for catch signal intermediate events only)
|
|
|
|
|
|
|
|
|
|
Correlation Timeout (for catch message intermediate events only)
|
|