Known Issues

You might come across the following issues when you work with AVEVA Work Tasks:

• When a workflow is scheduled to trigger after a specific time duration and the system experiences downtime, the system may create more workflow instances than expected once it resumes.

• Prolonged use of the Web Logger results in CPU utilization spikes. Immediate closure is crucial to restore CPU to normal levels and maintain application stability.

• Entering GET as instance name is not supported while designing a workflow in Process Designer or while creating Forms and Lists.

• Work Tasks supports OAuth-based authentication for POP3 and SMTP emails. A valid email address must be used for POP3 or SMTP configuration.

• Entering or editing values in Rich Text control is not supported in Mozilla Firefox browser.

• A colon character (:) is not supported for the Activity Name while designing a workflow in Process Designer.

• Role condition set through Filter Condition of To property in the Human Activity is not supported for CONNECT user provider.

• When installing a package, if Folder A already exists in the Forms List of the target environment and the package contains a Forms List with the same folder name (i.e., Folder A), the system logs the following message in the package history:

  Folder title is not unique, or it contains special characters like \\,*/, #&[]; ...

• When Quickflow application is integrated with AVEVA Work Tasks, the enabling and disabling persistence of exceptions and warnings into the database requires a restart of the Quickflow Status Monitor service to apply the changes.

• RFID scan is not supported for Work Tasks Pro Universal Windows Platform (UWP) app.

• Wonderware Skelta BPM 2017 server version is not compatible with the AVEVA Work Tasks Pro application.