ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to open or edit Workflow, receive message “To execute this type of workflow you need to switch to the Release Automation perspective.”

book

Article ID: 88117

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
To execute this type of workflow you need to switch to the Release Automation perspective.

After upgrading from Automation Engine (AE) version 9 to version 12, without an Automic Release Automation (ARA) installation on the system, when attempting to open or edit a Workflow using the Automic Web Interface (AWI) an error message similar to the one below is displayed.

 
2017-05-22 10:44:43,228 pool-2-thread-2181 [ERROR] UC4:1000/ABCDEF/ABC 0 0000000143275379 +944 [controls.messageprovider.MessageProvider] - Error message shown to user: To execute this type of workflow you need to switch to the Release Automation perspective. 
java.lang.Exception: object not executable: is application workflow 
at com.uc4.ecc.ae.commons.service.UC4ObjectExecutorService.verifyObjectIsExecutable(UC4ObjectExecutorService.java:464) ~[na:na] 
at com.uc4.ecc.ae.commons.service.UC4ObjectExecutorService.verifyObjectIsExecutable(UC4ObjectExecutorService.java:445) ~[na:na] 
at com.uc4.ecc.ae.commons.service.UC4ObjectExecutorService.lambda$null$124(UC4ObjectExecutorService.java:560) ~[na:na] 
at com.uc4.ecc.ae.commons.controls.async.prompts.commands.ExecuteBaseRequestCommand.execute(ExecuteBaseRequestCommand.java:65) ~[na:na] 
at com.uc4.ecc.ae.commons.controls.prompts.requestexecutor.PromptEnabledXRequestExecutionController$1.load(PromptEnabledXRequestExecutionController.java:114) ~[na:na] 
at com.uc4.ecc.ae.commons.controls.prompts.requestexecutor.PromptEnabledXRequestExecutionController$1.load(PromptEnabledXRequestExecutionController.java:109) ~[na:na] 
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:214) ~[na:na] 
at com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72) ~[na:na] 
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_60] 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_60] 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_60] 
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]

 

Cause

Cause type:
Other
Root Cause: Due to a bug in v9, the Workflows have the JPA_WFType field set to 1 in the database which sets the Wftype to Application causing the issue.

Environment

OS Version: N/A

Resolution

Contact Automic Support and reference this article and a database script can be provided to correct the issue.

The script will contain the necessary update statements to set the jpa_wftype field to the correct value in the database.

 

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
Use the Java User Interface to open or edit the Workflows.