ION Document Flow

A Document Flow moves the Business Object Document (BOD) from one application to another, like the Security User Master BOD from IFS to Landmark multi-Tenant, Landmark single-Tenant, Mongoose, Lawson LSF, etc.

Each of these applications had its own SUM BOD Document Flow created as the applications were rolled out, and after we implemented EAM we followed the same pattern and created a new Document Flow, this one with a Mapping included.

So, each application we were sending the SUM BOD to had their own separate Document Flow to process the BOD and so, we thought, the Mapping from one wouldn’t impact the others. That’s not what we discovered.

We started getting Error BODs because the Mapping we applied to the EAM Document Flow caused a problem with the other systems that couldn’t accept the change to the BOD. It was like the different Document Flows processed the BOD in a series and that’s what it looked like in One View when we reviewed the processing.

How then could we apply the Mapping for EAM without impacting the other applications? It sounds simple now, but we tried a few different things before we hit upon the answer. We needed to create one Document Flow for all of the applications together.

One Document Flow to move the BOD from IFS to all of the receiving applications, with the Mapping for EAM in a parallel stream within the Document Flow.

Not just answers, providing solutions