Migrating 8.0 Flows to 9.0

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.

I am usign bcitoxml.pl script to convert my BCI procedures into PFI XML flows. I have loaded the four tables(BCIAPI,LAWSONAPI,FORMFLDS,APIINFO) into LSF9 logan. After running the script I got the message saying,
No BCI procedures were retrieved using logan..
conversion of 0 BCI procedures completed.

Please clarrify me why com.lawson.bpm.conversion.BciToBpm is getting failed on this conversion?

The problem is that you are not using the procedure correctly. You *DO NOT* load the four tables into your new LSF9 LOGAN.

To migrate, you create a new (albeit temporary) productline (e.g. LOGAN803), to which you need to copy the 8.0.x LOGAN dictionary, your database parameter file, e.g. IBM, ORACLE, MICROSOFT, etc. You then use that new product line with the bcitoxml.pl command.

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

No, it doesn't require PFI. When you run the flow, are you specifying 'run on server'?

Yes.. I did checked the option to Run on server..

Should I have to do any steps on pfserv config in order to resolve this error.

You said you entered the username/password via pfserv config; after doing that, did you stop/start ProcessFlow (stoppfbpm/startpfbpm)?

I haven't restarted the process flow server - Just now I have restarted them and the flow works without any errors.
John, you are great.. Thanks for all your help..

I have used bcitoxml.pl to concert the 8.0.3 BCI procedures to PFI flows. We had about 15 flows and the converted flows ork fine except the one that has a call MercAdapter with custom2 value as "-if2WX". while converting the flow is says as the ascential doesn't support the "i" parameter. By removing the "i" in the above parameter the flow is converted but doesn't run successfully. We get the error "(12) source not available". We dont have PFI to edit the flows ?

try -IF (upper). I means input override and O is output override. Your error means it cannot find the file.

I am trying to find Buyer Code from RD30 record Could not find it in Resource Manager (people)
Did a query with all attributes Buyer code is not one?

Like Approver, it has been moved from RD30 to be part of the task which is assigned to users ProcessFlow Administration (/bpm).

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.

Hi all, I have read so much about migrating PF Pro 8 to 9. I have been scouring the Lawson site and can't find the tool migrate this, nor a documentation. The Lawson site has been terribly slow for 2 days now. Appreciate any help. Regards.

Nor will you find it on the support site. The migration documents are closely held by Lawson and certified partners to get you to use their services for the migration.

Here's what I did (from memory. been a long time).
1. Create sub directory in $GENDIR/ug81 call it 803flows then put all your .flo files in the sub dir.
2. In LID cd to $GENDIR/ug81
3. Run the perl script pflowtoxml.pl
Perl pflowtoxml.pl dir $GENDIR/ug81/803flows >pflowtoxml.log 2>&1

4. Checks for any errors in the log file. If converted will have a copy of .xml files in pfrepository
5. Download the converted flows from your designer.
6. Change all flows that has reference to RD30 or WEBUSER then re-upload.

The perl command should have been.

 

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

thanks, however I don't have $GENDIR/ug81 yet since we have not started the LSF9 foundation yet, that will be in May. We are still in 8.03. I was hoping to migrate all my PF now just to have a headstart. Should I wait then?

Yes this is part of the environment upgrade process from 803 to LSF9. The structure is not in 803 but only in LSF9. I used the perl command only after the migration because I found out some old .flo was not properly migrated.

Hello,

I'm new to the forum and new to process flow.  I found this post incredibly helpful!!  We are migrating from apps 8.0.3 to app 9.  We are already on LSF9.  Anyone have any tips on copying over process flow data from an 8.0.3 environment to a apps 9 environment.

Are you referring to things like tasks, user categories, workunits, etc?