This chapter describes issues associated with human workflow. It includes the following topics:
This section describes general issue and workarounds. It includes the following topics:
Section 16.1.1, "Close the .rule File Before Editing Rulesets for Additional Participants"
Section 16.1.2, "Using Multibyte Characters in Plain Text/HTML Document Task Attachments"
Section 16.1.3, "Schema Elements Not Displaying in Expression Builder for Old Projects"
Section 16.1.4, "HierarchyBuilder and HierarchyPrincipal Not Visible in Expression Builder"
Section 16.1.5, "FYI Tasks Must Be Claimed Before They Can Be Dismissed"
Section 16.1.7, "Push Back Action Not Supported If Including the Task History of Another Task"
Section 16.1.8, "Editing Visibility Rules Invokes a Feedback Dialog with an Exception Error"
Section 16.1.9, "Approve and Reject Actions in Actions Tab for Admin User Should Be Disabled"
Section 16.1.10, "Specifying Date From and Date To Values on Notification Management Page"
Section 16.1.11, "Some Fields Do Not Display After Updating and Saving a ToDo Task in a Portlet"
If you add a ruleset to a task participant in the Human Task Editor, this automatically opens the Oracle Business Rules Designer and a corresponding .rule file for editing.
If you then want to add or remove rulesets for additional participants in the Human Task Editor, ensure that you first close the .rule file. This can be done by clicking the x icon for the .rule file tab above the editor. The .rule file cannot be edited (adding or removing rulesets) unless this file is first closed and reopened.
If you select Send task attachments with email notifications in the Advanced tab of the Notifications section of the Human Task Editor and add a plain text/HTML document as the task attachment, multibyte characters in the email attached document are replaced with question marks.As a workaround, use a binary document (such as .doc) as the task attachment.
If you open a human task file from a release prior to 11g PS2, schema elements do not display in the Expression Builder. For example, perform the following steps:
Open the human task file in Oracle JDeveloper.
In the Assignment section, double-click the participant type and add a participant using the Expression Builder. Note that the schema elements do not display in the Schema section of the Expression Builder dialog. Only the file location is shown.
For 11g R1 and PS1 human tasks, there is a workaround:
Edit anything, such as adding a space in the Task Title field, and select File > Save All.
Close the human task file and reopen it. The Expression Builder correctly displays the schema elements.
Note that this workaround does not apply to 10g human task files.
The visibility flags for the getManager and getPrincipal methods are not enabled in the Oracle Business Rules Editor. This causes the HierarchyBuilder and HierarchyPrincipal functions to not be visible in the Expression Builder dialog.
To make these functions visible, you must first enable the visibility flags for the getManager and getPrincipal methods in the Oracle Business Rules Editor.
Go to Facts > Java Facts.
Click HierarchyBuilder.
Click Edit.
Change the attribute to Methods.
Check the visibility for the getManager and getPrincipal methods.
If an FYI task is sent to multiple users, a user must first select the Claim button to claim the task before they can dismiss it.
When you add an attachment to a task in Oracle BPM Worklist, it is automatically saved without you having to explicitly save it.
This can cause a conflict in a scenario in which you added an attachment, forgot to delete it, assumed that it was not saved (because you never performed a save action), and then reassigned, approved, or performed a similar action on the task. As a consequence, the task attachment was sent to the next assignee even though you did not intend to send it.
As a workaround, delete the attachment if it was added inadvertently before routing the task to others.
When you include the task history of another task in a SOA composite application, selecting the push back action in Oracle BPM Worklist is not supported. For example:
Create a SOA composite application that includes a BPEL process.
In Oracle BPEL Designer, drag a human task into the BPEL process.
In the Create Human Task dialog, select the Add icon to invoke the Human Task Editor.
Create a human task (for example, named humantask_1).
Add a payload to the task and assign the task to a user (for example, jcooper).
Save the human task and exit the Human Task Editor.
In Oracle BPEL Designer, drag a second human task into the BPEL process.
Create a second human task (for example, named humantask_2) and add a payload to the task.
Assign the second task to another user (for example, jstein).
Click the Advanced tab for the second human task and select the Include task history from checkbox.
From the dropdown list, select the first task, human_task1.
Select Use existing payload.
Save and deploy the SOA composite application.
Invoke an instance of the SOA composite application.
Log in to Oracle BPM Worklist as the assignee of the first task (jcooper), and approve the task for human_task1.
The task is completed.
Log in to Oracle BPM Worklist as the assignee of the second task (jstein).
The task for human_task2 is displayed.
From the dropdown box, select Push back.
Although a push back is completed successfully, the task is still assigned to jstein.
If you make changes to the visibility rules in the Access page of the Human Task Editor (for example, set assignees to have no access to task history), save your changes, switch to Source view, and then switch back to Design view, a feedback dialog is displayed with an exception error.
Close this dialog. There is no loss of functionality.
In the Actions tab of the Access page of the Human Task Editor, the Admin user is incorrectly assigned the actions Approve and Reject by default. These checkboxes should be disabled. During runtime, if you log in to Oracle BPM Worklist as the Admin user, the actions Approve and Reject are not in the Actions dropdown list. This is the expected behavior.
You must specify values for both the Date From and Date To fields in the Search sections on the Notification Management page in Oracle Enterprise Manager Fusion Middleware Control Console to receive the correct search results. These fields do not work independently. Specifying values for only one of these fields does not display the correct search results. To access these fields:
Right-click soa-infra in the navigation tree, and select Service Engines > Human Workflow > Notification Management.
Expand the Search icon in the Outgoing Notifications section or Incoming Notifications section to display the Date From and Date To fields.
After you update and save a ToDo task or a ToDo subtask for a business task in a Worklist Portlet, the following fields should appear, but do not: Assignee, Status, and Search options.
This section describes configuration issues and their workarounds. It includes the following topic:
For better performance, only the English language is listed for the LocaleList property in the System MBean Browser in Oracle Enterprise Manager Fusion Middleware Control Console. If you want to display the task title, category, and subcategory in other languages or add additional languages, you must change the required language locale in the System MBean Browser.
Right-click soa-infra in the navigator, and select Administration > System MBean Browser.
Expand Application Defined MBeans > oracle.as.soainfra.config > Server: server_name > WorkflowConfig.
Click human-workflow.
To change the language, perform the following steps:
In the Name column, click LocaleList.
In the Value field, click the value.
In the Name column, click Language.
In the Value field, change en to the language value that you want to use.
Click Apply.
To add additional languages, perform the following steps:
Click the Operations tab.
In the Name column, click createLocale.
In the Value field, enter a value. For better performance, ensure that you include only the languages that you need for task title, category, and subcategory.
Click Invoke.