Thought-Provoking Commentary for the Lawson Software Community
|Quote of the Issue|
"Any fool can make a rule, and any fool will mind it."
-- Henry David Thoreau
|LWSN: It’s Time (to Reinvest) |
Lawson released their fourth-quarter and fiscal year 2008. Just read Lawson’s press release, and you can see that (according to Lawson, at least) everything’s rosy...Read More...
Welcome to the latest issue of The LawsonGuru Letter, a free periodic 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.
| || |
|In response to your requests, I have opened the LawsonGuru Store, where you can purchase Crystal Reports for use with your Lawson applications. I'm still building up the inventory, but some popular reports are now available. I've kept the prices pretty low; you'll be getting high-quality reports for less than you'd pay for a couple of hours of consulting.|
|ProcessFlow Integrator, Part 6: The Transaction (AGS) Node|
In a previous installment of our ProcessFlow Integrator article series, we looked at one of the most commonly-used nodes, Query (DME). Just as you need to extract data from your Lawson applications, you also need the ability to update. That's where the Transaction (AGS) node comes into play.
|S3 Security: Search Box Lockdown|
I need to restrict ESS users from using Lawson Portal's Search box, as they could then have access to HR11 to inquire Personal data.
|Need a simple 'needs recovery' notification? |
Want to get a notification when a Lawson job goes into 'needs recovery'? There are a number of ways to do it, including full-scale system monitoring. You can also use a ProcessFlow that runs in the scheduler. If you're running UNIX, here's a bare-bones, quick-and-easy way.
|Fields not clearing on HR11 (Design Studio) |
I created a new version of HR11 with just our required fields. I deleted all the tabs and made it a single form with just the desired fields. It works well with one exception. If you inquire before adding, the data that is not on the new form (Name prefix and sufix for example) still gets added if it exists on the employee record that was inquired on before adding. Any ideas on how to stop this?
Thanks for joining us this month.
Hope you are enjoying your summer!
|Worthwhile Reading |
The Next-Generation ERP
The growing use of open-source and SaaS offerings is sharpening one of the enterprise's biggest weapons: enterprise resource planning. CIOs, pay close attention.
How I Learned to Stop Worrying and Love Telecommuting
CareGroup CIO John Halamka takes an in-depth look at the policies and technologies necessary for supporting flexible work arrangements.
Less Bleeding, More Edge
Runaway IT spending is out, creative cost control is in.
|© Copyright 2008, Decision Analytics. All rights reserved.
Please share The LawsonGuru Letter in whole or in part as long as copyright and attribution ar e always included.
Lawson® is a registered trademark of Lawson Software, Inc.
The LawsonGuru Letter is neither affiliated with nor sponsored by Lawson Software, Inc.
Lawson Software, Inc. is not responsible for the content of this information.