Widget SDK lime update to match current cloud version of @infor-lime/core?

I have the latest SDK from github and have been working on some new Widgets. I would like to customize some of the Infor Standard widgets, so I have been using the f12 dev tools in my browser to get the source code. The problem I run into is there are methods in lime (usually in IWidgetContext) that are being called in these Infor widgets that don't exist in the lime version we get with the SDK. Is there a newer version of lime that is more up to date with the lime version used in the cloud tenants? They use @infor-lime/core, which we can't access in the SDK. Because of this, if we make a change and then try to package it, we get errors from the linter and it fails to build.

Also, I have heard that all the standard widgets from Infor are available to download, but I haven't found them anywhere. Does anyone know where I can find these so I don't have to convert source code from the F12 dev tool?

Find more posts tagged with

Widget Development

Accepted answers

All comments

unknown

Apparently, the SDK is ONLY for homepages, not for anything with Portal OS or side bar widgets in CSD, so they do not include any of the portal OS or other methods that the Infor Widgets use from lime.

unknown

Hi,

The widgets built with the Homepages SDK are compatible but there is some Portal specific functionality that is only available for Infor Application teams and those will not be added to that SDK since it is for Mingle Homepages. You can use the Homepages SDK to build contextual widgets, but it's recommended to use the Infor OS App Designer for such tasks.

If there are scenarios where it's allowed to edit standard widgets, then they need to be available as source code with license information etc. Using the browser dev tools to hijack JavaScript files and updating them is questionable and not allowed. You don't have the right to edit widgets, it does not matter if they are possible to download even, it does not give you right to modify.

unknown

The App designer is a great idea but is 2-4 years away from being useful, Mongoose only has documentation, examples, and tutorials for M3 customers, and the SDK is only for Homepages, which is no longer even a "thing" with CSD. The push from Infor is Workspaces, Portal OS, and "get rid of context apps, use widgets instead".

Infor forced all of us CSD customers to switch from Mingle to Portal OS, is actively pushing Widgets and Workspaces, and took away functionality for existing Context Apps so they stopped working. The only tool we are given to replace context apps and build widgets for Workspaces is the App Designer? All I'm asking for is to have an SDK to be able to build the context based widgets we need to continue to do business. The Widgets SDK is close, it is just missing all the new lime classes and methods.

Without an SDK to test code, the alternative is to package it and test it in our TST tenant, making changes until we get the result we are after. Since there is no documentation or SDK for any of the functionality we need, the only place to find code syntax or examples is to look at the Standard Widgets, a practice I was taught by Infor people. Once I know how to write working code to get the results I need for my company, I will write my own widget to use in production. Give us an SDK, document all the classes and methods, and give us working code examples for each one, and we won't have to look at your standard code to figure out how things work in Portal OS for workspaces and CSD. Thanks!

unknown

The OS Portal specific functionality that you refer to that have been added is not something that you should need to use. There is some very limited functionality in there. The only thing I can think of that might apply to CSD would be getting default values for the widget, from the global settings, instead of on a setting on the widget. It's the company/userid combination from the User settings for CSD workspaces. However that functionality is not something that is released for customers to use. Using anything that is not documented or supported is a risk as those things might change without prior notice.

Can you please elaborate on "took away functionality for existing Context Apps so they stopped working". Context apps and a web widget are almost the same thing. There is one message to change the hight that is no longer supported but you have much more flexibility with the Smart Panel then what Mingle had with the context panel. There might be some context apps that are discontinued, is that what you are reffering to?

I'll take your feedback with me and forward it to the Product manager as well. I'm sure it would be useful to get some more insights in "the functionality that you need" so that we can meet those requirements with the low code no code solutions that are offered.

Thank you for your answer.

Copyright © 2025 Infor. All rights reserved.