Migrating 8.0 Flows to 9.0

The LSF9 tech migration process for process flow does convert DME calls to WEBUSER, SIRDIDHDR, LOMXVALUE, and SIRDXRFDTL to use ResourceQuery nodes.  However, there are some restrictions.

We're updating RD30 with an AGS call and querying other Logan tables (ie: Sirdidhdr) with DME queries. Thanks.

NO. Flows which UPDATE resources need ResourceUpdate node, which is ONLY included in PF Integrator and BCI. Flows which ACCESS resource info use ResourceQuery which is included in ALL EDITIONS of ProcessFlow.

There are some restrictions, which I can't detail here, but should be part of your LSF9 migration process. I will say that, while the flow conversion utility does do a conversion, it is a tangled-looking flow which I would only use as a starting point for re-engineering if you are a BCI customer who is now entitled to migrate to ProcessFlow Integrator. In other words, some of the design decisions you made in creating an 8.0 flow would be made differently with LSF9 ProcessFlow Integrator.

Flows are now stored in .xml format rather than the .flo format.

Correct. However, I have found that for simple data mapping, you might be able to just use javascript (and if you have ProcessFlow Integrator, the FileAccess & DataIterator nodes).

Hi

It's a related question. Since there are no WF tables in 9.0, how would I go about converting DME and AGS calls in ProcessFlows referencing WF tables and/or forms.

Lawson knowledge article 556115 briefly mentions the process to convert 8.0.3 ProcessFlow DME and AGS calls to WorkFlow forms inLawson 9.0 but it does not give an example of a DME query in specific.  If someone can give an example of a DME call to WFFOLDER in 9.0 that would be very helpful.

Thanks much for this forum !

-Sreeni

Thank you John. I feel better. One other quick question. How about RD41 form. Does that still exist in 9.0 or is it part of RM?  I have AGS calls updating RD41 for Employee Expense in our current ProcessFlows.

Thanks - Sreeni

So, how do we handle the AGS that are updating the WF forms (WF12, 20, etc)? We do not have PFI - we are using PF Pro 9.0.0.4.

You have to use the new BPM XML forms. See Lawson KB Article 556115 -- "Converting 8.0.3 ProcessFlow Flow workflow forms ags/dme calls to Lawson 9.0".  The 8.x->LSF9 migration scripts will convert the DME calls, but NOT the AGS nodes...those you will *manually* need to change to WebRun nodes which access the new BPM XML forms...

Thanks John. So, I have to go into each AGS node and replace it with the new bpm/..  location and the function? Is this avoided if I purchase PF Integrator?

Is anyone willing to provide me with an example (screenshot?) of how/where 'they' modified there AGS that reference and WF, RD screens that no longer exist? (PF Pro 9.0.0.0.4)

Here is the Properties of a Current AGS I have going to WF21 Form - in LSF9 is this where I make the changes to reference the /bpm dir, etc? How would this look? :

_PDL=LOGAN&_TKN=WF21.1&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=Change&WFF-WORKUNIT=&LINE-FCr0=C&WFF-SEQ-NBRr0=1&WFF-KEY-STRINGr0=&_DELIM=%09&_OUT=TEXT&_EOT=TRUE

So are you saying I replace all AGS nodes with WebRuns?

Thanks so much John! ProcessFlow migration is a "show stopper" for our LSF9 Go-Live, so this has been stressing me big time - among other things ! Attached is a screen shot - I replaced teh AGS with a WebRun, does this look correct? See attached:

And here's the actual FLO - attached for reference

Of course this attachment is the entire flo - my questions are focussed on the WebRun node I have in place (first one after the START) - I do have other WF screen AGS nodes to correct in this flo - but, will cross that bridge when I need to...Thanks for any info John.

Your original AGS to WF21 would need to change to a WebRun:

When I run a webrun node for workunit folder change, _result is the whole XML DTD instead of just the return_message.  One other issue is _success  is true even when change action cannot find the record and returns a message like "Perform Inquire before Change". I got around this problem by adding a Success String in the properties. 

I have attached a document with the webrun call and results. My question is:  How would I just capture the return_message instead of the whole XML DTD in the <webrun-activity>_result variable.

Thanks

Sreeni

I don't think there's any way around it (you're using the "success" string for how it was designed. You might be able to write some Javascript to parse the XML. . I'd suggest opening a case with Lawson and submit an enhancement request for a new node that interacts with the bpm forms that replace the WFxx forms, as a number for clients have that need as they discover that ags no longer works against WFzx forms. If you want to write an article, I could include it in the PF article series I'm publishing in the LawsonGuru Letter. 
John Henley

I would love to.  Please email me (srkomma@gmail.com) with what you want me to cover in the article.

One other question: I have found routines to update WFWORKUNIT and WFFOLDER tables. Is there anything similar to update WFMSGDTL table. I tired and tried but no luck with it yet.

/bpm/xml/workUnitBForm.do     -   Updates WFWORKUNIT table
/bpm/xml/folderForm.do             -    Updates WFFOLDER tables

Thanks

Sreeni

Thanks John. It worked.  Why is there no documentation whatsoever on these from Lawson?  On the top of that, there is no consistency.

Some WEBRUN calls have to be called with "xml" in the path (bpm/xml/folderForm.do) and some work without it (bpm/messageDtlForm.do)

Thanks much for this site...

Sreeni

However you do need it if you want to update resources.

Resource Query is included with all ProcessFlow editions.  ResourceUpdate, however, is only included with ProcessFlow Integrator.  For more on what's in each edition, see https://www.lawsonguru.co...ats-in-the-Box.aspx.

Dear John

Thanks a lot for your advise. I am now able to convert the procedures into XML flows by doing the above steps. I created a simple BCI procedure(with a system command involved in the step) then converted them to XML flows and then opened the flow in PF designer. When I try to run this flow, I got a message saying that system command username was not set in pfserv config. Then, I set the user ID and password for a system command but the the error still appears. Is this something to do with Process Flow integrator license ? as we dont have PFI license..

Thanks
Thenn

You can access any of the new forms using the WebRun node.   To find out what the field values are just view the source while accessing the forms in bpm/menu.do

Slighty off-topic but related...our flows use custom Design Studio objects.  Some of these Design Studio objects have AGS calls imbedded in custom JavaScript for the now defunct WFxx forms.  We know how to use the new bpm/xml/xxx.do in ProcessFlow but how do you do access these new forms in JavaScript in a Design Studio object?

I assume they are AGS calls because you are updating and not just doing an Inquire, if it is for inquiry the tables are still the same and located in LOGAN in 9.0.  For the AGS calls you should be able to replace them with an http request such as:

var oResponse=portalWnd.httpRequest(".....");

You will have to parse the XML that is returned to see if it is successful.

The perl command should have been.

Perl pflowtoxml.pl ProductLine dir $GENDIR/ug81/803flows >pflowtoxml.log 2>&1