To view/edit your own schedules, log into Rich Client and navigate to Start > My Actions.
To view/edit ALL schedules, log into Rich Client and navigate to Start > Applications > Async Framework Components > Requests. From there, you will be presented with a list of all Async Action Requests. The IPA process schedules are under module “pfi”.
To trigger a process manually, you first have to set up a trigger. From Rich Client, navigate to Start > Process Server Administrator > Scheduling > By Process Definition. Click Actions > Create to create a new trigger. For Process Name, select the IPA process that you want to run. Enter a descriptive Work Title (the trigger will fail if it doesn’t have a Work Title). Click Save. Then, click Actions > Start. Check the Work Unit log to see that your process has run! If you want to delete your trigger, you will first need to delete the work units associated with it.
To activate the time zones available in your Landmark applications, from the GEN data area, go to Start > Configure > Application. Under “Data Area” in the left panel, select “Time Zones”. Find the Time Zone(s) that you want to activate, and double-click to edit. Set the “In Use” flag. Now that Time Zone will be available to select in your Landmark applications.
The Landmark Configuration Console allows you to effect system-wide changes with no downtime for your users. You can personalize your Landmark applications in a multitude of ways:
The Infor-delivered role what will allow users to access Configuration Console is GlobalUIConfigAccess_ST. The role that will allow users to access Security Configuration is SecurityConfigAccess_ST.
When you are using IPA to transfer files, there may be some cases where you need to pick up multiple files, or where you need to get files for which you only know a partial name (such as a file that contains a date/timestamp). To get multiple or masked files, you can supply an asterisk (*) in the filename as a wildcard. Then, the destination file should actually be a directory name (of a directory that exists). All files that are picked up in the FTP process will be placed in that directory, and you can use them from there.
The Lawson database relationships are stored in the GEN database. Foreign key constraints are not actually added to the database tables. So, to see what these relationships are, you can query the GEN data. The primary relationship information is stored in FILEREL. Then, to get the fields that are used in the relationship you’ll need to join FILRELFLD and FILEINDFLD. FILERELFLD contains the primary field names, and FILEINDFLD contains the foreign field names. The below query is a sample run against a SQL Server database for a data area called “TEST”.
SELECT RTRIM(FILEREL.FILENAME) PARENT_FILE,
RTRIM(FILEREL.RELFILE) CHILD_FILE,
REPLACE(RTRIM(FILERELFLD.FRFLDNAME), ‘-‘, ‘_’) PARENT_FIELD,
REPLACE(RTRIM(FILEINDFLD.FLDNAME), ‘-‘, ‘_’) CHILD_FIELD
FROM FILEREL INNER JOIN
FILERELFLD ON FILERELFLD.FILENAME = FILEREL.FILENAME AND
FILERELFLD.RELNAME = FILEREL.RELNAME INNER JOIN
FILEINDFLD ON FILEINDFLD.FILENAME = FILEREL.RELNAME AND
FILEINDFLD.INDEXNAME = FILEREL.INDEXNAME AND
FILEINDFLD.FLDNBR = FILERELFLD.FLDNBR INNER JOIN
FILEDEF ON FILEDEF.FILENAME = FILEREL.FILENAME
WHERE FILERELFLD.FRFLDNAME <> ‘ ‘ AND
FILEREL.PRODUCTLINE = ‘TEST’
In Lawson v10, Admin users would have direct access to system logs but in the cloud, you’re access is limited to FTP access.
Problem: Reviewing IOS and LADB logs live is more difficult through FTP since you’re unable to download or view a file that is currently being written to. To get around this you simply use the copy line command or cp.
To understand this process, follow the steps below:
Step 1: Open LID and connect to the Lawson environment you want to access logs from.
Step 2: Go to %LAWDIR%\system directory
Step 3: Create a new folder in %LAWDIR%\system directory, command is: mkdir temp_logs (this will create a folder called temp_logs)
Step 4: In %LAWDIR%\system type this command (change based on your log names):
cp *ios_lsapp*.log temp_logs
Step 5: Go to %LAWDIR%\system\temp_logs and run the ls command to view your copied log files or simply download them from the FTP.
Here is a screenshot of my results:
It’s that time of year again! Infor has released the regulatory patching for Lawson. Patching affects 1099 reporting, benefits/ACA, and payroll. We have compiled some tips to help make your year-end patching experience as smooth as possible.
This node is used to parse a JSON response from a file or a web service call. The input can be any JSON text, such as the result from a web service call or output from a file.
On the output tab, you can select a sample document that will help building the variable list. When you click “Set Variable”, you can see all the variables that are available from the sample document, and you can export those variables so that they can be copy and pasted in assign nodes.
When setting up a lambda function there will most likely be secure information that you don’t want to put into your lambda functions. This is when you want to use environment variables. When declaring environment variables inside the code of your lambda function, add the string “process.env.varable_name” where “variable_name” is any string. Once you’ve declared all your environmental variables, go to your was lambda function console, and scroll down to the environment variables section. Then add all your “variable_names” to the left side text boxes and on the right enter in the actual value of the variable. You can then, if needed, encrypt the environment variables by using the encryption configuration.
