Archive for category: Articles

Many of our clients would like to lock down their external websites to EMSS only, because it is a security risk to allow super users to access HR & Financials from the web. The official word is that this cannot be done in Lawson. However, Nogalis has devised a method to remove the search box and all but the desired bookmarks from the external Lawson website. (See a sample below.) If you would like to have this done at your organization, please contact us today!

Internal Lawson Site

External Lawson Site

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

1. In Rich Client, go to Start > Scheduling by Process Definition
2. Create New
3. Select the Process under Process Name
4. Give the trigger a work title
5. Add variables if your process accepts them
   
   

Creating a Service Trigger

1. In Rich Client, first create the Service Definition by going to Start > Configuration > Service Definitions
2. Create New
3. Give the service a Name and Description
4. Check the “Is Service Enabled” check box
5. Click the Save button
   
   
6. Under the Processes tab, add the process that you will be running with this service (click the add new button)
7. Select the process to add
8. Make sure the “Is Service Process Enabled checkbox is checked
9. Click the save button
10. 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

When installing Landmark 11 with Oracle, an error may return in the log related to a config variable when setting up the database.  The installation will run for some time and eventually call D:\lmkprod]\env\install\dbconfigda.pl.  When it does this, the perl script reads the install.cfg file under the landmark system directory.  Within that file, it looks for a number of variables for the database that begin with ORA.  Those variables are set in place during the interview questions before the installation begins. Rather than read the ORA variables, the perl script will look for an additional prefix to those variables – GEN.  When it does not find GEN.ORA, the installation fails.  The installation error can be resolved by copying the ORA variables to the end of the install.cfg file and edited to begin with GEN.ORA.  After updating, the install.cfg, dbconfigda.pl will complete.  The installation can then be restarted and continue past the error.

The Message Builder Node accepts a string of text and appends each text of that string to the message each time the node is used. This can be useful when your process loops through records and records any error messages for each record. It’s also good for notification messages for multiple records.

The Variable name is what will be referenced when you want to use the built message later in the process.

Reference the variable name just like any other variable name. All nodes after the message builder will have access to the message builder variable.