Common problems when converting/upgrading from Process Flow to IPA

We are in the process of converting OS platforms and upgrading from LSF 9.0.1 to Infor Lawson 10.0.8.

What are common areas that have caused problems when converting Process Flows to IPA?

Any particular flows or nodes?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Data iteration nodes. The data needs to reside on our LandMark server.
Email node too. If you have attachments the aatchments need to be on your landmark server to attach the file.

jreese

Any flows with User Actions or that currently query data from the Logan product line will need to be modified a little bit. Most flows will convert over but I would recommend you take this time to review all of your flows to see if they can be streamlined using some of the new features. Any flows that write files out to the Lawson server need to be changed to write the files to the Landmark server. We just went live this weekend and I had to convert about 100 flows over to IPA.

serafino

Exporting and importing services and process definitions as well as converting flows were a crap shoot for us. I had to export/import/convert several times to get most of PFlow converted and then we had to manually adjust about half the imported configs and flows.

unknown

aanders4, does the data need to reside on the Landmark server for performance reasons?

jreese

On the Data Iteration node you can access the data from the Lawson server if you place a file access node in front of the Data Iterator node and then use that as your input.

unknown

Pretty much anything like file access or webrun mode need an entry in the rich client in the config area so they work. Also, we had to add FROM-WORKFLOW=Y to all of our PA53 calls in IPA - did not have this in ours in v9 and they worked fine.

unknown

Nothing to do with performance for the data iteration node. jreese has a good idea about putting a file access node before the Data iteration node. I will have to try that.

acollins

My biggest issues were with anything going against WF tables which were in logan. The table structure in IPA is so different. We used List Messages in PFI sometimes with a display exec. It looks like it converts over if you open the lpd file, but it does not. I have not been able to find the equivalent of List Messages, but I believe the custom displays have been expanded for various formats. If you use a display exec and a list message, it looks like you have to add the list message to the display exec as you can only choose one. If you added javascript custom functions and put it in pflow.js, you should consider moving them to pflow_user.js so that they will not get lost with upgrades. Another thing I found out that was there are a bunch of actions you can use to do things like the job queue submit.

unknown

What is list messages? Does it list the messages from the Work Unit? If that is the case what I do it sql against the DB and concatenate all the messages to display them. It is a pain. Do you have an easier way in 10.x IPA?

acollins

The List Message is a way to produce a message when someone is working the work unit. In PFI, it was the box below the work unit description. It displayed the message in the in box.

Copyright © 2025 Infor. All rights reserved.