Infor Helps Organizations Meet Demands of the Emerging Workforce

Infor has released the Infor CloudSuite CRM Mobile for iOS to simplify customer relationship management for busy, on-the-go sales professionals. This new native mobile solution aligns with Infor’s goal of anticipating the needs of the emerging workforce. Users have access to information such as events, contacts, notes, and reminders from their mobile devices anytime, anywhere – all without navigating through pages of data. Infor CloudSuite CRM Mobile is part of the Infor Customer Experience suite of solutions and will help sales professionals seize opportunities in real-time, as well as increases active selling time by encouraging sales teams to be proactive. Additionally, users have a streamlined resource that leverages the most relevant features of Infor CRM and iOS functionality including contacts, meetings, directions, and analytics from core product and Apple 3D Touch, Apple Maps, and the iOS Quick Look file previewer. Infor CRM Mobile is currently available in the Apple iOS App Store and is planned to be available for Android devices in late 2019.

For Full Article, Click Here

Easily Create Upload Formatted Documents from Existing Spreadsheets

, ,

Often people have spreadsheets that they are using for data gathering and don’t want to change the familiar format to accommodate a Lawson Upload.  Especially when it is a multi-tab spreadsheet that data can change depending on which tab you are pulling data from. No problem. Using advanced Excel techniques can pull the information from the specified tab in a format needed for uploading.

In this example, time attributable to projects is entered on a multi-tab spreadsheet one tab per period.

As the tab changes on the Instructions tab, and after the macro finishes by clicking n the Create Upload button, the total count and amount can be validated that the process worked as expected.

Each tab can have a different order of users and/or different active projects across the top.

As the tab changes on the Instructions tab, and after the macro finishes by clicking n the Create Upload button, the total count and amount can be validated that the process worked as expected.

The macro extracts the non-zero time entries and formats the data in a way that the Upload Wizard can then load the data into Lawson. 

How to write fail safe stored procedures

, ,

We normally write stored procedures for nearly any transaction that has more than one component to it. For example, creating an invoice record that has many lines would require you to insert a record into a header table, and multiple records into a detail table. But what happens if you insert the header and one of the detail records fails to get inserted properly. In these cases, you’re usually greeted by a SQL Exception and error out. However, depending on how you write your stored procedure, you might now have one header record and some of the detail records in the database. In some cases this might be okay, but in most cases it is not and the preference would be to avoid inserting any of the records if even one of them fails. Luckily MySQL provides a really great solution for this problem.

You simply define the action to be taken once the exception is encountered, in our case a rollback, and then you start and end your transaction in between a “START TRANSACTION” and “END” directive as shown below:
BEGIN

    .. Declare statements ..

    DECLARE EXIT HANDLER FOR SQLEXCEPTION 
    BEGIN

          ROLLBACK;
    END;

    START TRANSACTION;

        .. INSERT  ..
        .. UPDATE  ..
        .. SELECT  ..

    COMMIT;
END

Overview of Flow Documentation Sections

,

Grav is an open source flat-file CMS that we use for client documentation.

Requirements:

  1. Web Server (Apache, Nginx, LiteSpeed, Lightly, IIS, etc.)
  2. PHP 5.5.9 or higher

