We are facing a problem with the Business Object job AWI plugins. Would like to know if anybody has encountered this problem, and if so, if a work-around has been discovered.
Automation Engine (AE): 12.3.2+hf.2
Automic Web Interface (AWI): 12.3.2.hf3
Business Objects Agent: 12.3.2 RA core / 4.0.2+build.928 solution
Problem descriptionThe AE system allows us to create a new Business Object job, but ignores the 'Prompts' entries/popups from the chosen BO reports.
Once the job is saved, it is no long possible to access or change any details on the Business Object tab. This problem also affects previously existing BO jobs.
When we try to access the Business Objects tab of a job, the AWI throws following plugin exception:
com/automic/ecc/ae/sheet/ra/buiness/objects/views/BusinessobjectsdeaultPresenter $1
java.lang.IncompatibleClassChangeError: com/automic/ecc/ae/sheet/ra/business/objects/views/BusinessobjectsdefaultPresenter$1
at com.automic.ecc.ae.sheet.ra.business.objects.views.BusinessobjectsdefaultPresenter.getPromptsLoader(BusinessobjectsdefaultPresenter.java:153)
at com.automic.ecc.ae.sheet.ra.business.objects.views.BusinessobjectsdefaultPresenter.loadPrompts(BusinessobjectsdefaultPresenter.java:133)
at com.automic.ecc.ae.sheet.ra.business.objects.views.BusinessobjectsdefaultPresenter.render(BusinessobjectsdefaultPresenter.java:82)
at com.automic.ecc.ae.sheet.ra.commons.AsyncBuilder$1.renderResult(AsyncBuilder.java:37)
at com.automic.ecc.ae.sheet.ra.commons.AsyncBuilder$1.renderResult(AsyncBuilder.java:33)
at com.uc4.ecc.framework.commons.controls.async.AsyncContainerRenderer.render(AsyncContainerRenderer.java:75)
at com.uc4.ecc.framework.commons.controls.async.AsyncContainerRenderer.render(AsyncContainerRenderer.java:83)
at com.uc4.ecc.framework.core.async.NoArgsRendererWrapper.render(NoArgsRendererWrapper.java:17)
at com.uc4.ecc.framework.core.async.NoArgsRendererWrapper.render(NoArgsRendererWrapper.java:7)
at com.uc4.ecc.framework.core.async.MementoSafeRenderer.render(MementoSafeRenderer.java:28)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$4$1.run(BaseRequestCoordinator.java:455)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$RenderingStep.execute(BaseRequestCoordinator.java:633)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.renderInGuiThread(BaseRequestCoordinator.java:365)
at com.uc4.ecc.framework.core.async.push.PushAsyncService$1.execute(PushAsyncService.java:209)
at com.uc4.ecc.framework.core.async.push.PushAsyncService$1.execute(PushAsyncService.java:204)
at com.uc4.ecc.framework.core.async.VaadinSessionLockUtil.exeuteLocked(VaadinSessionLockUtil.java:30)
at com.uc4.ecc.framework.core.async.push.PushAsyncService.readyForRendering(PushAsyncService.java:204)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.fireReadyForRendering(BaseRequestCoordinator.java:653)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.setRenderingStep(BaseRequestCoordinator.java:600)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.access$1800(BaseRequestCoordinator.java:35)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$4.execute(BaseRequestCoordinator.java:447)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$4.execute(BaseRequestCoordinator.java:439)
at com.uc4.ecc.framework.core.async.VaadinSessionLockUtil.exeuteLocked(VaadinSessionLockUtil.java:38)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.onResult(BaseRequestCoordinator.java:439)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator.access$900(BaseRequestCoordinator.java:35)
at com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$2.onSuccess(BaseRequestCoordinator.java:243)
at com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$TimeoutListenerRunnerImplementation.run(ContextAwareExecutorService.java:113)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Screenshot
ImpactThe problem affects only editing BO jobs, and does not appear to prevent job execution; there may however be problems processing the reports that have prompts defined. The problem does not affect our 12.0.8+hf2 systems.
Possible work-arounds
- XML export, manual edit, import. This seems like a tedious process because the BO report prompts vary.
- Set up a separate v12.0.8+hf2 system for editing BO jobs, and then move them via XML to the v12.3.2 system when they are ready.
Broadcom responseBroadcom Support identified this as a bug with AWI, and agreed to deliver a hotfix. However, this may take some time.
Has anyone else encountered this bug? Did you find any better work-arounds than the ones mentioned above?
Thanks to @Vinod_Murukappan_7846 for reproducing this bug and compiling the above info.