Lawson Add-ins Script error “An error has occurred in the script on this page”. This used to be caused by an outdated internet explorer browser before Microsoft migrated fully to Edge. Now this can occur when Excel extension apps get added via an app update or feature update.
When logging into Lawson Excel addins, you may get this script error, locking up your session and not being able to login.
To resolve this, in Excel, go to File >> Options >> Add-ins >> Com Add-ins >> Go
In this case, it was an Acrobat PDFMaker office com addin extension that was added after an update, simply uncheck this extension and click OK.
Now close excel and open again, you should be able to login to Lawson Add-ins now.
Problem:
A user is encountering a problem while utilizing the XM reporting tool in conjunction with the Chrome browser.
Solution:
When launching the Ad-hoc reporting tool using Chrome and selecting the ER Model option, the “list” option is chosen from the provided pre-defined report layouts. Normally, users would be presented with the report building functions, and the right-side source panel would display all available fields that can be dragged into the report area. However, as observed in the attached document, both the source field and report area are completely empty, rendering it impossible to construct any form of report.
This issue persists when creating new reports and running existing ones through both Ad Hoc and Professional Reporting, specifically when utilizing Chrome or Incognito mode.
Note: Please be aware that IR only supports IE11 or Edge (in IE mode).
Another workaround may be to use another Browser: IE, Firefox, Edge, etc.
And that’s all there is to it. Good luck!
If you’re creating a new IPA (Infor Process Automation) Process Flow or editing a new one, you’ll want to know where the SMTP configuration information is to send out email notifications within the flow itself.
For 901 and v10 systems:
- Go to your LSF application server
- Go to the $LAWDIR\system directory.
- Search for the bpm.properties file and find the mailserver= line that contains the SMTP server info.
- Update it if needed, restart the server and test.
For cloud customers, this can be found in the Web based Process Server Administration portal for your organization.
- Login into your organizations Process Server Administration portal
- Go to Configuration >> System Configuration
- Locate the “system” configuration name and double click it to open
- Under property name, find mailServer, edit the value if needed
That’s it!
The IPA Services for Infor Lawson product (lpaservice.jar) contains the definition for each service.
These steps describe how to download, install and configure the services.
Download and install the services
- Download IPA Services for S3 from the Infor Product Download Center.
- Transfer the .jar file to your IPA server.
- Extract the contents of the .jar file to a new temporary directory.
jar –xvf lpaservice.jar
- Run the installation program from the temporary directory. Use the data area created in Landmark for IPA.
perl install-lpaservice.pl dataarea
- In order for Lawson applications to create workunits in IPA, standard workflow service data must be loaded onto the System Foundation (LSF) server.
In the temporary directory that you created, you will see the following directory structure and file:
YourTempDir/lsf/ wf-data-10.exp
Copy this file to your LSF environment in your normal install directory.
- Run the following command:
perl GENDIR/bin/pflowimpexp.pl imp wf-data-10.exp
NoteIf the installation provides feedback that some data was duplicated, you can ignore the message. This means that some or all of the workflow data already existed on the server which is not a problem.
- Verify that the services imported. View them on the IPA server. Navigate to: Start > Applications > Process Server Administrator > Configuration > Service Definitions
Configure email properties for IPA services
- From the IPA administration console on the IPA server, navigate to Configuration > System Configuration.
- Locate a configuration set named “ProcessFlowSolutions”.
- Verify that the configuration set should contains the following properties:
- FromEmailAddress
- ToEmailAddress
If the configuration set and/or the two properties do not exist, either re-install the product OR manually create the configuration to add the properties. Be sure to name them as shown above.
- Set the values of the properties to be meaningful for your organization.
- When you are finished updating, save the configuration.
Problem:
I am running Requisition Center (RQC) and I need to clear my user’s cookie data due to errors or issues accessing RQC.
Resolution:
The cookie and XML data is stored in your RQC work directory. This directory is defined in the LAWDIR/system/rqc_config.xml file. It is most commonly defined as “LAWDIR/RQC_work”.
To delete the cookie and XML data, follow the steps below:
- Change to your rqc_work directory.
- Delete all files for the web user(s) (e.g., rm userid*)
- Change to your rqc_work/cookies directory.
- Delete all files for the web user(s) (e.g., rm userid*)
- Change to your rqc_work/xml directory (if it exists).
- Delete all files for the web user(s) (e.g., rm userid*)
- Run the following URL to perform IOS Cache Refresh: https://hostname/servlet/IOSCacheRefresh
- Run the following URL to perform RQC Cache Refresh: https://hostname:port/rqc/html/utility.htm
- Have the user delete their browser cache ensuring that ‘All time’ is selected. See linked KB 1188792: “How to clear your browser cache”.
- Have the user enter RQC and immediately click on the NEW button.
The cookie and XML data is stored in the RQC work directory. This directory is defined in the LAWDIR/system/rqc_config.xml file.
To delete the cookie and XML data, follow the steps below:
- Change to your rqc_work directory.
- Delete all files for the web user(s) (e.g., rm userid*)
- Change to your rqc_work/cookies directory.
- Delete all files for the web user(s) (e.g., rm userid*)
- Change to your rqc_work/xml directory (if it exists).
- Delete all files for the web user(s) (e.g., rm userid*)
- Run the following URL to perform IOS Cache Refresh: https://hostname/servlet/IOSCacheRefresh
- Run the following URL to perform RQC Cache Refresh: https://hostname:port/rqc/html/utility.htm
- Have the user delete their browser cache ensuring that ‘All time’ is selected. See linked KB 1188792: “How to clear your browser cache”.
- Have the user enter RQC and immediately click on the NEW button.
