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:

  • Importing and activating an application may sometimes fail if the application is updated by splitting forms to multiple presentations.
  • Reimporting an application may sometimes fail.

Connector issues

The following issue is related to connectors:

  • Importing an integration in process automation connector may sometimes faila and show an error message.

  • The connectors page may display incorrect base URL.

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.

  • Data association fails while migrating a Gen 2 process application to Process Automation if you use the same name for both input and output. Rename one of them.

    Workaround: Rename one of them so that the the unput and output names are different.

    .

Decisions issues

The following issues are related to decisions:

  • Updating or importing a decision model may sometimes fail.
  • Creating a type using a schema in decision can make process automation unresponsive.
  • Updating the description of a decision may sometimes display Something Went Wrong error messages.

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.

  • The details of the Inbound Email server like secret are displayed in plain text oin the Register Application screen.

Form issues

The following issues are related to forms:

  • When the table property Keep Header Visible is enabled, the table header appears over the last row of the table.
  • Process application could not be activated due to an incorrect form. Workaround: Select any existing stylesheet and apply it. Now, again select no style and apply it. Activate the process.

Notify email template

The following issue is related to notify email template.

  • The special character in the task title changes when a human task email notification iss sent.

Notifications issues

The following issue is related to notifications.

  • After a task has expired, a task expiry notification is sent along with a task completed notification email.
  • Selecting the default template for an email notification may sometimes result in emails that do not contain formatted text as per the template.
  • In an email template, the approverComment variable does not show the comment for the custom action REQUEST MORE INFORMATION.

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

  • Opening a process may sometimes show a blank screen.

  • Process cannot handle field references that do not exist.

    Workaround:

    If there is a missing node or an uninitialised value while operating with an untrustworthy data source and if initialisation isn’t guaranteed, then do the following:

    1. Get type of the missing node/field.

    2. Use GetOrElse function based on the type of the node.

    3. Wrap the expression within the GetOrElse function so that if a node is missing, then the default value supplied is returned instead of getting errors during runtime.

    Node Type GetOrElse Original Expression Transformed Expression (Workaround)
    String GetOrElse.string(original exp, default value) myDO.stringAttr.substring(0) GetOrElse.string(myDO.stringAttr.substring(0), "")
    Boolean GetOrElse.boolean(original exp, default value) fname.contains("myName") GetOrElse.boolean(fname.contains("myName"),false)
    Number GetOrElse.number(original exp, default value) myDO.numberAtt < 100.50 GetOrElse.number(myDO.numberAtt,0.0) < 100.50
    Integer GetOrElse.integer(myDO.integerAtt, 12) myDO.intAtt > 999 GetOrElse.integer(myDO.intAtt,0) > 999
    Integer GetOrElse.integer(myDO.integerAtt, 12) approverFormDataObject.andApprovers.length()>10 GetOrElse.integer(approverFormDataObject.andApprovers.length(),0)>10
    Date

    GetOrElse.string(original exp, default value)

    Since it has type =string, and format=date, use GetOrElse.string.

    		    
    DateTime

    GetOrElse.string(original exp, default value)

    Since it has type=string, and format=date, use GetOrElse.string.

    		    
    Time

    GetOrElse.string(original exp, default value)

    Since it has type =string, and format=date, use GetOrElse.string.     		   

REST API issues

The following issues are related to REST APIs.

  • The reassign bulk task API does not work without the user id.
  • Importing a dmn application through a design time API may intermittently fail.

Roles issue

The following issue is related to roles.

  • When you create a role and click the category dropbox users or group or external applications, the first five values are duplicated.
  • Role assignments may incorrectly work when human tasks are embedded in the subprocesses.
  • Non-administrator users can access GET roles API.

User task issues

The following issues are related to user tasks:
  • 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:
  • Whena task is assigned to a user and after the user claims it, the more information section shows the user's username instead of showing the display name.
  • The Workspace displays a maximum of 12 activated process applications.