$ /usr/sbin/swlist -l bundle HPUXBaseAux
Some Lawson ERP forms, like HR65.x and PA08.x, use multiple forms – similar to a wizard-style dialog. In LID, you used F9 (Next Screen) and Shift+F9 (Previous Screen) to move between the screens, In Portal 9.0, there are no hotkeys assigned to move between the screens. Here’s how to do it.
You can add a user preference to change the number of workunits that are displayed in the Portal Inbasket.
If you get an error on AIX when you try to use batchdebug or cobdebug.
I need to restrict certain users from using the Portal Search box. For instance, Employee Self Service users, as they would then have access to HR11 to inquire on their Personal data.
Here's a quick sample flow demonstrating the use of the ResourceQuery and FileAccess nodes in ProcessFlow Integrator to write a file of usernames. It uses ResourceQuery to retrieve users, and FileAccess to write them to a file.
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.
One of the derived fields in the PAEMPLOYEE table is the employee age. Here's how it's defined.
On AIX, if you try to perform a command on a list of files, you'll frequently get an error:
The parameter or environment lists are too long.
Here's a quick sample of using the WebService node in ProcessFlow Integrator. It uses DME to read currency codes from the Currency Relation table, calls a WebService to retrieve latest exchange rates, and updates to CU10 via an AGS call.
There's no doubt--Lawson Application Security in LSF9 is more robust, and therefore more complicated, which makes it harder to troubleshoot. Fortunately, you have some visibility--unlike with LAUA security--into the rules engine.
Here's a quick script you can use to notify--via email--an Administrator when jobs are in 'Needs Recovery'.
Here's a slide showing how to connect a form customized with Design Studio to a ProcessFlow (Note that WF05 (Service Definition) has changed with LSF9 to the /bpm/menu.do Process Flow Administration module).
Here is a technique I recommend for notifying sys admins of jobs in recovery.
When you do a full product line re-compile, and you have customizations, you might find that some of your customizations don't get re-compiled.
Powerpoint slides demonstrating various methods (Portal, LID) for determining database field name for a field on a Lawson form.
When you install the "wfdata" jar for ProcessFlow solutions on an LSF9 server, you might encounter an error referencing jnilauntdll.dll.
I get an error ("Windows cannot find "\bin\javaw") when opening up ProcessFlow Administrator, Scheduler, etc. on the Windows machine.
I want to use dynamic parameters with my Crystal Report, which is published in LBI.
If you run long-running queries against Lawson using the OLEDB provider, you might run into issues with the query timing out.
You're running the Lawson environment or LSF9 on Windows 2003 Server, and you run into problems printing from Portal (or using print/report 'autoprint', e.g., for POs) to Windows printers, and you're NOT running into problems printing from LID).
Often when you do a full Lawson recompile (i.e. via cobcmp), there are some programs which don't compile due to contention within GEN, compiler issues, etc. All it usually takes to fix them is to simple resubmit them on the compile queue. You do this using the qcompile command, which submits individual programs to be compiled. The problem is knowing which programs need to be re-submitted.
A utility you can load onto a Windows Server to determine who has a file locked.
You've customized a Lawson-delivered table (let's ignore the drawbacks of that and just assume you've added an index) and run dbreorg. Then your users start getting lacobrts errors.
Sometimes, it's just not your day. For instance, you might have a whole bunch of jobs go into recovery. Maybe the backend database server went down. Unfortunately, Lawson doesn't have a way to recovery a whole bunch of jobs--you have to go into jobschd and recover each job--one by one. Here's a tip for doing it in one easy step.