Archive for category: News

The IP Designer Wait Node, located under the Control Menu Group, inserts a specified wait time into your Process.  The wait times can be units of days, hours, minutes, or seconds.  This can be used for approval flows, if you want approval notifications to be sent after a certain number of days.  This can also be used in flows that run commands which need a “sleep” time between runs.  You also have the option of setting up “variable” wait times.  This could be useful if the wait time varies based on some other condition that is evaluated in the Process.

Here is a configuration for a wait time of 5 days

Here is a configuration for a wait time on a variable

While using Previous/Next on a record in Lawson portal, you may eventually stumble upon a pesky error message of:

“Security search limit of X employees exceeded” (X being anywhere from 1-100+)

 Commonly this could happen when restricting user access via process level, department, etc.

What happens when you click next or previous while inquiring on employees is that Lawson is searching in blocks of records based on your specified search limit.

For example:

If the Employee Security Search limit is set to 10 and we click next to inquire on the next employee record in HR11.

Lawson searches the next 10 employee records to see if the user has access to them.  If they do not, you will get the error message: “Security search limit of 10 employees exceeded”.

When we get the error, we should be on employee record number 10 – meaning if we click next again, we will be on employee number 20 if we do not have access the next 10 records again.

 

Ideally we’d like to reduce clicking next 10+ times by increasing the search limit.

Solution:

HR00.1

Don’t forget to click CHANGE after adjusting Employee Search Limit

As seen above, changing the search limit to something higher like 100 or more can dramatically reduce the amount of clicks to get to the next record that the user has access to.

If we change it to 100 and the next employee record is #200, it will only take 2 NEXT clicks to get to that record.

The Return Activity node in IP Designer is useful for running command line tools within a process.  You can run anything from the System Command node that could be ran in a Unix or DOS command prompt.

The first step to using a System Command Node is to configure the Sys Cmd tab in the appropriate configuration setting in Landmark.  In this case, we are using Rich Client to configure the setting.  This can also be configured via the Landmark administration web application.

To configure the System Command settings:

1. From Rich Client, open your Configuration Sets
2. Choose the Configuration Set for the server that you wish to run your commands
3. Click the Sys Cmd tab, and click Actions > Create (or if one exists, select it and click Actions > Update)
4. Fill in the parameters
   1. If the server you are accessing is remote (respective to the Landmark server), click the “Remote” checkbox
   2. The LSF Web/RMI root is the server web address
   3. The Web User is a user who has access to the Lawson Portal
   4. Password is the Web User’s password
   5. RMI timeout is the number of milliseconds to attempt the connection before timing out
   6. GENDIR and LAWDIR are the locations of those specified directories
   7. Run as user information is if you want to run your command as a different user from the user that runs the BPM process
      1. NOTE: Windows no longer allows a “Run As” user in command line activities. In typical installs, the local system user runs the BPM process on the LSF server, that is who will be running the commands in your System Command Node.  If you are using the System Command node to run Lawson tools such as importdb, you will need to make sure this local system user has access to the necessary roles in Lawson Security.

Now that your Sys Cmd settings are configured, you can use the System Command node in IPA.

1. In the node properties, select your Configuration name.
2. The default is the System (Landmark) configuration.
3. For Execution mode, you can leave it as automatic and it will use the server’s inherent command mode. Or, you can specify the mode.  Options are:
   1. run directly -> {command}
   2. run shell -> sh –c {command}
   3. run Korn shell -> ksh –c {command}
   4. run shell as System Command User (Unix only) -> su –p {password} {username} –c {command}
   5. run cmd.exe (Windows only) -> cmd.exe /C {command}
4. The Command property is the actual command script. Be sure to use the syntax appropriate for the Execution mode you chose.  You can use process variables in this window.
5. Command input is text that is sent to the command’s input stream. This is typically left blank.

Results of this example: