Best practices

Keep the design of objects consistent throughout the entire user interface for easier navigation throughout different applications.

Consider the approach for the same functionality across all applications.  If other applications have similar behavior, make sure the application handles the process in the same manner. End users want consistency and assume taking the same action in one application should be done in the same manner as any other application.

Consider using Application layouts. Not every field is used or even necessary. Using an alternate layouts can help streamline the user interface. 

Consider notifying an end user when a process has been completed. End users want to know when an action they have taken is complete. Some options include using a status, workflow, or a notification. 

Consider whether you show/hide fields rather than enable/disable fields. Make it easy for an end user to understand why a field is disabled and what actions need to be taken for it to be enabled. All help text for fields should be clear and specific.

Consider using a row action or a field action. Row actions tend to get buried and they take the end user away from what they were doing.  If the action is tied to a specific field, perhaps a field action should be used instead. 

Consider the performance of the application and keep the number of clicks to process a transaction to a minimum. 

Avoid scrolling the best you can. Vertical scrolling is generally acceptable, but avoid horizontal scrolling. Horizontal scrolling on list view are acceptable, but avoid it in the detail view if possible.

Consider user navigation when designing your user interface. Spend enough time on your user interface design to minimize:

  • Unnecessary scrolling.
  • Excessive clicking.

Consider the tabbing order when configuring an application. Nextworld tabbing navigates the user from left to right and from top to bottom through rows. Organize fields that should be navigated:

  • From left to right into the same row across multiple columns. 
  • From top to bottom into the same row under one column.
  • Think about the field sequence from an end user's point of view as they tab through the application.  

Design applications so that users can view them on multiple devices. The field positions must not change when viewing applications on different screen resolutions. Optimize applications for:

  • Desktop view. For example, 1366 x 768px. 
  • Tablet view. For example, 768 x 1024px.
  • Mobile view. For example, 375 x 667px.

Hiding application components best practices

These best practices ensure that application developers hide application components such as actions, pages, rows, and fields consistently throughout Nextworld. Use application settings, control actions, and logic blocks to hide these components.

In applications, there are different ways that you can hide fields, pages, rows, and buttons from the user. How you decide to hide these things can depend on why you are hiding them. Sometimes hiding something changes the function of the application.

The different methods you can use to hide application components include:

  • Application settings
    • Create an application setting to hide application actions, pages, rows, and fields when doing so does not change the function of the application. For example, hiding fields that aren't relevant to the application when it is opened from a certain menu entry.
    • This can be changed through customization.
  • Control actions
    • Configure a control action for an application to hide application actions to change the function of the application or it is part of the design of the application that a user can't use a specific action. For example, hiding a Save button in an application where a user can't edit any fields.
    • This can't be changed through customization.
  • Logic blocks
    • Configure a logic block to hide application actions, fields, rows, and pages to change the function of an application or it is part of the design. For example, conditionally hiding and showing a page based on the value of a field or hiding the Edit button of a read-only application. 
    • This can't be changed through customization.

Hide individual fields instead of entire rows. That way if the field layout is later changed, no other rework is required.

Style Definitions best practices

Use the following standards when defining and implementing Style Definitions.

Style Definitions can be applied to dashboards or by using the Apply Styles action. For more information, see Style Definitions application and Apply Styles action.

Simple Clickable Link 

Always use display text size = Extra Small and Display Text Alignment = Center.  If the clickable link is used only within your own module, you can create your own standards by creating groups for the same function or role. For examples, see the deliveredSimple Clickable Linkfor Manufacturing in the Style Definitions application.  However, if you have a dashboard where clickable links may be used across modules, then a new standard needs to be determined.  

Field 

Below are the defined use cases when a style can be used on a field using the Apply Styles logic block action. If you need a different style for a use case defined below or if you have a new use case a new standard should be determined within application development. 

Use CasesStyle Defintion To Use
Comparing fields and style the field when the values are differentFieldComparisonStyle or FieldComparisonStyleReadView
Highlight the background yellow and use the indicator that shows the field has changed. We will leave the text color blank so that the tool would dynamically pick the right text color based on the user’s current theme. 
Indicating when a date field or transaction is past duePastDueDateFieldStyle or PastDueDateFieldStyleReadView
Text color is red. Currently, there is no visual indicator to the past due field.  This is currently being defined. 
Indicating when a field is conditionally required in an applicationFieldConditionallyRequiredStyle
The Conditionally Required field is set to true. This will add the required field indicator to field where this applied.
Indicating that additional actions needs to take placeStandards are currently being defined for this use case.
Increase focus on an item by increasing textStandards are currently being defined for this use case.
Highlight a negative value either cost or quantityStandards are currently being definied for this use case.