Learn how to customize the user experience in all your Landmark applications with the Configuration Console. We’ll show you how to create user fields, how to bring data from a related business class into a form, and more!
Posts
If you are logging into Rich Client and getting a “login failed error”, check the security_authen.log file located on the Landmark server at LASYSDIR/security_authen.log. If this file contains the error “ADFS login failed. The call to ADFS Login page was not successful”, you can configure your Rich Client installation to use an ADFS login.
These steps can be performed in the LPA Web App, or you can get to Rich Client using the command line utility. To do this, log into the Landmark server as the Lawson user. Open a Landmark command window, and type the command “canvas64 gen”. This task is performed in the GEN data area.
In the search window, type “IRC” and select “IRC Install Specifications.”
The default specifications for Rich Client 64 should look something like this:
Modify the specifications to:
- -s
- $specfile.href.url$:$specfile.version$
- -iw
- -m
- $com.lawson.url.protocol$://$com.lawson.url.host$:$com.lawson.url.port$
- <your data area>
- -q
- $com.lawson.url.protocol$://$com.lawson.url.host$:$com.lawson.url.port$
Download Rich Client again, and you will be presented with a new style of login page:
Depending on the process run, Rich Client workunit logs can grow extremely large. So large in fact that you may not be able to extract the full log from the Landmark Rich Client.
If a workunit log grows too large you may not be able to extract the full log from the Landmark Rich Client, in this case you can use the following command to extract the log from a Landmark Command Prompt.
What Is the Landmark Command Prompt?
The Landmark administrator will perform many tasks from a command prompt. When you are instructed to use a Landmark command prompt, you should be sure you are in the Landmark Environment that you want to use, and that all environment variables are set correctly.
Setting Environment Variables
Before you startBefore you perform this procedure, be sure that the /etc/lawson/environment/environmentName/config.sh file contains the appropriate settings for environment variables.
Use this procedure to export the appropriate environment variables for your Landmark Environment before issuing commands from a Landmark command prompt.
To set the Landmark Environment variables
At a command prompt, type
. cv landmark-env-name
Where landmark-env-name is the name of the Landmark Environment.
Resolution:
dbexport -C -f “PfiWorkunit=####” -o . -n <dataarea> PfiWorkunit
Example:
dbexport -C -f “PfiWorkunit=7000” -o . -n prod PfiWorkunit
When using Infor Cloud, the landmark rich client looks the same in dev as it does in prod. How can I easily recognize the difference between them?
Mistakes can happen when you are frequently changing between a development and production environment. It is easier to tell the difference between the environments when the productlines are installed with different names (dev and prod for example). If your environments use the same names, you can change the appearance in the rich client to help make it more obvious which environment you are using. From the Rich Client, click Start – Settings. Then select a different Theme color for the dev productline (green for example) and add DEV to the Display Name field. The other productlines on the dev system can also be selected and changed to green. Each of the productlines on the prod system can be changed to another color while also changing the Display Name to include PROD.
From the Landmark Rich Client, forms can be changed under Options – Personalize in the menu. Fields on a form can be renamed or changed in color or style. They can be hidden, marked as display only, or as required. In this example, the field “Last Employment ID Assigned” is highlighted in bold red with a shortened name. Once Personalize is selected, Form Personalization shows Actions and Fields at the top. Actions will allow restrictions for a specific condition. In this case, click on the “Last Employment ID Assigned” and then click Fields in the upper right. Select the Label tab to change the style, color, and text. Once the changes are made, the window is closed and the Form Personalization is Saved in the upper right. The changes are then seen immediately without restarting the client. To undo the changes, return to Options – Personalize in the menu, and click Reset in the upper right.
There are several ways to trigger an IPA process, including 4GL triggers and scheduling. One simple and low-overhead method is to use a HTTP(S) call.
HTTP(S) calls can be used to trigger a Process or a Service. To begin, you should have the process uploaded into IPA. Then you should create the Process or the Service Trigger. These can be created in Rich Client or in the IPA Admin web tool, but note that the following instructions use the verbiage & menus in Rich Client.
Creating a Process Trigger
- In Rich Client, go to Start > Scheduling by Process Definition
- Create New
- Select the Process under Process Name
- Give the trigger a work title
- Add variables if your process accepts them
Creating a Service Trigger
- In Rich Client, first create the Service Definition by going to Start > Configuration > Service Definitions
- Create New
- Give the service a Name and Description
- Check the “Is Service Enabled” check box
- Click the Save button
- Under the Processes tab, add the process that you will be running with this service (click the add new button)
- Select the process to add
- Make sure the “Is Service Process Enabled checkbox is checked
- Click the save button
- Add variables if your process accepts them
URL syntax for calling Process & Service Triggers
- Make sure you give your process a work title, in this case we are using Trigger Test
- These examples assume two variables: TestVar1 and TestVar2 (variables use a zero-based array)
- For a Service Call, triggerName is the service definition name
- For a Process Call, triggerName is the process trigger name
Asynchronous Service Call – https://ipahost:port/bpm/trigger?triggerType=ServiceAsync&triggerName=DHTest&dataArea=prod&workTitle=Trigger%20Test&varName\[0\]=TestVar1&varValue\[0\]=xyz&varName\[1\]=TestVar2&varValue\[1\]=123
Synchronous Service Call – https://ipahost:port/bpm/trigger?triggerType=ServiceSync&triggerName=DHTest&dataArea=prod&workTitle=Trigger%20Test&varName\[0\]=TestVar1&varValue\[0\]=xyz&varName\[1\]=TestVar2&varValue\[1\]=123
Asynchronous Process Call – https://ipahost:port/bpm/trigger?triggerType=ProcessAsync&triggerName=FileAccess&dataArea=prod&workTitle=Trigger%20Test&varName\[0\]=TestVar1&varValue\[0\]=xyz&varName\[1\]=TestVar2&varValue\[1\]=123
Synchronous Process Call – https://ipahost:port/bpm/trigger?triggerType=ProcessSync&triggerName=FileAccess&dataArea=prod&workTitle=Trigger%20Test&varName\[0\]=TestVar1&varValue\[0\]=xyz&varName\[1\]=TestVar2&varValue\[1\]=123