Infor 10...process flow administrator?

When they installed your Landmark environment, there should have been a URL for you to use to install the Rich Client. This is the interface into Landmark and includes all of the things you found in process flow administrator and bpm/menu.do in previous versions of Process Flow.

You will definitely need this because the configuration sets are created and maintained in this area and you will probably need to update things. It is also where scheduling of flows happens.

Yes I have rich client on my machine, but nothing that looks similar to processflow admin.

no one?

Hi Ronnie,

It is pretty different, and I just found a document for using Infor Process Automation out on the InforXtreme site.

Document 36280 - Infor Process Automation Administration Guide
Document 36282 - Infor Process Designer Help

I think the Admin guide should help you get around in the rich client because it is pretty different from PFI. I would also recommend attending the training if you can manage it. It is a good refresher and they cover the new features and ways of doing things in IPA.

Make sure that you have the proper Landmark security roles. Go into Rich Client in Gen. Check that you have ProcessServerAllAccess_ST. I seem to recall having the same issue when I started out with it, and I believe that fixed it.

Concur on the training, unless you're good at hacking around and figuring everything out on your own.

Curious - who installed Landmark for you, as somebody would have had to setup Task, Cat Filters, etc in Rich Client?? Interesting that whom installed LM didn't give you any training on at least how to navigate around Rich Client, Config Console or the Asynch Page. Everything that was setup & maintained in BPM is now setup and maintained in Rich Client.

Viewing and maintaining workunits is a little more cumbersome in LM, but there's a lot more information available to you, that wasn't easily available in Administrator. Read the books and try to get to Inforum this year, as i'm sure there will be plenty of classes/demos on Rich Client

Yes, IRC as it gets referred to is what you need. The thing I remember is that it opens to GEN and you have to switch to the product line to see the ipa icons. (Upper corner) The tool has most of the same features with some improvements. Installing is simple once you have the url and certificates.

I seem to remember there being a Web version of administrator that I checked during our pre-go-live but it was not robust enough for our needs.

Training is always a good thing but can be quite pricey. (System vendors should offer online training free.) Definitely a leading curve moving to ipa 10...

There is a /canvas page that is installed as part of landmark.
It is a simple page with specific links to rich client for each data area in landmark. So it has separate links for gen vs your IPA product line.

Thanks for these responses. I am a lot more familiar these days with Rich Client.

Does bpm/menu.do still get used in any form or fashion in 10? I know we have some flows defined at the current company i am at, that is getting ready to go live on 10. Some of the flows use a webrun that reference the old bpm/WorkUnitBform.do section of the old Process Flow Admin program

Are you running IPA or PFI?? If IPA, why would you need to use a ".do" form...but it sounds like you're still running PFI??

Posted By Tim Cochrane on 07/23/2015 10:46 AM
Are you running IPA or PFI?? If IPA, why would you need to use a ".do" form...but it sounds like you're still running PFI??

We are currently running PFI...that is my question. Would the webruns that reference a .do form be replaced with soemthing else?

Posted By Tim Cochrane on 07/23/2015 10:46 AM
Are you running IPA or PFI?? If IPA, why would you need to use a ".do" form...but it sounds like you're still running PFI??

We are currently running PFI...that is my question. Would the webruns that reference a .do form be replaced with soemthing else?

It is my understanding the Lawson v10 doesn't use PFI any longer, only IPA.

To specifically answer BMH's question - the webrun nodes that run the .do web programs (e.g. /bpm/folderForm.do etc.) will need to be replaced by Landmark nodes.

Posted By BarbR on 07/23/2015 11:46 AM
To specifically answer BMH's question - the webrun nodes that run the .do web programs (e.g. /bpm/folderForm.do etc.) will need to be replaced by Landmark nodes.

Thats what I was thinking. We had a consultant tell us we could just leave them in place. Thats why i posted the question up. 

 

I am trying to figure out in what way I would replace this 

BMH, there is a process flow migration tool that will "convert" your flows from PFI to LPA. We are also still on PFI, so I can't share my experience with it, but it is possible that it will convert these nodes for you and then you'll know what to use in future flows that have a similar need.

Posted By BarbR on 07/23/2015 12:11 PM
BMH, there is a process flow migration tool that will "convert" your flows from PFI to LPA. We are also still on PFI, so I can't share my experience with it, but it is possible that it will convert these nodes for you and then you'll know what to use in future flows that have a similar need.

Yeah, it doesnt convert those during the conversion. 

As others have said - These nodes will not convert and will error out in your converted flow.
You will need to replace them with a Landmark Transaction node. Learn to LOVE the Landmark node, as this your new tool for accessing ANYTHING within Landmark (app data, work unit date, etc). S3 queries and transaction nodes are available to access/maintain S3 data.

So, this is what you need to do:
1. follow the directions in the IPA install manual(?) and run the script to convert your .xml flows (PFI) to .lpd format (IPA). Good news - conversion is a one-time thing. Once you've converted flow "x" to IPA, any maintenance going forward is done in IPA.
2. when you open the converted flow in the IPA Designer any conversion errors & warnings will appear in the "Process Issues" tab at the bottom of the Designer window. This tab is where you'll also see errors when you're creating new logic. NOTE - the conversion report will also list any conversion errors.
3. Open your PFI flow and see what your ".do" node was doing (changing work unit title, adding variables, etc), then recreate it using the Landmark node.
4. BEWARE - work unit related tables (business classes in Landmark) DO NOT HAVE THE SAME NAME that they did in BPM...similar, but not the same.

Good luck, use brute force if neccessary, PM me if you have specific questions.

Tim, most of the webrun .do nodes DO get migrated to the IPA Landmark nodes. There were a couple that did not, but I think those have been corrected in a recent (10.1.1.23 I think) release. That latest migration does a pretty decent job, IMO. But you do still have to open and muck with most flows that do anything complicated.

do nodes do the below:

method=Change&workUnit=&categoryValue=NA&category=No%20Routing

@ John - good to know it works better now. Last time i ran the script...4 yrs ago(?)...it didn't do so well.