As you might have heard, we’ve been working on a fully cloud-based, vendor self service solution for about a year now. We have worked with several customers to create a solution that is simple, intuitive, and brings instant value to any organization dealing with vendors and suppliers. Join us on Thursday June 6th (9am PST) as we do a walk-thru and a public Q&A. The webinar will feature the following modules and functionality:
Vendor OnBoarding
Vendor Check Requests and Invoice Submissions
Purchase Requests
Routing, Approvals, Document Management, Audit, Integration, and much more
Infor’s newest partnership is with Destination XL Group (DXLG), the industry’s leader in men’s big and tall apparel. This partnership allows DXLG to increase their market share and top line sales, improve customer segmentation and drive state-of-the-art marketing activities. Infor Alliance partner Three Deep Marketing will work alongside DXLG to leverage Infor’s rich breadth of customer engagement solutions to deepen relationships with existing and new customers by better understanding preferences around promotions, pricing and assortment. DXLG will implement Infor CloudSuite CRM, Infor Marketing Resource Management (MRM), Infor Omni-channel Campaign Management (OCM), and Infor Loyalty powered by CrowdTwist to provide relevant communications across all channels. “With Infor’s end-to-end customer engagement solutions, we can understand our customers better, produce rich and deep customer profiles and drive incredibly smart segmentation to connect and engage with our customers in a more meaningful and targeted way,” said Jim Davey, CMO of Destination XL Group. Infor’s Retail division now supports more than 2,500 global fashion, retail, and grocery brands that work to modernize operations by taking advantage of the latest consumer and business technologies — mobile, social, science and cloud.
When you configure LSF for ADFS, you will need to make some changes to your LBI configuration so that users will be able to access LBI with the userPrincipalName.
The first thing you need to do is ensure that you have a user in Lawson security where RMID = SSOP = UPN (userPrincipalName). The RM User that is used to search LSF for LBI users must have an account where RMID and SSOP match. It is recommended that you have a new AD user created for this purpose (such as lbirmadmin).
Add the new user to Lawson, ensuring that their ID and SSOP values both use UPN. Also make sure the new user is in the appropriate LBI groups for LBI access.
The next change will take place in the sysconfig.xml file located in <LBI install directory>/FrameworkServices/conf. The ssoRMUserid should be the UPN of your LBI user mentioned above. After you make these changes, restart the application server, clear the IOS cache in Lawson, and try logging into LBI.
https://www.nogalis.com/wp-content/uploads/2019/06/Configure-LBI-for-ADFS.jpg427470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-11 11:22:102024-10-10 10:22:44Configure LBI for ADFS
If you update your LSF core technology, and subsequently find that your SSO applications (such as LBI or MSCM) produce a 500 service error, you probably need to update your DSP install on the host server for the SSO application. Please see our article archive for instructions on how to update and reconfigure DSP.
If you get a “NoClassFoundError”, you may need to add a new class path to your JVM properties in WebSphere. Figure out which class is missing and add the path to the JVM properties, then restart your application server and check to see if the issue is resolved.
https://www.nogalis.com/wp-content/uploads/2019/06/500-Error-in-DSP-Applications.jpg429470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-10 08:41:492019-06-07 17:42:08500 Error in DSP Applications
Nothing makes an organization run more smoothly than the right Customer Relationship Management (CRM) system. However, you must regularly evaluate if your current system is doing the job for your growing company. Barrett Cordero, President of BigSpeak, a leading global speakers bureau, recently learned that their CRM system needed updating. He shares seven signs below that you should look for to know when it’s time for you to update your CRM system to something better.
It’s unreliable – If your CRM used to work perfectly but now can’t be relied on 99% of the time, it’s time to switch systems.
It doesn’t do mobile – If you can’t access your CRM by phone, you miss opportunities.
It doesn’t integrate with other software systems – integrating with other systems (sales, contracts, websites) is a huge time saver.
It’s user unfriendly – friendly deisgn makes for quick and easy navigation (again, saving time).
It doesn’t work well across departments – If your CRM works well for one department but bad for others, then it’s bad for your entire company.
It doesn’t have growth potential – If your CRM doesn’t have the potential to grow with your company, then it’s time to find the kind of CRM that can grow with you.
It’s all you talk about – When you reach this stage, it’s time to do the research, take the leap and spend some time getting a new system in place.
It may take a while to realize you need to change your CRM system. But when you first notice it, take immediate action and start finding a newer and better system to help your business go further.
https://www.nogalis.com/wp-content/uploads/2019/01/crm-customer-relationship-management-loyalty.jpg512700Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-08 13:11:082019-06-06 13:11:45Seven Signs Your Business Should Move To A New CRM System
If you see some error messages when you first open IFS (similar to the message below), make sure that all components of the Application Server have been installed.
These are installed in the Server Management area > Add Roles and Features. The Application Server role is delivered with PowerShell commands that are required for IFS to run.
https://www.nogalis.com/wp-content/uploads/2019/06/Web-Page-errors-when-logging-into-IFS.jpg431470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-07 11:02:292019-06-06 11:03:13Web Page errors when logging into IFS
If you have installed a new DSP for your LBI server, it is very simple to point LBI to the new DSP install.
First, update the sysconfig.xml file located at <LBI Install Directory>/FrameworkServices/conf. Look for the old DSP name and update it with the new name. Then, be sure to change the class paths in WebSphere > Your Application Server > Java and Process Management > Process Definition > Java Virtual Machine. Also, update the Custom Properties at the same location.
Restart the application server.
https://www.nogalis.com/wp-content/uploads/2019/06/Update-DSP-for-LBI.jpg433470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-06 09:23:282019-06-05 12:23:51Update DSP for LBI
When you journalize a Recurring Journal Entry, it goes through the standard JE approval flow. There is no delivered flow that looks at the Recurring Journal.
If you want the Recurring Journal Entry to be approved once when it is created and not approved each time it is journalized, a Custom IPA will need to be created to do that.
If you want changes on the Recurring Journal Entry to be re-approved when generated, make sure your custom trigger kicks off the IPA every time the Recurring Journal Entry is released.
You may then want to modify your JE approval flow to exclude transactions with the RJ system code since it was already approved – both initially and when it was changed.
https://www.nogalis.com/wp-content/uploads/2019/06/How-are-Recurring-Journal-Entries-Approved.png.jpg427470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-05 11:02:012019-06-06 10:59:19How are Recurring Journal Entries Approved?
Infor’s latest channel partner is with Mashfrog, an IT and digital services company based in Italy. The partnership is designed to help manufacturers in both the fashion and industrial industries in Italy to modernize through technology and pursue digital transformation programs. Mashfrog will have access to the Infor CloudSuite Fashion (based on Infor M3) and combined with the company’s service delivery credentials, it will help local businesses to capitalize on digitization, drive performance and expand market share. “Infor’s continued innovation and cloud first strategy is impressive and we are delighted to join forces with them to consolidate our proposition for the Italian market,” comments Federico Zuin, Mashfrog Group CEO. “Fashion and apparel companies face huge challenges and complexity, but through making the best decisions about where to invest in digital capabilities, they stand to win market share in what has become a global mega industry. Infor’s cloud first strategy combined with deep domain functionality and industry expertise, together with our credentials, industry knowledge and experience in service delivery, mean that we have an impressive proposition to take to the Italian market.”
You may find the need to install or update DSP for your SSO applications, such as LBI or MSCM. DSP allows these external web application to authenticate against Lawson for Single Sign-On.
Information you will need:
The password for ssoconfig
The passkey used to install your current DSP version (if applicable)
FQDN’s for your LSF server and the server that hosts the application for which you are installing DSP
Credentials for an admin account (usually lawson)
First, download the latest DSP jar file from InforXtreme.
It is best practice to back up your ldap instance before you begin the install.
On the server of the SSO application, open a command prompt as administrator. Navigate to the directory where you saved the DSP install file.
Type command java -jar <DSP file>.jar. This will open the install wizard.
Enter a new configuration passkey. NOTE that if you are updating an installed DSP, you will need to know what passkey was used to install it.
Give your DSP instance a meaningful name
Set the location where you want the install files saved, and set the java location.
Mingle DSP install is a different process not addressed in this article.
Provide the FQDN of your LSF server. The standard and secure ports can be found in your LSF install log. Enter the password that you use to run ssoconfig.
Enter account information with administrative privileges in Lawson
Enter the appropriate values for the server that hosts your SSO application
Click Install
Update the JVM custom properties with the new install information (if necessary)
Install or update your security application in WebSphere. The install file lawsec.ear can be found in <DSP install directory/jar/secondary
Run a smoke test against the new DSP install at https://<application base url>:<port>/sso/SSOConfig
https://www.nogalis.com/wp-content/uploads/2019/06/Installing-DSP-for-Authentication-Against-LSF.jpg427470Angeli Mentahttps://www.nogalis.com/wp-content/uploads/2013/04/logo-with-slogan-good.pngAngeli Menta2019-06-04 08:09:292019-06-03 11:50:03Installing DSP for Authentication Against LSF
