Archive for category: Frontpage Article

Intuitively you may assume that you can access scheduled processes in the Lawson Process Server Administrator main toolbar:

This becomes more frustrating because you would assume it would be under “Scheduling”. After all, this is supposed to be Infor’s convenient move away from the clunky Rich Client app.

To access your existing scheduled processes, you need to go to the top right where your user is and click there and select “My Actions”, NOTE: you’ll need to be logged in as the system user

This will take you to your Scheduled Actions as show below. Double click the Name to modify the schedule and you’re set after saving!

Follow these steps below to learn how to Access and elect an older IPA Process Version History:

1. You can access via Rich client or web based Process Server Administrator:
   • Process Server Administrator – configuration >> Process Definitions >> User Defined Processes
     
   • Rich Client – Process Server Administrator >> Configuration >> Process Definitions >> User Defined Processes
     

2. Double click the process:
   
3. Under Process Versions >> Right Click the version you want >> Make Current Version
   

You’ll also see new versions here once uploaded from IPD.

Sync has seven phases.

When it fails, it will create a locked process and it can be resumed from the last completed phase.

All errors are written to lawdir/system/security_provisioning.log. Sync can be cancelled altogether with ssoconfig.

Sync will always identify some conflicts. Follow the instructions in the ISS Configuration guide to know which conflicts can safely be ignored.

For example, it might fail to sync an environment identity for a user. Try creating or deleting that environment identity in Landmark under the Gen profile manually using Rich Client, then rerun the sync identities phase.

Once federation is complete use the ISS website for all user maintenance tasks instead of LSA. Grant the actor role SecurityAdministrator_ST to anyone who needs the ability to maintain Lawson user accounts.

Update or rewrite user provisioning scripts to work with the newly federated environment. Use ISS list-based sync functionality.

Problem:

When I click on the LBI bookmark in my Lawson screen, I get an error message stating the URL redirected you too many times. This only happens when using the EDGE browser. It did not happen in Chrome.

Resolution:

Open settings in EDGE and go to Cookies and site permissions>>Cookies and data stored>>Cookies and site data and make sure the Block Third-party cookies is not off.

Turn on the following:

Now refresh cache and clear your cookies.

Note: adding any exceptions may cause the same issue, so make sure to remove any exceptions under Allow or Clear on Exit.

Often our Lawson print queues get cluttered and out of hand.  Lawson’s deljobhst command is a really great tool for cleaning up your batch jobs.  It can clear the clutter from your user’s print managers, as well as free up some space on your server.  Run this command in LID.

For each of these commands, you must provide a “ToDate” in MMDDYY format.  So, if you give it an end date of 033119, for instance, you would delete all the selected job history up to March 31, 2019.

You also have the option of providing a user’s account so that you just perform the delete for a specific user.  There is also a from date option that allows you to manage job history for a specific date range.

We recommend setting up some of these commands on a schedule to keep your Lawson server happy & healthy.

Here is a summary of the command:

The -w option will delete all waiting jobs, so jobs in recovery and jobs with Invalid Parameters.  After you run this, there will not be any jobs listed in the waiting queue for the specified user (or all users) up to the specified run date.

The -c option deletes all completed jobs.  This is a great way to clean up user’s job schedule print manager lists.  This action removes the data from the QUEUEDJOB table.  It does not remove print files.

The -r option removes all the print files associated with batch jobs, that were created up to the specified to date.  This will help keep your server from getting too cluttered.  Make sure you back up your print directory, especially if you have a retention policy at your organization.  If you run the command so that it deletes ALL print files (so delete everything up to today), it will delete your entire print directory.  Don’t panic!  It’ll be created the next time a user runs a batch job.