Welcome to the latest issue of The LawsonGuru Letter, a free newsletter providing provocative commentary on issues important to the Lawson Software community. The LawsonGuru Letter is published by-and is solely the opinion of-John Henley of Decision Analytics. |
|
ProcessFlow Integrator Part 14: ProcessFlow Server |
So far in this article series on ProcessFlow Integrator, we have
focused on designing flows, and have examined some of the nodes that
can be used in your flows. The nodes we have looked at thus far
have been in the context of standalone flows; however, using flows in
conjunction with the ProcessFlow server provides the backbone for
building a process-based use of Lawson's applications in your
organization. So, we now turn our attention to the server-based
components of ProcessFlow. Read More... |
|
Purchasing for Routine Maintenance
|
Our Facilities Dept. has many
routine purchases each month. What would work best is a Blanket PO and
release numbers for each invoice. Can Lawson help us easily with
this? How do other Hospital Facilities groups do it? We are in a
terrible quandary of band-aids to make things work. Rhe charges need to
be easily dispersed throughout the other departments cost accounts. We
end up taking three days fixing the GL because we can't get Lawson to
work for us on the front end. Any help would be appreciated. Read More... |
|
Any MSS "plain vanilla" implementations? |
My employer has been using Lawson for some years, paying for manager
self service (MSS) but not successfully able to implement it. I'm new
to the organization (working in HR), and have taken responsibility for
getting MSS up and running. We keep running into system limitations for
basic HR processes, and appear to be faced with the decision to abandon
MSS, or use our talented IT folks to make lots of changes... Read More... |
|
Interface development methodology and standards |
We are preparing to implement Lawson, and will be utilizing a combination of ProcessFlow Integrator (PFI) and our Cloverleaf engine for our interfaces. We
are looking for advice and lessons learned pertaining to process flow
development methodology, file naming conventions, and coding
standards. Does anyone have information or recommendations to share? Read More... |