PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09/01/2009 1:58 PM by  Shane Jones
Migrating 8.0 Flows to 9.0
 87 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Joe O'Toole
Private
Private
Veteran Member
(784 points)
Veteran Member
Posts:306


Send Message:

--
02/22/2008 1:05 PM

    We have some flows written in designer V 8.036 and they reference RD30. Is there a migration utility to move these to LSF 9 and will it move the flows even though the RD30 logan objects no longer exist?

    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/22/2008 1:55 PM

    they reference RD30

    Can you clarify this? i.e. are you using DME against WEBUSER, AGS against RD30?
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/22/2008 2:03 PM

    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.

    Thanks for using the LawsonGuru.com forums!
    John
    Joe O'Toole
    Private
    Private
    Veteran Member
    (784 points)
    Veteran Member
    Posts:306


    Send Message:

    --
    02/22/2008 2:04 PM

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

    Joe O'Toole
    Private
    Private
    Veteran Member
    (784 points)
    Veteran Member
    Posts:306


    Send Message:

    --
    02/22/2008 2:06 PM
    Thanks John, is this a utility or is this a manual process?
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/22/2008 2:17 PM
    It is an automated utility that Lawson provides, and should be done as part of the LSF9 migration. The DME queries should convert to ResourceQuery nodes. However, I don't think (but don't quote me...) the RD30 AGS calls are converted to ResourceUpdate nodes, since you would need to have ProcessFlow Integrator in order to have ResourceUpdate.
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    02/22/2008 2:33 PM
    John,

    We too are migrating to LSF9 and I have 2 processflows that do DME to the tables mentioned above to get the hierarchies
    when dealing with who's going to approve POs (inbasket). We are still on 803 env and I want some clarification as to how
    these flows should be changed when going to lsf9.

    It is my understanding that:

    1. Flows that deals with RD30 or tables above will need PF integrator in order to work?
    2. Other Flows should transition to lsf9.
    3. All flows is now in xml format.
    4. All data mapping (aka mercator or datastage) show now be called by processflow?

    Appreciate any information you can share.

    Thanks.

    Sam
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/22/2008 2:49 PM
    1. Flows that deals with RD30 or tables above will need PF integrator in order to work?

    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.

    2. Other Flows should transition to lsf9.

    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.

    3. All flows is now in xml format.

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

    4. All data mapping (aka mercator or datastage) show now be called by processflow?

    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).

    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    02/22/2008 4:06 PM
    Thanks John. That's quite enlightening!! Again allow me to bother you with some lsf9 questions.

    1. What happen with BCI procedures? Does it still calls the compiled map (mercator or datastage) or call the processflow that calls the map?
    2. Will fileClient/ScanFileClient be the same?

    Thanks again.

    Sam
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/22/2008 4:47 PM
    1. What happen with BCI procedures? Does it still calls the compiled map (mercator or datastage) or call the processflow that calls the map?
    Similar to the ProcessFlow migration, there is a similar utility to convert BCI procedures to Processflow (.xml). There is a new "Ascential"/"DataStage TX" node which is configured to call the compiled map and pass inputs/outputs.
    2. Will fileClient/ScanFileClient be the same?
    Yes.
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    02/25/2008 9:40 AM
    Thanks again John! I suspected all along that this will be happening. Therefore BC02 is gone in lsf9.

    Can you please tell me where to find documentation on this new BCI implementation if any?

    Thanks.

    Sam
    Sreenivasa Komma
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:19


    Send Message:

    --
    02/25/2008 12:58 PM

    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

     

     

    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/25/2008 1:02 PM
    Sam, the user/admin documentation is available on Lawson's support site. The migration documentation is available only to installers from Lawson and authorized partners.
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/25/2008 1:16 PM
    -Sreeni, those tables still exist. It's just the forms which don't.
    Thanks for using the LawsonGuru.com forums!
    John
    Sreenivasa Komma
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:19


    Send Message:

    --
    02/25/2008 1:42 PM

    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

    jojo.serquina
    Veteran Member
    (163 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    02/25/2008 1:44 PM
    John, correct me if I'm wrong... but I don't think RD41 no longer exist in 9, either.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/25/2008 1:50 PM
    The RD41 fields are now stored as identities within Lawson Security. You will need ProcessFlow integrator ResourceUpdate node in order to update them.
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    02/26/2008 3:57 PM
    John,

    I found the script that converts BCI procedures to .xml and is located in $LAWDIR/bpm/pfrepository. Mercator maps are now in
    $LAWDIR/bpm/bci_maps. Can you tell me how will ScanFileClient be able to call these new xml procedures.

    Thanks again.

    Sam
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/26/2008 8:14 PM
    Pretty much the same as pre-LSF9, except the .cfg files are now in $LAWDIR/system; -Procedure specifies the ProcessFlow filename (without the .xml).
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    02/27/2008 9:18 AM
    Thanks again John. I hope I'm not boring you with all of these questions.

    Would it also mean that procedures are built in processflow designer? Do I need an Integrator to do this?

    Thanks.

    Sam
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    02/27/2008 8:19 PM
    Yes, the flows/procedures are maintained via ProcessFlow Designer. You will need to install an additional module--either BCI Enabler or ProcessFlow Enabler, depending on which you are licensed for--in order to have access to the additional BCI/PFI nodes in the Designer.
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/03/2008 2:33 PM
    Sam, FYI: Lawson sent out a notification today that they are decommissioning BCI and clients will need to migrate/upgrade to ProcessFlow Integrator...
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    03/03/2008 5:44 PM
    Thanks for the news John!!! I'm already registered to take the 9.0 lab in April 7-10.
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/05/2008 10:27 AM
    Posted By John Henley on 2/25/2008 1:16 PM
    -Sreeni, those tables still exist. It's just the forms which don't.



    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.

    M. C. Miller
    Analyst
    Salem, Oregon
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/05/2008 10:40 AM

    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 for using the LawsonGuru.com forums!
    John
    Paxson Kabala
    Private
    Private
    Basic Member
    (10 points)
    Basic Member
    Posts:4


    Send Message:

    --
    03/05/2008 1:47 PM
    We are migrating to 9.0 in the next six months. Without having any emergency/immediate work flow needs, should we even consider building process flows using the product we have now (ProcessFlow Professional) vs. waiting until we get up and running with ProcessFlow Integrator on LSF9. I'm getting the impression from these postings that the conversion process is complicated and labor intensive. On the same token, does training new power users and end users (inbasket) on 8.0 only to migrate to 9.0 in the near future make any sense? Any opinions on this would be appreciated. Thanks!
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/05/2008 5:07 PM
    Posted By John Henley on 3/05/2008 10:40 AM

    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 should convert them for you...



    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?

    M. C. Miller
    Analyst
    Salem, Oregon
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/06/2008 8:23 AM
    You will need to manually change the flow to convert the AGS node so that it uses WebRun to access the appropriate bpm/*.do function.

    PF Integrator has nothing to do with it.
    Thanks for using the LawsonGuru.com forums!
    John
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/06/2008 11:15 AM

    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)

    M. C. Miller
    Analyst
    Salem, Oregon
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/18/2008 1:52 PM

    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

     

    M. C. Miller
    Analyst
    Salem, Oregon
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/18/2008 1:54 PM
    Posted By John Henley on 3/06/2008 8:23 AM
    You will need to manually change the flow to convert the AGS node so that it uses WebRun to access the appropriate bpm/*.do function.

    PF Integrator has nothing to do with it.


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

    M. C. Miller
    Analyst
    Salem, Oregon
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/18/2008 2:00 PM
    You need to replace AGS nodes which reference WF** forms with WebRuns.
    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/18/2008 2:03 PM
    /bpm/xml/folderForm.do?methodName=Change&workUnit=xxx&sequenceNumber=1&keyString=
    Thanks for using the LawsonGuru.com forums!
    John
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/18/2008 2:14 PM

    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:

    M. C. Miller
    Analyst
    Salem, Oregon
    Attachments
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/18/2008 2:16 PM

    And here's the actual FLO - attached for reference

    M. C. Miller
    Analyst
    Salem, Oregon
    Attachments
    mil0n023
    Veteran Member
    (137 points)
    Veteran Member
    Posts:63


    Send Message:

    --
    03/18/2008 5:15 PM
    Posted By Michael Miller on 3/18/2008 2:16 PM

    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.

     

    M. C. Miller
    Analyst
    Salem, Oregon
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    03/19/2008 3:47 PM

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

    Thanks for using the LawsonGuru.com forums!
    John
    Attachments
    Sreenivasa Komma
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:19


    Send Message:

    --
    07/08/2008 10:34 AM

    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

     

     

    Attachments
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    07/08/2008 4:59 PM
    Re: Migrating 8.0 Flows to 9.0 (f1951b5e-4aed-46be-ac11-16add62ee9b2) <!-- Converted from text/plain format -->

    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

    Thanks for using the LawsonGuru.com forums!
    John
    Sreenivasa Komma
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:19


    Send Message:

    --
    07/15/2008 8:33 AM

    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

    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    07/15/2008 9:16 AM
    messageHeaderForm.do & messageDtlForm.do
    Thanks for using the LawsonGuru.com forums!
    John
    Sreenivasa Komma
    Private
    Private
    Basic Member
    (39 points)
    Basic Member
    Posts:19


    Send Message:

    --
    07/15/2008 1:24 PM

    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

    Shane Jones
    Private
    Private
    Veteran Member
    (1246 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    09/11/2008 5:40 PM
    We are in the process of planning our migration and was wondering how the migration of flow from 8 - 9 has been for other companies? Smooth - I hope.
    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    David Williams
    Private
    Private
    Veteran Member
    (3061 points)
    Veteran Member
    Posts:1031


    Send Message:

    --
    09/11/2008 5:59 PM
    The migration of flows from 8 to 9 is pretty easy (and is part of the migration steps). You will have to review the migration logs to see what updates you may need to do and should go through the flow files to make sure they are correct. For example, in LSF9 Lawson took away the option to add criteria from related tables so if I had a DME Query against PO header and PO lines and had criteria on both the DME call might not work.

    Also, if you had a AGS (Transaction) call to update WF or RD forms in 8.03 they will have to be replaced with WebRun calls.
    David Williams
    Shane Jones
    Private
    Private
    Veteran Member
    (1246 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    09/11/2008 6:11 PM
    I have a bunch of DME's with table relations... Am I going to have to move those to two different query nodes?
    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    David Williams
    Private
    Private
    Veteran Member
    (3061 points)
    Veteran Member
    Posts:1031


    Send Message:

    --
    09/11/2008 6:28 PM
    Check and test them first to see if they work in the API builder. If not, you will have to work around this limitation (by the way, Lawson says these types of queries didn't always work so they took away the option) by either adding a 2nd query within the first or by using a Branch.
    David Williams
    Shane Jones
    Private
    Private
    Veteran Member
    (1246 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    09/11/2008 9:52 PM
    That is interesting .... I hate it when a vendor takes away functionality. I was rather frustrated when I learned that I was being forced to upgrade Process Flow from Professional to Integrator so that I could continue my automation of WebUsers (something they should have automated already as part of the system.)
    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    David Williams
    Private
    Private
    Veteran Member
    (3061 points)
    Veteran Member
    Posts:1031


    Send Message:

    --
    09/11/2008 9:56 PM
    I thought the Resource Query and Resource Mgmt Update nodes were part of ProcessFlow Professional?
    David Williams
    Shane Jones
    Private
    Private
    Veteran Member
    (1246 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    09/11/2008 10:37 PM
    I was told that I would not be able to update RD and WF tables without upgrading to Integrator. Should I verify this because I really do not want to do LSF9, APP9 and Integrator at the same time... Too many moving parts.
    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    David Williams
    Private
    Private
    Veteran Member
    (3061 points)
    Veteran Member
    Posts:1031


    Send Message:

    --
    09/12/2008 3:18 AM
    You don't need PFI to update WF and RD tables - these are done with WebRun calls to the web based ProcessFlow Administrator tool. See my blog entries at http://consultdavidw.blog...-processflow-9x.html and http://consultdavidw.blog...r-task-setup-in.html for examples.
    David Williams
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    09/12/2008 6:02 AM

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

    Thanks for using the LawsonGuru.com forums!
    John
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    09/12/2008 7:59 AM

    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.com/Articles/View/tabid/346/ArticleId/539/ProcessFlow-Integrator-Part-3-Whats-in-the-Box.aspx.

    Thanks for using the LawsonGuru.com forums!
    John
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/13/2008 9:02 AM
    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?
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    10/13/2008 9:27 AM
    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.
    Thanks for using the LawsonGuru.com forums!
    John
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/13/2008 3:05 PM

    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

    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    10/13/2008 7:33 PM
    No, it doesn't require PFI. When you run the flow, are you specifying 'run on server'?
    Thanks for using the LawsonGuru.com forums!
    John
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/13/2008 10:24 PM
    Yes.. I did checked the option to Run on server..
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/14/2008 7:30 AM
    Should I have to do any steps on pfserv config in order to resolve this error.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    10/14/2008 7:44 AM
    You said you entered the username/password via pfserv config; after doing that, did you stop/start ProcessFlow (stoppfbpm/startpfbpm)?
    Thanks for using the LawsonGuru.com forums!
    John
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/14/2008 7:54 AM
    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..
    Any ideas?
    Private
    Private
    Basic Member
    (41 points)
    Basic Member
    Posts:17


    Send Message:

    --
    10/20/2008 6:21 AM
    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 ?
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    10/20/2008 10:49 AM
    try -IF (upper). I means input override and O is output override. Your error means it cannot find the file.
    nlmoran
    Veteran Member
    (121 points)
    Veteran Member
    Posts:53


    Send Message:

    --
    10/30/2008 4:14 PM
    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?
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    10/30/2008 4:35 PM
    Like Approver, it has been moved from RD30 to be part of the task which is assigned to users ProcessFlow Administration (/bpm).
    Thanks for using the LawsonGuru.com forums!
    John
    Gary Davies
    Veteran Member
    (738 points)
    Veteran Member
    Posts:248


    Send Message:

    --
    03/09/2009 5:00 AM

    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

    Paul Gallucci
    Private
    Private
    Basic Member
    (29 points)
    Basic Member
    Posts:15


    Send Message:

    --
    04/08/2009 4:52 PM

    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?

    Gary Davies
    Veteran Member
    (738 points)
    Veteran Member
    Posts:248


    Send Message:

    --
    04/09/2009 5:48 AM

    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.

    JudeBac
    Private
    Private
    Veteran Member
    (335 points)
    Veteran Member
    Posts:129


    Send Message:

    --
    04/17/2009 3:48 PM
    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.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    04/17/2009 4:34 PM
    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.
    Thanks for using the LawsonGuru.com forums!
    John
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    04/17/2009 5:07 PM
    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.
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    04/17/2009 5:12 PM

    The perl command should have been.

     

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

    JudeBac
    Private
    Private
    Veteran Member
    (335 points)
    Veteran Member
    Posts:129


    Send Message:

    --
    04/20/2009 11:36 AM
    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?
    Sam Simpson
    Private
    Private
    Veteran Member
    (673 points)
    Veteran Member
    Posts:239


    Send Message:

    --
    04/21/2009 9:25 AM
    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.
    jrbledsoe001
    Veteran Member
    (219 points)
    Veteran Member
    Posts:91


    Send Message:

    --
    08/19/2009 6:18 PM
    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.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    08/19/2009 8:28 PM
    Are you referring to things like tasks, user categories, workunits, etc?
    Thanks for using the LawsonGuru.com forums!
    John
    jrbledsoe001
    Veteran Member
    (219 points)
    Veteran Member
    Posts:91


    Send Message:

    --
    08/20/2009 7:30 AM
    Hello John Henley,
    Thank you for replying to my post. I am refering WF things like tasks, user profile def and user category definitions. We have an install of 9.0 apps and there is no data copied over to process flow administrator. Surely Lawson does not intend for customers to rebuild all their data manually when they go from v8 apps to v9. I saw some information on WEBRUN and using PFI. Unfortunately we only have PF professional. I'm new to PF any input will be most appreciated.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    08/20/2009 7:58 AM
    That data is included in Lawson's 8-to-9 migration path. Lawson didn't leave it out. Who(m)ever did your migration didn't include it.
    Thanks for using the LawsonGuru.com forums!
    John
    Gary Davies
    Veteran Member
    (738 points)
    Veteran Member
    Posts:248


    Send Message:

    --
    08/20/2009 11:20 AM
    If the delivered Service Definitions, Forms, Objects etc did not get ported over, you can install one of the Solution packs and that will load those, but nothing you had custom. I would strongly do this if they are not there because if Form definitions and Objects are missing some delivered triggers will not work even if the Services are defined correctly and there is no diagnostics as to what the issue is, they simply just do not create a work unit.

    jrbledsoe001
    Veteran Member
    (219 points)
    Veteran Member
    Posts:91


    Send Message:

    --
    08/20/2009 12:03 PM
    You guys are a Godsend! Thank you so much for replying to my post. I hope one day I can reciprocate by sharing a tid bit of my Lawson experience with you.
    jrbledsoe001
    Veteran Member
    (219 points)
    Veteran Member
    Posts:91


    Send Message:

    --
    08/21/2009 8:28 AM
    I put the install instructions in the hands of my system admin contractor for the Process Flow Professions and Process Flow Solutions Apps 8x to Apps 9 migration. Now we need to load our data.

    Anyone have any sucess stories on how you migrated your user data in the PF (logan WF tables) to version 9.0? We are considering using import db to load the user set up information; example WF tables such as WFUSERCAT and WFUSRPROFL. Aer there pitfalls with this approach?

    When you did your Process Flow data migration, did you bring over transactional history?

    Any input will be most appreciated!

    joanna.bledsoe@jhsmh.org
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    08/21/2009 9:13 AM
    The Lawson-provided migration utility will convert the configuration data as well as the transactions/workunits (there are a couple of options...off the top of my head, I can't remember them). So, you can use it to convert the flows, and the config data. Then you can start fresh with workunits, which is what most organizations try to do.

    Thanks for using the LawsonGuru.com forums!
    John
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    08/25/2009 3:56 PM
    So after reading thru 5 pages on this thread.... Are you saying if we chose NOT to pay Lawson for their migration services, we're SOL when it comes to converting .FLO files to .XML files?

    They must all be re-written from scratch?

    If so, that sucks.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    08/25/2009 5:13 PM
    Well not really, but since you should be using a certified installer (i.e. Lawson or a partner) to do the migration , it should be included. The conversion utility is installed with LSF, it's the process of doing the conversion that is where you need the expertise.
    Thanks for using the LawsonGuru.com forums!
    John
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    08/25/2009 5:25 PM
    Why should you use a certified installer? We have a large IT staff. The reason we did not use Lawson to do the migration was they would not SHOW or TEACH us how to do it. We wanted them to show us the first time, then they would do the other 11 conversions. (They are basically an ASP for 12 school districts). Lawson wanted to charge $$$ time 12 times, so we skipped using them. I'll ask the conversion programmer if they know anything about the utility and how I can use it (I'm one of the 12 districts), but we do our own PF, DS, etc.
    John Henley
    Private
    Private
    Senior Member
    (9638 points)
    Senior Member
    Posts:3230


    Send Message:

    --
    08/25/2009 5:58 PM
    The only reason is because Lawson stipulates it as a condition for providing support. Trust me, I'm not advocating their position.
    Thanks for using the LawsonGuru.com forums!
    John
    Gary Davies
    Veteran Member
    (738 points)
    Veteran Member
    Posts:248


    Send Message:

    --
    08/25/2009 9:21 PM
    "Awson offers a class to certify in the install that allows customers to self install. As far as converting fklows from .flo to .xml goes their is a perl script to do that and it is a simple to run. You may have to tweek some flows such as of you do AGS calls to RD30 but otherwise it is a simple process.
    Terry P
    Private
    Private
    Veteran Member
    (612 points)
    Veteran Member
    Posts:234


    Send Message:

    --
    09/01/2009 11:10 AM
    BTW - I found the PERL script and ran it with no problem. All of my .flo files converted and I'm now tweaking them as needed. It was MUCH easier than trying to rewrite them from scratch (and a whole lot cheaper than having Lawson do it).

    Shane Jones
    Private
    Private
    Veteran Member
    (1246 points)
    Veteran Member
    Posts:460


    Send Message:

    --
    09/01/2009 1:58 PM
    I found that I had to tweek a number of my flows after the conversion. The Lawson conversion only took us part way. Some things that worked in 8 did not work as well in 9.

    Also, we had a flow that looked at each associate to make sure that they had an active direct deposit record. (Ran great in 8.) Since upgrading to 9 it does not work. Lawson has not been able to find out why the flow will not work. The flow runs about half way through the associates and then the query stops working. (Some kind of SSO error).

    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    You are not authorized to post a reply.