The Lawson query node can be used to query Lawson data using the DME format. In the properties of the node, click “Build” to build your query. Select the product line from which you are trying to get the data. Select the module and the table name where the data resides. Choose the fields that you want to see. You will also have an opportunity to choose related fields from other tables (i.e. a description from a parent table). You can also use an index and provide keys for your query, using either hard-coded values or an IPA variable. On the Criteria tab, you can select other fields besides key index fields to narrow your results. You can use the Test tab if you don’t have any variables in your query.
Use the Landmark Transaction node to query or update Landmark data. In the properties window, select “Build” and you will be presented with a wizard to help you build your Landmark query.
Select the data area that you are querying/updating. Select the Module and Object Name. (HINT: these values can be found by using Ctrl+Shift+Click on the form in Rich Client or the Landmark Web UI).
Choose your action. There are basic CRUD (create, read, update, delete) actions for each object, and there will be more actions specific to the object you selected. Action Operator will likely be “NONE”. Select your action type (SingleRecordQuery, MultipleRecordQuery, etc.), and finally select the criteria. Click OK.
Decide whether to use the hardcoded values for your transaction field values. You can supply variables here to make your flow more portable.
https://www.nogalis.com/wp-content/uploads/2020/02/IP-Designer-Series-Landmark-Transaction.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-02-20 08:33:332020-02-19 11:01:43IP Designer Series – Landmark Transaction
Security on activity groups is handled outside of LSA. If users are getting a “security violation for activity group” when they try to add a batch job in the activities module, you will need to do a little extra security maintenance.
First, go to AC00 and make note of the value in the “Security” field.
Next, open the user’s security record in ISS or LSA and navigate to the “Company Control” field. Click on the search and make sure that “Security” value is in the user’s company list. If not, add it. Then clear out the security cach and perform an IOSCacheRefresh.
https://www.nogalis.com/wp-content/uploads/2020/02/Security-violation-for-activity-group-on-Activities-batch-jobs.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-02-18 08:09:422020-02-14 13:10:04Security violation for activity group on Activities batch jobs
AP Invoices only flow to Asset Management when there is an Asset Template associated with the AP invoice distribution line.
The invoices appear on AM15 and can be then added to AM or not depending on the actual need.
AP invoices do not automatically create assets, they need to be reviewed on AM15 and all aspects of the information that appears there is able to be adjusted before the invoice becomes an Asset.
https://www.nogalis.com/wp-content/uploads/2020/02/AP-Invoices-and-Asset-Management.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-02-14 11:51:572020-02-14 12:56:48AP Invoices and Asset Management
Recently we ran into the dreaded “Unable to load” error message in Portal, and could not find any indication of why Portal couldn’t load. The most we could see through a Fiddler trace is that the sso.js file was getting a 500 error. There was nothing logged anywhere. Not on the WebSphere node, application server, nothing in ios, security, event viewer. Nothing! We figured WebSphere had to be the culprit, because sso.js is wrapped up in an ear file in WAS_HOME, and everything on the Portal side was working until it tried to hit that script. So, we started digging into WebSphere and figured out that one of the certs was expired on the Node. For some reason, a custom wildcard cert had been used for the WebSphere install on the node only. We opted to switch it to use the default self-signed cert, which was not expired, and was the solution that worked best for us. Another option would, of course, be to upload a new wildcard cert and switch the old one to the new one.
To switch a cert in WebSphere, go to Security > SSL certificate and key management > Key stores and certificates. Select the NodeDefaultKeyStore of the node you want to change, and under additional properties on the right, select “Personal certificates”. Click your “old” cert and select “Replace”. Select the “new” certificate that is replacing the old one. Check the “Delete old Certificate after replacement” box.
Bounce WebSphere services, or better yet, reboot. And you should be good to go!
https://www.nogalis.com/wp-content/uploads/2020/02/SSO-Error-Due-to-Expired-WebSphere-Cert.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-02-10 07:06:492020-02-07 22:15:10SSO Error Due to Expired WebSphere Cert
The indexOf() method returns the first index of where a user given element is found in an array or it returns -1. This method has 1 required parameter and 1 optional parameter. The required parameter is the lookup value and the optional one is start index. The lookup value is the element you are trying to find. The start index is where you want to start looking for the lookup value.
Below shows some examples of how the indexOf() method works.
https://www.nogalis.com/wp-content/uploads/2020/01/Know-whats-in-your-Array.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-02-06 07:54:002020-02-04 16:28:11Know What’s in Your Array
Lawson RQ02 approval strings work hand in hand with Landmark and are setup in different ways per organization. Some use general hierarchal titles and some use individual usernames. Regardless of how you implement it, you want to be able to create a report so you can update them as individuals join/leave/move around the organization
To generate a database dump of all approval strings and their levels using my method, you’ll need read access rights to the LSL database and must be using SQL.
Login to your TEST or PROD database application.
Create a new query window and paste the below SQL code in, one is a screenshot to show syntax highlights and the other is the raw code for your convenience.
Run the query, copy and paste with headers into Excel to filter down the data or edit the query.
I’ve renamed various column names to reflect the different levels and dollar amounts more clearly. Feel free to change the query to your liking. This is only the RQ02 strings, to get the filters for users’ setup in Landmark, check out my article titled: “Generating a simple approval level report from the Landmark database”.
https://www.nogalis.com/wp-content/uploads/2020/01/How-to-dump-RQ02-approval-strings-out-of-a-Lawson-database.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-01-31 07:27:422020-01-23 13:44:07How to dump RQ02 approval strings out of a Lawson database
For this tutorial, we will be restricting a table in CU01.1
Login into Lawson Security Administrator
Load up your default security profile typically titled PROD10 or TEST10
Add a new security class
Ours will be called TestSecClass
Grant token access to CU01.1
Once this is added, we want to restrict a specific table on CU01.1 to find the table name, go to CU01.1 and press CTRL + SHIFT + O when selecting the field
Back in LSA, set CUC-CURRENCY-CODE to Deny Any Access
Add this new class to a role of your choice. Add the role to a user and test CU01.1. To learn more about how Lawson security handles access, check out my other article titled: “Lawson Security – The Theory of Least Privilege Access Explained”
https://www.nogalis.com/wp-content/uploads/2020/01/Form-Field-Lawson-Portal.jpg400400Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-01-29 09:34:392020-01-23 13:10:02How to Restrict a Specific Form Table Field in Lawson Portal
For this part in the series, we will be adding a simple module to our new LBI Dashboard.
First login into LBI environment as an admin user.
Go to your newly created dashboard
Click the + icon on the top left and select “New Module”
On the Main tab, title your module, ours will be called “Payroll”
By Default, the module will inherit access from the Dashboard itself, if you want to further restrict each module to separate users, you would do this again here. The expanded checkbox is great for convenience as the Module will be expanded by default:
Go to Appearance Tab and select a Icon for your module to help distinguish it from others, we will select the money icon for Payroll module:
When done select Save and you should see a blank Module in your dashboard:
To add reports to this module, click the gear wheel icon in the top right of the module and select Add Items and then Search. You can also select a direct URL but this is much easier.
A Searchbox should come up, this is to search all existing LBI reports. Type in the report name you want, check “Search Reporting Services Reports” and click the search icon to see the results.
Once you find your report, select it and click Save:
You’ve created a report module in your dashboard and added your first report!
That’s all for this article, keep an eye out for more in our LBI Dashboard series.
https://www.nogalis.com/wp-content/uploads/2020/01/Creating-an-LBI-Dashboard-Series-Adding-a-Module-Part-2.jpg470470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2020-01-27 07:17:302020-01-21 15:34:16Creating an LBI Dashboard Series – Adding a Module (Part 2)
