Using a UI Pattern with a condition is the recommended best practice. UI Patterns allow for centralized management, reuse across forms, and declarative logic that is easier to maintain than scattered JavaScript or API scripts. Form Rules are also valid but are specific to a single form, whereas UI Patterns promote component reuse.

Within a Mashup, relative API paths need to be resolved based on the Mashup’s runtime context (e.g., /m3api-rest). The preview might use a different base URL. The correct solution is to ensure the data source configuration in the widget uses the appropriate context variable (like `{{context.m3}}`) to construct the full endpoint URL, rather than a hardcoded relative path.

A mobile-first, single-column approach is the industry best practice for responsive design. It ensures core functionality is accessible on small screens and typically provides a clean, scannable layout that scales well to larger screens by utilizing available width. Designing for desktop first often leads to cramped, unusable mobile experiences.

Filtering at the data source (in the SQL view or within the M3 API program itself) is the most secure and performant approach. It ensures only the relevant data subset is retrieved from the database and transmitted to the client, adhering to the principle of least privilege. Client-side filtering (options 0, 2, 3) exposes all data to the user and can cause performance issues with large datasets.

Encapsulating complex business logic into a single server-side endpoint (a custom M3 API or Logic service) is a core best practice. It improves maintainability (logic is in one place), security (logic is executed server-side), reusability (other clients can use the same endpoint), and provides a cleaner separation between UI and business logic. While IPA (option 2) is also valid for long-running processes, a custom API is often more direct for transactional sequences.

The primary bottleneck is network latency and the overhead of multiple HTTP requests. Reducing the number of round trips to the server is the most impactful optimization. Consolidating calls into a single, composite data fetch (via a custom API or a well-designed existing one) dramatically reduces load time. Caching (option 1) helps subsequent loads but not the initial one, and hardware (option 0) addresses symptoms, not the architectural root cause.

Workspaces in Infor OS are a fundamental security and organizational construct. Assigning a Mashup to a Workspace acts as a permission filter. Only users who have been granted access to that particular Workspace will see the Mashup in their Home Page navigation. This is a key method for tailoring the user experience and access to functionality based on role or department.

For forms built using the Infor OS Form Designer, the layout and field bindings are managed declaratively within that tool. You must first open the form in the Form Designer to see its current structure, identify the relevant data source (likely an API like CRS610MI/GetItem), and then add the new field from the available fields in that data source to the desired panel. This is the standard, low-code approach for form modification.

‘Execute JavaScript’ is chosen when you need programmatic control over the action. This includes interacting with the Mashup’s runtime state (e.g., getting input from a field, checking a toggle), validating data, calling multiple APIs conditionally, or transforming data before navigation. ‘Navigate to URL’ is for simple, direct navigation without client-side logic.

Using a UI Pattern with a condition is the recommended best practice. UI Patterns allow for centralized management, reuse across forms, and declarative logic that is easier to maintain than scattered JavaScript or API scripts. Form Rules are also valid but are specific to a single form, whereas UI Patterns promote component reuse.0