Known Issues for Oracle Cloud Infrastructure Process Automation

Learn about the issues you may encounter when using the current version of Oracle Cloud Infrastructure Process Automation.

Topics:

Activation issues

The following issues are related to activation of applications:

  • Activation may sometimes fail after you migrate a process from Oracle Integration Generation 2 to Gen 3.
  • Activating multi-instance processes may generate errors that prevent activation
  • The 500 Internal Server Error message displays when a decisions file is imported and a version of it is activated. The error message also displays if you activate the decision after adding an if else condition to the imported decision.
  • While performing tasks such as activating a process or creating a connection, the process designer intermittently displays the message "Something went wrong..".
  • While activating a process, process designer intermittently shows the message "Couldn't activate your application".

Alter Flow issues

The following issue is related to alter flow:

  • Changing the flow variables in the alter flow can result in errors.

Analytics issues

The following issues are related to Analytics:

  • Analytics does not show some faulted structured processes.
  • The Analytics graphical view shows linkages for milestones of dynamic processes.
  • The Analytics graphical view shows links for non-dependent activities of dynamic processes.
  • When you invoke an application with a timer and boundary event, the Analytics engine does not report the timer event's average time and the boundary event's activity is shown as in progress even though the process is completed.
  • The Analytics graphical view of dynamic processes shows incorrectly that manually activated global activities and stage is linked to other stages.
  • Terminal end event does not get linked to the activity node in the graphical view on the Analytics page.
  • Clicking elements on the Analytics page in a Safari browser doesn't navigate to the Tracking page.

Connector issues

The following issue is related to connectors:

  • Chinese characters that are passed as part of query parameters in an integration call do not reach the integration server in the required format.

  • Issue while using the OCI Signature security policy: Any call using OCI signature policy with passphrase fails and results in error.

Clone issues

The following issue is related to cloning applications:

  • Cloning an application may fail if there are validation errors.
  • When you clone an application with a different name and activate it, the cloned application retains the old name.

Data association issues

The following issues are related to data association:
  • The parent data object is not passed for correlation mappings.

    Workaround:

    Change the name of the variables and use the object that contains the variable or the parent. For example, input.correlationID.

  • Import an exp file and view the validation details summary. If you see a MovmentRestResponseTODB transformation invalid mappings message link, click the link to open it. Closing the transformations window does not revert to the original page.
  • Process fails when ExternalUI attribute is used as a task assignee expression.
  • Mapping of the service task input attribute input.Content-Type fails.
  • Subprocess data object may not work properly in some data associations.

Decisions issues

The following issues are related to decisions:

  • For a decision, the major version state goes to Validation in Progress when a minor is being edited.
  • Decision remains in a configured state and gives an activation error after project import.
  • Configured decisions in a project are in Draft state after import.
  • Decision application names are not validated.
  • Some decision applications cannot be deactivated.
  • In decisions, Process Automation does not allow versioning of a minor version from a major version.

Email service registration

The following issue is related to email service registration.

On the email service registration page, the Port field allows strings to be entered.

Form issues

The following issues are related to forms:

  • Some forms may not load correctly if the browser language is not set to English language.
  • Designer fails to populate the field if the form event reference to a connector value includes cases like upper case.
  • Form validation fails to indicate invalid connector data in events.
  • The message associated with the prevent submit event does not appear on the form in runtime.
  • Process Automation fails to execute the process if there are spaces within the special characters in query parameters.
  • Event based triggers at the form level fail to trigger.
  • Using the same objects in input and output of a form start even results in a conflict.
  • When you import an Oracle Integration Generation 2 application containing forms and without specifying the default values, the form preview doesn't display form data.
  • An imported Oracle Integration Generation 2 webform that contains a stylesheet associated with Valida-solicitud.css or a formSolicitaModDoc with reusable snippets does not render correctly in Gen 3.
  • Project with a form containing table components does not activate.
  • Resizing a read only text field does not show the full text in the text box.
  • On a Chrome browser, the submit event allows the user to reject the form or request for more information even if a mandatory field is not filled.
  • When you change the browser language to Japanese, auto binding of user interface components may not work correctly.
  • Activating the imported recipe Approve Quote Discount recipe fails because the form references a stylesheet that does not exist in the project.

    Workaround: Before activating the recipe, open the form that results in an error. Navigate to the CSS and import a new CSS to apply.

  • Detaching nested forms that contain JSON objects result in duplicate objects.

Intermittent attachment download issues

The following issue occurs intermittently for document download:

  • Downloading attachments intermittently fails with the 403 File not scanned error. Retry doesn't work and the file download remains stuck.

Migration issues

The following issues are related to migration.

  • Design time validation shows errors if the migrated data object names contain non-English characters.
  • Importing Oracle Integration Generation 2 Process Application exp file can fail if it contains a form with model type with id null.
  • After migrating Oracle Integration Generation 2 Process Application exp files to Process Automation, some applications cannot be activated.
  • When a Oracle Integration Generation 2 application is imported, some service tasks of a structured process that is called by a dynamic process may fail.
  • Single forms of imported applications fail to render if opened using the browser tools.
  • Decision names may change after migration.

    Workaround:

    Add a new decision referencing the -LATEST model and reconfigure all calls to the decision model.

  • When a Oracle Integration Generation 2 process containing email templates is migrated to Process Automation and then when the task is reassigned or escalated or if any system action is performed, the state, SubState, fromUser, updatedBy task variables are incorrectly populated.
  • Custom email templates from Oracle Integration Generation 2 when migrated to Process Automation are not converted into the styling of Process Automation.
  • Actions in custom templates are correctly migrated to Process Automation.
  • Migration of an Oracle Integration Generation 2 Process Application exp file containing a default email template was not successful because fromUserId and creatorId task variables could not be migrated to Process Automation.
  • Sometimes, importing a process application does not fully load the process.
  • When a Oracle Integration Generation 2 application is imported, the validation report displays validation errors. Clicking on the error displays an internal error page.
  • Migration of a process artifact from Oracle Integration Generation 2 to Gen 3 may sometimes fail.
  • If an Oracle Integration Generation 2 process application containing duration is imported, it results in type casting errors because the duration attribute is converted to a string.
  • Integration response types in Business Type context are overridden after migration.
  • The report of migrating a Oracle Integration Generation 2 process application to Process Automation contains duplicate messages.
  • Migrating Oracle Integration Generation 2 Process Application exp files to Process Automation gives validation errors if the applications contain business exceptions.
  • During migration of Oracle Integration Generation 2 Process Application exp file to Process Automation, the Repetition Cycle properties of a multi-instance subprocess are not migrated.

