IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Developing business processes > Building BPEL processes > Create a BPEL process > BPEL process editor
Defaults tab: BPEL process editor
You use the Defaults tab shows in the Properties view when you are working on a BPEL process. You use the Defaults tab to set default values .
Process level
- Expression language
- Use this drop down list to choose the default programming language for all customized code this BPEL process. You can choose from the following:
- Java™
- This is the default setting for processes that use BPEL extensions, otherwise XPath 1.0 will be the default . If you choose this, then you will be able to compose the expressions in the Java programming language using either the visual snippet editor, or a text editor.
- Simple
- Choose this to always have a user interface prompt you for your expression choices.
For example, when you are required to compose a condition, you will be able to work with the appropriate fields and drop down menus.
- XPath 1.0
- Choose this to compose the expressions in the XPath 1.0 programming language, using either the XPath Expression Builder, or a text editor.
- Query language
- Use this drop down list to choose the default language for all queries in variable assignments. The default language is XPath 1.0.
- Suppress join failure
- When an activity is nested within a parallel activity, and the link conditions that lead to an activity conflict with those of its join condition, then a fault is thrown on that activity. This option suppress a join failure fault from being generated on all activities contained in the process, skips all activities that generate the fault, and continues to run the process. If you select this option for an individual activity, it will override any default settings.
- Ignore missing data
- Use this option to suppress runtime faults when data is missing during assignments. Assignments occur either in assign activities, or implicitly by receiving messages in Receive, onMessage, onEvent or Invoke activities.
For example, data may be considered missing in a business object where an attribute is declared "optional". If you have an assign activity that tries to access one of these attributes, this setting prevents a fault from being thrown in the runtime environment during execution.
- Process is long-running
- When this check box is enabled, the process will be interruptible, and will be run in multiple chained transactions, each of which span the processing of one or more activities. When it is cleared, the process will be a microflow, and will run within a single transaction; and is never stored in a database.
If you want to change this setting, make sure you use refactoring or else you may get validation errors especially if your process implements a component on your module's assembly diagram.