Posts

How to setup a temporary requisition approver user to start and end at a certain date

  1. Login into Lawson Landmark via Richclient or the cloud-based Process Server Administrator.
  2. In PSA, go to Configuration >> User Configuration >> Users
  3. Select the user we will be adding the filter to then under User Tasks, select create a new filter. (this will be a backup or temporary filter for the user)
  4. Now create the new task (a new tab may open in your browser):
  5. Type in task name and description, save:
  6. Back under user task, select the newly created filter, select the dates you want and save. For our example today is 3/20/2020, we will be setting the date in the future to activate for 3/23/2020 to 3/27/2020:
  7. Now select your new temporary filter and add your filter keys in which you want to approve for:

That’s all there is to it, this filter will enable on 3/23/2020 and disabled again on 3/27/2020 and is useful for users that take time off and need someone to cover them.

Getting ahead of the EMSS Patch W4 Patch Security Violation

Infor KB 2096388 recently came out this year (2020) updating Employee Manager Self Service.  In doing so it brought with it an added table that users will not have access to. (Also, for that same KB, a recent notice came out on 3/26/2020 so revisit that article for latest info).

After you’ve applied the EMSS Patch for your version of Lawson. Table PRREGPARM will now be secured from ESS users when accessing their W-4 Tax Withholdings.

To fix this, go into your Lawson security Profile:

Locate your Employee File Table access class, most commonly named EmployeeSSFile.

 

Add a new rule to this class:

Choose “Files” under the “Securable Types” drop down. Expand the + sign next to the PR system code. Scroll down and locate PRREGPARM.  Now select  the check box next to the program, select conditional rule access and click edit as shown below

In the Expression builder editor, write the rule closely to the screenshot below (You may not have an Element Group named COMPEMP or may be using a different element group all together). This secures access to the employees own personal information and no one else. Click the Apply button to save the rule.

 

How to Mass Copy Lawson Portal Favorites from one user to another

In Lawson portal, you may have a user with several dozen favorited Lawson forms and a new user coming in will inevitably have a hard time maneuvering the software.  To simplify this process, you can simply copy one users’ favorites to another if you have direct access to the Lawson LSF server folder directory.

 

First login to your LSF server.

 

Go to %LAWDIR%\persistdata\lawson\portal\data\users

 

Locate and open the username of the person you want to copy the favorite URLs from. The format will be in xml Example: username.xml

 

Now Locate the username.xml you want to copy to.

Simply copy and paste from one username.xml to the other username.xml as shown below:

Save the XML file, login to Lawson Portal as an Admin user and clear IOS cache. Notify the user to clear their browser cache as well and to relog into Lawson Portal.  They should now see all the copied Favorites!

How to create a Lawson Business Intelligence (LBI) Report Schedule

You may have a report in LBI that you want to create historical instances of as well as refresh data from time to time. Let’s go over how to do this.

  1. Login into LBI as an admin user and go to Reporting Services Administration
  2. Go to Maintain Reports and open the report via the [Details] link next to the report name.
  3. In the report under Scheduling, select New Schedule
  4. Under Run Date and Time fill in the:
    • Name (schedule name)
    • Instance Name (name of generated report), you must manually re-schedule if you want to include specific unique information in the name like date.
    • Description
  5. Under Time and Frequency:
    • Set the Scheduled Run Time (time of day)
    • Time and Frequency
      • Schedule for days in a Week – This will run for every day in the week you select regardless of date.
      • Schedule for days in a Month – This will run the day you select in a month. Please note that there are specific check boxes for First and Last day in the month. If a month does not have a day like the 30th or 31st, it will skip that month.
    • Effective Date Period
      • Effective start date: This date must be set after current date and time.
      • Expiration date: The report will no longer run this schedule after this date and time.
  6. The remaining Schedule Options should typically mirror the report options. Any customizations will not change the base report.

Utilizing Lawson Business Intelligence (LBI) Security Groups

Traditionally LBI is setup with Lawson Groups such as the LBIUser which by default, communicates to LBI which users should have access.

There is another way to assign rights in LBI aside from adding more groups to users. LBI has its own native “Report Security Group” system.

  1. To access this system, login into LBI as your admin user and access Reporting Services Administration.
  2. Under Report Management, select “New Report Security Group” to create a new security group
  3. Enter the name of the group and description, click Save
  4. Now set the permissions similar to how you set permissions per report.
  5. Go to Users and add the users you want to have access to this group, you can even set report overrides per user if needed
  6. Now on an individual report, you can add the entire security group you just created to it:

You’ll still need to have Lawson groups to grant access to individual dashboards and modules but this helps add a new layer of security in an organized way.

How to Resolve “An error has occurred in the script on this page” for expression builder in Lawson Security Administrator

Here is a simple was to Resolve the notification: “An error has occurred in the script on this page” for expression builder in Lawson Security Administrator (LSA).

In LSA when trying to build a custom rule for a program you may get this error:

Trying to get passed it, it comes up again and doesn’t allow the user build rules for a file or token:

The resolution is pretty simple, go to your C:\Windows\SysWOW64 directory and run the following command:

regsvr32 msxml14.dll

You should get a pop-up confirming this. Login to LSA again and you should be good to go!

How to resolve tokendef error – You Are Secured From This Form ID: Cannot Delete

  1. You may have noticed a tokendef command you no longer need but get an error when trying to delete it.
  2. Simply go into Lawson Security Administrator (LSA) and open the environment profile. Locate a class already assigned to your user and open it.
  3. Add the tokendef you’re trying to delete, apply and clear the server cache
  4. Open tokendef again in Lawson Interface Desktop (LID) under the same user. Locate and select it, press F9 to delete and then save.
  5. Don’t forget to delete the token in Security
  6. That’s it!

Adding a custom batch command to Lawson Environment Security

  1. If you need to run a batch command in Lawson, first we need to open up Lawson interface desktop (LID).
  2. Type the tokendef
  3. For this example we’ll select Environment Form IDs and then select SECURITY category.
  4. Place your cursor at the top of the Environment Form ID list and press F8 to insert a command
  5. Type in the command you want here, ours is customcomm
  6. In Lawson Security Administrator (LSA), go to ENV profile, open a security class you want to assign customcomm command to. Under Environment Security, you should see your new batch command, select and grant all access.
  7. And we’re done!

Resolving job error – “No Data in Report File – Check Report Parameters for Possible Error Message”

While this error itself may be obvious, you’ve already taken the steps to run the job under a different user with the same parameters and everything seems to be working. Sound familiar? Let’s dive deeper to see if this issue is related to yours.

  1. Go to the Lawson batch job form for the user that is having issues.
  2. Inquire on the job and verify that you do NOT get an “Unknown” user
  3. If you’re seeing an “Unknown” at the bottom of the browser bar, continue, else you likely do not have the same issue.
  4. Open Lawson Interface Desktop (LID) and run command: listusermap -n
  5. In LID, run command: listusermap -a
  6. This should generate a new list of user identities again.
  7. Clear your server cache and IOS cache, logout and back in and your issue be resolved.

 

Chrome 80 Browser SameSite Workaround

With the Chrome 80 update, here is a simple workaround to disable SameSite cookies.

 

To get started open your Chrome Browser.

Type chrome://flags in the URL and press enter:

Search cookies and set SameSite by default cookies and Cookies without SameSite must be secure to disable, then relaunch the browser:

Confirm changes after relaunching and that it!

 

Watch the accompanying video below for a visual guide.