How-toInfor OSApp Designer / Homepages

Infor OS App Designer: How to Build Apps and Homepages

Question
infor os app designer

Also searched as

  • infor os homepage designer
  • how to create a homepage in infor os
  • infor os build custom app

Short answer

In Infor OS, apps and homepages are assembled in the portal: you register an app (a URL, launch parameters and an icon), place it in a role-based set of apps, and compose homepages from widgets and links. The tooling and menu names differ by release, so confirm them in your tenant, but the process and the governance below hold.

Applies to: Infor OS Portal in CloudSuite and OS enabled on-premise installations; menu names and designer capabilities vary by release and by what your administrator has enabled

How to create an app and a homepage

  1. 1Sign in as a user with the administrator or designer role for the Infor OS portal and open the administration or designer area.
  2. 2Define the app: a name, an icon, the launch URL or application reference, and any launch parameters such as the company or the form to open.
  3. 3Assign the app to security roles or user groups so it only shows for people who should have it.
  4. 4Create a homepage and add widgets: links, key figures, lists, or embedded content from the application.
  5. 5Arrange the layout for the audience, with the five or six things that role does most at the top.
  6. 6Publish to a test group first, review on desktop and mobile, then release to the target roles.
  7. 7Document the app, the owner and the change process so it does not become orphaned.

Think in roles, not in apps

The mistake in portal design is to expose every function to everyone. A buyer, a planner and a controller need different starting points. Define a short list of roles, map the ERP security to them, and design one homepage per role with its daily tasks and a handful of figures.

Because security is enforced by the ERP behind the link, the homepage is a convenience layer, not a control. Do not rely on hiding a link as protection. Make sure the underlying application roles are right.

What belongs on a homepage

Good homepages hold actions and exceptions: tasks awaiting approval, late orders, items below safety stock. Poor ones hold decoration. Each widget should answer a question the user asks every day, and link to the place where they act on the answer.

Keep data widgets light. A widget that runs a slow query on every page load will make the whole homepage feel broken. Where a number is expensive, source it from a scheduled extract and show its refresh time.

Governance and change control

Designer access is a privilege. Limit it to a small group, require a test-first process, and keep a record of what was changed and by whom. An accidental change to a shared homepage affects every user at once.

Plan for upgrades. Custom apps that depend on hard-coded URLs or undocumented parameters break when hosts or versions change. Prefer supported launch methods and record dependencies.

Try it here, free

IBM i OS Upgrade Readiness Checklist

Open full tool

A grouped checklist covering planning, backup, compatibility, the upgrade weekend and validation for an IBM i operating system upgrade.

Common pitfalls

  • !Treating a hidden link as a security control.
  • !Building one giant homepage for all roles.
  • !Putting slow live queries in widgets that load for everyone.
  • !Giving too many people designer rights.
  • !Hard-coding environment URLs, which then break at the next move or refresh.

How an ERP-grounded AI assistant handles this

A natural-language entry point can sit beside the homepage: instead of navigating to a report, the user asks the question. ERPray provides grounded answers and dashboards over the ERP, read-only and role aware, and can be offered as an app link from the portal. For on-prem estates, the model and data stay inside your network.

See ERPray

Frequently asked questions

What is Infor OS App Designer?

It is the tooling in the Infor OS portal for defining apps and composing homepages. The exact name and features differ by release, so check which designer capabilities are enabled in your tenant.

Who can create apps and homepages?

Users with the designer or administrator role in the portal. Keep this group small and use a test group before publishing to everyone.

Does hiding an app link secure the function?

No. Security is enforced by the application and its roles. Hiding the link only changes what users see, so confirm the underlying role design.

Can I build a homepage per role?

Yes, and it is the recommended approach. Assign homepages to roles so each group gets its own tasks and figures, and review them regularly.

Related

How-to

How to Set Up SAML Single Sign-On for Infor OS

Infor OS can trust your corporate identity provider, such as Microsoft Entra ID or Okta, through SAML 2.0 federation. You exchange metadata between the two sides, map a stable identifier such as the email or user principal name to the Infor user, and then test with a pilot user before switching everyone over.

How-to

How to Create an .ionapi File and Service Account in Infor OS

An .ionapi file is a JSON credentials file you download from ION API after registering an Authorized App of type Backend Service and creating a service account for it. It carries the tenant, client id, client secret, the token and authorization endpoints, and the service account keys that your scripts or integrations use to request an OAuth 2.0 access token.

How-to

Infor OS Usage Limits: What They Are and What to Do When You Hit Them

Infor OS limits how hard clients can call its services, most visibly through the ION API gateway, and answers over-limit calls with HTTP errors such as 429 rather than silently dropping them. Exact numbers depend on your tenant and contract, so confirm them with Infor, then fix the cause: chatty clients, missing caching, or polling that should be an event.

How-to

How to Add a Personalization Script to an M3 H5 Panel

M3 H5 lets an administrator attach a JavaScript personalization script to a specific panel of a specific program, using the MForms client API to read fields, react to panel and field events, and adjust the UI (hide fields, set defaults, validate input) without modifying the underlying M3 program. Scripts are written and attached through Personalization mode in H5, saved against the panel/program combination, and deployed to the users or roles who should see the behavior.

Error fix

Fix a 401 Unauthorized error from Infor ION API

A 401 from ION API almost always means the credentials in the .ionapi file no longer match what ION API Gateway expects - not that the password is simply wrong. Check whether the Authorized App or service account behind the file was revoked, regenerated, expired, or issued for a different tenant, then re-test with a direct OAuth2 client_credentials call before touching any calling code.

Error fix

Diagnose and fix a failed BOD document flow in ION Desk

A Document Flow showing Failed in ION Desk means a BOD (Business Object Document) stopped either at schema validation, at the mapping step, or at the target application. Open the failed instance's detail to see the exact failing element, fix the source data or mapping, then use Resubmit rather than re-triggering the original transaction to avoid duplicates.

AI for ERP

AI Agents Over Infor ION API, BODs, and the Infor Data Lake

Build AI agents on Infor ION API Gateway, BODs, and Data Lake, alongside or instead of Infor's own GenAI features, with your choice of model and hosting.

AI for ERP

Infor M3 AI: A Practical Path from MI Programs to a Private Assistant

Infor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.

Stuck on Infor OS?

Talk to engineers who work inside Infor OS every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

Integrations

Software