RA FTP Job FTP tab not displaying after import from v10 to v12

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Some RAFTP jobs which migrated from V.10 to V.12 could not open their FTP tab. Instead, the following error presents:

Cannot convert FALSE to java.lang.Boolean com.vaadin.data.util.converter.Converter$ConversionException

com.vaadin.data.util.converter.StringToBooleanConverter.convertToModel(StringToBooleanConverter.java:89) com.vaadin.data.util.converter.StringToBooleanConverter.convertToModel(StringToBooleanConverter.java:36) com.automic.ecc.ae.sheet.ra.commons.ValidatableObjectProperty.setValue(ValidatableObjectProperty.java:171) com.automic.ecc.ae.sheet.ra.commons.ValidatableObjectProperty.setStringValue(ValidatableObjectProperty.java:143) com.automic.ecc.ae.sheet.ra.ftp.job.command.copy.CopyCommandModel.loadValue(CopyCommandModel.java:83) com.automic.ecc.ae.sheet.ra.ftp.job.command.BaseJobCommandModel.load(BaseJobCommandModel.java:95) com.automic.ecc.ae.sheet.ra.ftp.job.CommandListModel.lambda$load$7(CommandListModel.java:87) java.lang.Iterable.forEach(Unknown Source) com.automic.ecc.ae.sheet.ra.ftp.job.CommandListModel.load(CommandListModel.java:85) com.automic.ecc.ae.sheet.ra.ftp.job.RAJobObjectSheetPresenter.asyncLoad(RAJobObjectSheetPresenter.java:125) com.automic.ecc.ae.sheet.ra.commons.AsyncBuilder.lambda$new$48(AsyncBuilder.java:31) com.uc4.ecc.framework.core.async.NoArgsLoaderWrapper.load(NoArgsLoaderWrapper.java:16) com.uc4.ecc.framework.core.async.NoArgsLoaderWrapper.load(NoArgsLoaderWrapper.java:7) com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:226) com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72) java.util.concurrent.FutureTask.run(Unknown Source) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 

Cause

Incorrect configuration/functionality. 

Environment

Any V12 environment.

Resolution

We’ve found that there may be some incorrect characters in the .xml file that is exported from V10. Specifically, “FALSE” instead of, “false”.

Additional Information

Two workarounds exist currently:

1) Export the object from V10.
2) Edit the .xml file with Notepad++ (or similar).
3) Find and Replace all “FALSE” iterations with “false”.
4) Save the file.
5) Import the job into V12.

*)Alternatively, the jobs would need to be recreated in version 12.