View Full Version: Pflow Std Vs Pro

LawsonTalk > BCI, Processflow and Addins > Pflow Std Vs Pro



Title: Pflow Std Vs Pro
Description: Bother with Standard?


3monkeys - March 15, 2007 03:36 PM (GMT)
We haven't done anything with PFlow yet but are interested in getting started. Not even sure what the first steps are, but we'll get to that. We have looked at PFlow Pro and it was difficult to tell where you really had to use Pro over Std.

Since we haven't done anything with our free Std version we're wondering how much mileage we'd get out of it before realizing we can't do much and have to go Pro. Was this the approach any of you took, or did you just get started with Pro? I feel like we might have a hard time justifying the need (and $$) for Pro if we haven't been able to demonstrate the limitations of Std.

Interested in anyone's feedback about whether or not they'd recommend Standard - at all. Since it's free it seems a shame not to at least try it, unless the consensus of those that have been there is that it doesn't really do much for you.

TIAA,
-GW

dctarheel - March 16, 2007 08:40 PM (GMT)
The only difference I know of between the two is that PFPro Designer has the HR User Action button, and Std does not.

mthedford - April 17, 2007 02:37 PM (GMT)
Standard doesn't have the Work Object node either. The HRuseraction can also be used outside of HR/PR/PA uses. An employee can be assigned to multiple HR supervisor codes. These can be used for any type of structured path of employees a flow will need to follow. Use your imagination with it. I haven't gotten my hands on it yet, but the new PFlow Integrator opens all kinds of doors for uses with it's additional nodes. Of any of the tools Lawson has offered, we have gotten the most use out of this one.




Hosted for free by InvisionFree