Migrating 8.0 Flows to 9.0

Can you clarify this? i.e. are you using DME against WEBUSER, AGS against RD30?

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.

Thanks John, is this a utility or is this a manual process?

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.

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

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

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

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

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

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

 

 

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.

-Sreeni, those tables still exist. It's just the forms which don't.

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

John, correct me if I'm wrong... but I don't think RD41 no longer exist in 9, either.

The RD41 fields are now stored as identities within Lawson Security. You will need ProcessFlow integrator ResourceUpdate node in order to update them.

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

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

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.

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 the news John!!! I'm already registered to take the 9.0 lab in April 7-10.

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