Advantages of using a Grav CMS for documentation:

  1. SEARCH bar: Can search entire collection of documentations for a search term instead of going through each doc file individually
  2. Not reliant on database: Flat-file content management system means that the data is stored in folders rather than a database = fast loading
  3. Easy to maintain since all data in local folders
  4. Simple HTML format written with Markdown syntax (https://nogalis.com/docr/how-to-use-docr to learn more about Markdown)
  5. Many useful plugins freely available (https://www.nogalis.com/2018/07/27/grav-a-modern-flat-file-cms for more information on plugins)
  6. User authentication and custom user privileges

Documentation Sections


  1. Introduction – Screenshot of the IPA flow and a short description about what it does
  2. General Data Flow – Box diagram showing step-by-step what is happening in the flow. Also accompanied by a paragraph explanation
  3. Components Table – A table that lists all input/output files, databases, scripts, triggers, jobs, and configuration variables
  4. Dependencies – The files, triggers, jobs, or SQL/server connections required for the flow to function
  5. Scheduling and Triggers – How/when the flow gets triggered
  6. Recovery – This section provides instructions on how to manually execute the steps of the flow if it fails. Each step here represents a box in the General Data Flow box diagram.
  7. Archiving – Table showing archived files and their archived locations
  8. Notifications – Details of the notifications sent by the flow
  9. Troubleshooting – General tips for troubleshooting
  10. Maintenance – Maintenance needed by the flow (usually involves cleanup of archived/done files)
  11. Security – Overview of user permissions and connection credentials needed for the flow
  12. Key Contacts – The person to contact for questions about the flow/documentation
  13. Related Files – File uploads related to the flow (these are able to be viewed/downloaded from the page)

For full examples, please visit https://nogalis.com/docr/demo_documentation

Monthly Server Healthcheck Section Overview

, ,

Nogalis offers monthly server healthchecks that informs clients of any current or potential problems in Lawson for both PROD and TEST servers. The healthcheck covers error logs, smoke tests, patches, LID functionality, portal check, database integrity, and many other sections (26 total) which will be briefly outlined here.

You can visit https://nogalis.com/docr/demo_hc to view a demo healthcheck for yourself.

  1. Summary

    This is arguably the most important section of the monthly healthcheck. If there is one section to read, it should probably be this one as it brings to attention the most pressing needs of all the other sections. There is also a handy letter grade assigned each month so you can quickly keep track of the overall health of your server!
  2. Recommendations

    This section has all the combined recommendations from the other sections of the healthcheck. It is divided into three levels of urgency so the client can decide what to focus in on.

  3. System Layout

    System hardware and OS information.

  4. Component Versions

    Lawson components version information. If server versions start to fall significantly behind latest versions, recommendations are made.

  5. Application Versions

    Lawson application version information

  6. Programs with Errors

    Any .err files found in the Lawson directory are pointed out in this section. As with any section, further investigation into any issue can be requested by sending an email to the Key Contact.

  7. Custom Programs

    List of custom Z/Y/X programs

  8. CPU Performance

    Tested while idle and under duress. Just a very rough idea of the CPU performance.

  9. Disks Report

    Report on the free space available of the different drives on the server. We make sure to point out in the Summary and Recommendations sections when a drive is getting dangerously low on free space.

  10. Purge Recommendations

    The disks report is followed by purge recommendations where we point out certain things that could be deleted to free up some space.

  11. Java

    Java settings information/recommendations and a screenshot of the jconsole.

  12. licsta

    Summary table of current licenses (viewable in LID)

  13. Error Logs

    Every month we grab these 6 important logs to analyze them for current errors. These errors are pointed out in this section so that the client can determine if they are worth investigating or not.

  14. Smoke Tests and Component Testing

    Various smoke tests with LID, Lawson portal, and various URL tests

  15. Recurring Job Listing

    Simple table listing of recurring jobs. One of the sneaky benefits of having all this information in one healthcheck page is that it allows for a quick search for any terms using the DOCR search bar on the left panel.

  16. Waiting Jobs

    List of waiting jobs

  17. Database/Table Review and Sizing

    This section displays the 10 tables with the largest number of rows for each of PROD/LOGAN/GEN. A quick overview of this section might lead to decisions to purge certain tables for example.

  18. Database Integrity Check

    Summary of database integrity check performed through LID. Any errors here are pointed out in Summary/Recommendations.

  19. Printers

    List of printers and their commands

  20. Work Directory Review

    Overview of Lawson work folder

  21. Print Directory Review

    The Lawson print directory list by user. This information could possibly be used to purge old users/records.

  22. Security Analysis

    Security analysis performed using LSFIQ
    (1-click Lawson security audit and reporting tool: see https://www.nogalis.com/nogalis-products/lawson-security-with-lsfiq/ for more info.)

  23. Patches Installed Report

    List of latest patches installed on this server.

  24. Source Versions Report

    The source versions report is in a zipped file available to download in the Related Files section.

  25. Related Files

    Any related files related to the healthcheck are in this section where they are available to view or download.

  26. Key Contacts

    If you have any questions about the healthchecks or would like to request an investigation into some error discovered by the healthcheck, please contact anyone in the Key Contacts section with your questions.

What does deljobhst really do?

, ,

Often our Lawson print queues get cluttered and out of hand.  Lawson’s deljobhst command is a really great tool for cleaning up your batch jobs.  It can clear the clutter from your user’s print managers, as well as free up some space on your server.  Run this command in LID.

For each of these commands, you must provide a “ToDate” in MMDDYY format.  So, if you give it an end date of 033119, for instance, you would delete all the selected job history up to March 31, 2019.

You also have the option of providing a user’s account so that you just perform the delete for a specific user.  There is also a from date option that allows you to manage job history for a specific date range.

We recommend setting up some of these commands on a schedule to keep your Lawson server happy & healthy.

Here is a summary of the command:

The -w option will delete all waiting jobs, so jobs in recovery and jobs with Invalid Parameters.  After you run this, there will not be any jobs listed in the waiting queue for the specified user (or all users) up to the specified run date.

The -c option deletes all completed jobs.  This is a great way to clean up user’s job schedule print manager lists.  This action removes the data from the QUEUEDJOB table.  It does not remove print files.

The -r option removes all the print files associated with batch jobs, that were created up to the specified to date.  This will help keep your server from getting too cluttered.  Make sure you back up your print directory, especially if you have a retention policy at your organization.  If you run the command so that it deletes ALL print files (so delete everything up to today), it will delete your entire print directory.  Don’t panic!  It’ll be created the next time a user runs a batch job.

Infor Supports EKZ Renewables with Expansion

Infor recently announced that Zurich based wind parks company EKZ Renewables AG has deployed Infor d/EPM to help support the company’s continuous growth. Infor d/EPM is a sophisticated business intelligence solution that will assist EKZ with optimizing reporting, planning and forecasting of their wind power projects with their goal to generate green electricity certificates as well as meet their corresponding return on invested capital. Christian Hürlimann, managing director of EKZ Renewables AG, expressed his excitement to implement Infor d/EPM as it will provide his employees with helpful tabular and graphical evaluations of their activities, which can help them derive practical recommendations for next steps. “With the introduction of our strategic performance management solution Infor d/EPM, we support the planning, reporting and analysis of the wind park portfolio of EKZ Renewables AG. This shows how versatile Infor software can be”, said Jörg Jung, managing director central and east Europe at Infor.

For Full Article, Click Here

Designer Series – JSON Converter Node

, ,

The JSON Converter node can be used to build a JSON object from CSV or XML, or to convert a JSON object to XML or CSV.

Under the input tab on the Properties, the input could be output from some other node, a variable, or a text string.

The output from the converter node can be used to saved to a file, in a data iterator, or in other reader nodes in your flow.

IPA Node Error – There is not one Actor for this identity

,

I was doing some work in Landmark and ran across an issue where my LPA node wouldn’t start in the grid.  I looked at the logs and saw the error “There is not one Actor for this identity: <IDENTITY>”.  Issues like this often present themselves when trying to log into Rich Client also.  In this case, it came back with a “logon failure” message.  When you come across issues like this, and you can’t get into Rich Client, the next step is to check the database.  For an error referring to actors and identities, the first table to look at would be IDENTITYACTOR in the Landmark GEN database.  In this case, I discovered that the record for the IDENTITY mentioned in the error had a DELETEFLAG that was populated with the UNIQUEID (meaning that it had been deleted).  I updated the record and set the DELETEFLAG = 0, rebooted my server, and the LPA node started right up.

Infor Launches Next Generation of CloudSuite CRM

Infor recently launched the next generation of CloudSuite CRM – Infor CloudSuiteTM CRM. This cloud-based customer relationship management (CRM) application is part of the Infor Customer Experience suite of solutions, and includes sales, customer service, marketing analytics and reporting tools. Infor CloudSuite CRM allows companies to manage the full customer life cycle in one environment – this helps them to capitalize on future sales opportunities and deliver exceptional services. The newest release of Infor CloudSuite CRM is built on Infor’s highly-extensible, framework, Infor Mongoose, offering a scalable product in an easy-touse interface where users can tailor the solution to meet their specific needs. “Infor CloudSuite CRM remains a key solution in Infor’s strategy and continues to receive significant R&D investment,” said Jason Rushforth, vice president and general manager, Infor Customer Experience. Sales teams can maximize customer interaction with access to better prospect and customer data. Additionally, Real-time access to operational and sales data gives a complete view of customer interactions that enables the sales team and other departments to make informed decisions throughout the sales process and beyond.

For Full Article, Click Here