Notify email template

The following issue is related to notify email template.

  • The preview option of an email template does not validate the syntax and allow you to save the changes.
  • On some browsers, the vertical bar, Preview and Cancel UI elements of the notify email template do not work as expected.

Notifications issues

The following issue is related to notifications.

  • Clicking on a human task action link in the task notification email opens the task list instead of opening the task.
  • Notification activity containing array variables without any values fails with an error message.

Parallel gateways issues

The following issue is related to parallel gateways:

  • The previous approver is not retained when multiple tasks are set to use the previous approver within a parallel gateway.
  • An application that contains a parallel gateway and multiple inclusive gateways within may not work as expected due to converging gateways.

    As a workaround, you can add a dummy service task or a user task before the converging parallel gateway flows to ensure that the parallel gateway completes.

Process Automation Upgrade

The following issue is related to Process Automation upgrade:

  • During Process Automation upgrade, users may experience intermittent error messages.

    Workaround: Retry the operations.

Process issues

You may find the following issues with structured and dynamic processes while creating and configuring them in Designer, and running them in Workspace.

Runtime processes

  • When a task in a subflow is rejected, the process instance becomes unresponsive and does not flow to next activity in the main process flow.
  • The GetTimer process response contains extra empty braces.
  • When a runtime process fails, the audit page doesn't display the details for the event sub processes.

Subprocess

  • Altering the flow from a user task in an event subprocess to start event in event sub process or user task in event sub process results in failure.

Structured processes:

  • User cannot use the user interface to modify attributes during workflow.
  • The external decision model gets corrupted if the corresponding process application is deleted.
  • Runtime exception occurs when a process is invoked with missing attributes.
  • In the process designer, when you create a process and then create an integration using the Add Component palette, the newly created integration is automatically not added to Activities Canvas. User can refresh the browser to view the newly added Integration component in the Process activities Canvas.
  • When the draft mode of multi-instance human tasks and system tasks is enabled, the audit records incorrectly displays details of these activities.

Dynamic processes:

  • If you alter the flow of a decision model, the process instance remains in Active state even after the activity is completed.

Project issues

The following issue is related to projects.

Importing a project with decisions does not load the decisions. Deletion of an imported project fails.

REST API issues

The following issues are related to REST APIs.

  • Decision REST API may fail with 401 authorization error.
  • The reassign bulk task API does not work without the user id.
  • Importing a dmn application through a design time API may intermittently fail.
  • When the load crosses the threshold limit for a GET API call, the error stack trace shows connection pool exhausted error message.

Roles issue

The following issue is related to roles.

  • Role assignments may incorrectly work when human tasks are embedded in the subprocesses.
  • Non-administrator users can access GET roles API.
  • In projects, changes made to roles and users in the designer do not reflect in runtime.

Search issues

The following issues are related to the new business search in the Tasks and Tracking pages:

  • On the Tracking page, the advanced search does not show the correct results.
  • Search operation does not return nested control values.
  • Using non-string values in Business search fails to give search results.
  • Business search inconsistently shows Public info dat in the search results.
  • Search results page shows an inappropriate error message if the search includes unused service instances and if tasks do not exist.
  • On the tasks and tracking pages, there maybe a mismatch in the number of tasks and instances that appear as compared to the previous release.
  • Search for instances using the business key as free text search may not give the correct results.
  • Dynamic process instances search using the business key and the * wildcard character may not give the correct results.
  • Searching for tasks may not display the correct results if the browser language is changed to German.
  • Search for instances and tasks that have one or more assigned members doesn't give results.
  • When there are no tasks and process instances, search functionality displays an incorrect error message.

User task issues

The following issues are related to user tasks:
  • If you search for a task using the Select Assignee filter, Process Automation does not allow you to reassign the task to another user.
  • Attachment cannot be downloaded from a user task if the attachment exceeds a certain size limit.
  • The Team tasks tab doesn't display overdue tasks.
  • Incorrect tasks appear for a user although the user cannot perform any action on the task.
  • If you assign a task to a user, activate and invoke the process at runtime, and the user is later deleted in IDCS, then the Assignee details are shown as IDENTITY-NOT-FOUND found in Task details and in audit details pages.
  • When a task payload is modified, the audit API does not show the changes.

Workspace issues

The following issues are related to Process Automation Workspace:
  • On the tracking page, the status of a process instance may show as in-progress even if the task is completed.
  • The print option sometimes may not work.
  • On My Tasks page, the title of a task may sometimes not appear if the browser language is set to Japanese.
  • The tracking page does not show the correct title of a process instance if it is in progress state.
  • In a custom component, an error message is displayed instead of a custom message.
  • When you create an application using a recipe, the cloned process application name doesn't appear in the workspace.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.