This chapter describes issues associated with Oracle Business Process Management (BPM). It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
This section describes issues and workarounds for Oracle BPM Studio. It includes the following topics:
Section 20.1.1.1, "Do Not Edit the BPMN Process WSDLs directly"
Section 20.1.1.2, "Dynamic Endpoint Properties Are Not Available"
Section 20.1.1.3, "Cannot Edit Link Between BPMN Process and Business Rules in composite.xml"
Section 20.1.1.5, "The XPath Data Association Editor Does Not Validate Expressions"
Section 20.1.1.7, "Data Associations for Elements of a Collection Are Not Available"
Section 20.1.1.8, "Do Not Define Multiple Catch Events for the Same Error or Message"
Section 20.1.1.9, "Changes to a Deployed Organizational Unit Not Supported"
Section 20.1.1.12, "The Initiator Node List Shows the Names of the Possible Initiator Flow Objects"
Section 20.1.1.13, "The Pushback Task Operation Is Not Supported In an Aggregation Context"
Section 20.1.1.14, "Must Assign Application Roles from the OracleBPMProcessRolesApp Context"
Section 20.1.1.17, "Adding Counter Marks to Subprocesses is Not Available"
Section 20.1.1.19, "The Number of Business Indicators Per Project is Limited"
You must always use the Process Editor to edit a BPMN process. Do not edit the BPMN process WSDLs directly. Doing so does not allow you to save the changes and causes multiple error messages.
Dynamic endpoint properties are not available in BPM for this release.
To set endpoint properties to an SOA component used in Oracle BPM, use a BPEL process to invoke the SOA component and invoke the BPEL process from Oracle BPM.
The business rules task is used to incorporate Oracle Business Rules within a BPMN process. You can specify the business rule used as part of the configuration properties for the business rules task.
However, you cannot edit this property in composite.xml. Use the Oracle BPM Studio user interface to edit or remove the reference to the business rule.
When you delete a customized service or a reference from the SOA Composite, Oracle BPM Studio does not delete the customized component from the business catalog. Before building the BPM project you must manually delete the customized component from the business catalog.
The XPath Data Association Editor does not validate the expressions you use to assign values to arguments and data objects. You must ensure that the XPath expressions you use in an XPath data association are valid. Using invalid XPath expressions causes errors at run time.
Deleting a reference from the SOA Composite does not delete the reference from the payload of the Human Tasks that use the reference.
After you delete a reference, you must remove the deleted reference from the Human Tasks using it.
Data associations for elements of a collection are not available in this release. To assign a value to an element of a collection, use XLS transformations.
Do not define multiple catch events for the same error or message. Only the first catch event fires; the remaining catch events are ignored.
When a BPM Project is deployed, any organizational units that do not exist are created. However, when redeploying a project, if any existing organizational units are changed, the changes will not be updated.
These changes must be made by a business administrator using Oracle BPM Workspace as described in Oracle Fusion Middleware User's Guide for Oracle Business Process Management.
When you create a Human Task using Oracle BPM Suite, the enableAutoClaim property is set to true by default.
When configuring data associations for a flow object, you can map simple XML elements based on simple types to compatible basic data objects.
In the implementation properties of message events and send and receive tasks, the Initiator Node list shows the name of the initiator flow object. A BPMN process might contain multiple flow objects with the same name. It is a good practice to use a different name for all of the flow objects in the process. Not doing so causes the Initiator Node list to contain multiple items with the same name, making it difficult to identify the one you want to select.
The Approval Management pushback task operation is not supported in an aggregation context. Use the request for information task operation instead.
Using Oracle BPM Studio, you can map the roles defined in your process to application roles defined by Oracle WebLogic Server.
However, you must ensure that the application roles you use are defined as part of the OracleBPMProcessRolesApp application context. Only application roles defined in OracleBPMProcessRolesApp are used at run time.
You must configure the implementation of certain BPMN flow objects, such as gateways, business rules, and human tasks, in a BPM project created from a BPA project. Not doing so causes errors when building the BPM Project.
If you do not configure the hierarchy provider plug-in, then the following list builders do not work:
Job Level
Position
The Supervisory list builder uses the LDAP management chain if you do not configure the hierarchy plug-in.
Adding counter marks to subprocesses is not available for this release.
The available workaround is to add the counter mark to add an activity immediately after the start event in the subprocess and add a counter mark to this activity.
In BPM Suite if you define a human task assignments based on Business Rules, then you must edit the XSD of the decision service to remove the additional slashes from the import statements.
For example, you must replace the following statement:
schemaLocation="oramds:///soa/shared/workflow/TaskEvidenceService.xsd"
with the following import statement:
schemaLocation="oramds:/soa/shared/workflow/TaskEvidenceService.xsd"
You must not define more than twenty business indicators per project. The average length of the name of the business indicator must be 15 characters.
This section describes issues and workarounds for Oracle BPM Process Composer. It includes the following topics:
Section 20.1.2.1, "Deploy Option Not Available in Approval WorkFlow Browser"
Section 20.1.2.2, "Chinese, Korean, and Character Input Problems in Flow Object Labels"
When you specify an approver who also has deployment permissions, the user will not initially see the deployment option. To be able to deploy the Oracle BPM project, the user must first select approve. Once the approval workflow is complete, the option to deploy the project is available.
The Adobe Flash Player has a bug related to input for Chinese, Korean, and Japanese characters. This causes problems in Oracle Business Process Composer when editing flow object labels within the process editor.
For more information see: http://bugs.adobe.com/jira/browse/FP-501.
To resolve this issue, use Microsoft Internet Explorer version 7.
This section describes issues and workarounds for Oracle BPM Workspace and Process Spaces. It includes the following topics:
Section 20.1.3.2, "File Size Limit for Process Attachment Is 2 MB"
Section 20.1.3.3, "Drilled Down Graphs Will not Honor the Filter Criterion From the Source"
Section 20.1.3.5, "Role Members Are not Removed During Process Re-Deployment"
Section 20.1.3.6, "For Large Number of Users Set Timeout to 5 Minutes Maximum"
Section 20.1.3.7, "Possible Mixed Translation Issue when Displaying BPM Audit Trail"
Section 20.1.3.8, "Task URL Attachment from Process Tracking Page Is not Supported"
If you have a Process Spaces group space open and you bring down the documentation service, then, when you launch instance group space for an instance, you see that an instance group space is created. However, when you open the instance group space, you receive the error message "Instance 'null' is not available". This happens because the newly created group space does not have the custom attribute instanceId
.
For the workaround, the administrator should do the following:
Navigate to Settings in the process instance group space.
Navigate to custom attributes.
Create the custom attribute instanceId
and associate the process instance identifier as the value.
If you attach a file to a process, the file must be no larger than two megabytes.
In a dashboard, when you are drilling down from one widget to another, the filter conditions may not all be honored.
If you are logged into Oracle Business Process Management Workspace, and changes are made to your organizational membership, you will not see these changes reflected in the interface until you log out and log back in again. This is because, for better performance, the organizational unit information is cached when you log into Process Workspace.
If, during design time, you update a process by removing a member from a role and then re-deploy the process, the member you removed is still listed as a member of that role. This is because permission to remove members from roles is limited to administrators during runtime.
To remove the member from the role, the administrator must use Oracle Business Process Management Workspace as described in Oracle Fusion Middleware User's Guide for Oracle Business Process Management.
If you have a large number of users, set the timeout to no more than 5 minutes. To do this, expand the BPM Workspace .ear
file, open the web.xml
file, and update the timeout parameter.
In BPM Workspace, when displaying the audit trail, the fallback mechanism for the BPMN flow element labels is incorrect.
When there is no label for the browser language, an element's first label—that is, the first label in the list of localized labels—is used. This can cause the translation to be mixed because the first locale for each activity is not always the same.
To work around this issue, make the first locale the same for all activities.
You cannot access the task URL attachment from Process Tracking page.
This section describes issues and workarounds for Oracle BPMN Administration. This section contains the following:
If you encounter the following error in the log file:
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (SH_SOAINFRA.BPM_AUDIT_QUERY_PK) violated when exceeding the Quota
then increase the quota by doing the following:
Run the following SQL command:
update BPM_AUDIT_SEQUENCE set seq_count = ( select max(query_id) from bpm_audit_query) +1 where seq_name = 'AUDIT_QUERY_SEQ';
Restart the server.
There are no known configuration issues or workarounds for Oracle Business Process Management at this time.
There are no known documentation errata for Oracle Business Process Management at this time.