Route Workflow error in cloned applications

Maximo Everyplace is the quick way-to-go to provide access to mobile devices for IBM Maximo. It is basically a slightly changed look and feel of the standard web interface with a dedicated start center that is automatically displayed when logging from a mobile web browser. Obviously it works only in online mode but is straightforward to configure and supports Maximo workflow.

When using workflows with Maximo Everyplace you may encounter some errors like these:

BMXAA2301W – Doing this will cancel the workflow interaction and you lose any changes made. Do you want to save your changes before continuing?

BMXAA4365E – Process XXXX attempted to continue interacting after a node changed the current MBO.

Typically these errors are caused by the workflow trying to switch to the non-mobile version of the same application. This is caused by interaction nodes where the Application field is filled in.

In such cases, the new flag ‘Stay on Current App’ has been added in version 7.5.0.10/7.6.0.3. Here is the IBM’s description of this flag:

Workflow configuration option to Stay on Current App has been added to interaction nodes. This allows for access to the actions of another application without forcing a switch to the interaction node application upon completion of the interaction. Workflow processes with interaction nodes that specify an application-specific action and that are used in multiple applications no longer attempt to switch applications when these nodes are configured to “Stay on Current App”, thereby avoiding undesired application switching and the “BMXAA4407E – A nested exception caused the workflow process to fail (null).” error.

If you already have an existing workflow it may be hard to find all the problematic interaction nodes. Here is an SQL query to discover those nodes:

select
wfi.wfinteractionid, wfi.processname, wfi.processrev, wfi.app, wfi.staycurrentapp,
wfn.title, wfi.directions, wfi.action, wfi.tabname
from wfinteraction wfi
join wfprocess wfp on wfp.processname=wfi.processname and wfp.processrev<=wfi.processrev
join wfnode wfn on wfn.nodeid=wfi.nodeid and wfn.processname=wfi.processname and wfn.processrev=wfi.processrev
where app is not null and staycurrentapp=0
and wfn.nodetype='INTERACTION' and wfp.active=1
order by wfi.processname, wfi.processrev, wfi.nodeid;

In some cases we have discovered that the Stay on Current App is not working as expected. This query lists all the interaction nodes that have the application set but have no action or tab switch. In this cases the Application field is not needed and can be cleared.

select
wfi.wfinteractionid, wfi.processname, wfi.processrev, wfi.app, wfi.staycurrentapp,
wfn.title, wfi.directions, wfi.action, wfi.tabname
from wfinteraction wfi
join wfprocess wfp on wfp.processname=wfi.processname and wfp.processrev<=wfi.processrev
join wfnode wfn on wfn.nodeid=wfi.nodeid and wfn.processname=wfi.processname and wfn.processrev=wfi.processrev
where app is not null and action is null and tabname is null
and wfn.nodetype='INTERACTION' and wfp.active=1
order by wfi.processname, wfi.processrev, wfi.nodeid;

Route Workflow error in cloned applications

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to top