Ometa Nexus

Ometa Nexus is our new main user interface. It is a part of the obiz-suite that exists in our core service. It will gradually replace the Ometa Business Connector.

Currently Ometa Nexus consist of 3 main topics:

• Object Manager
  • Object & View List
    • Modern Forms
    • Cards
    • Gantt Chart
    • Timeline
• Translations
• Lifecycles

The user can use Ometa Nexus by navigating to "Core Service Url/obiz-suite/nexus/object-manager".

Navigating within the Ometa Nexus

To access the Object Manager, Translations, or Lifecycles, use the side menu on the left and select the desired section.

To switch between applications like the Case Management Dashboard or the Ometa Nexus, use the menu button located at the top right of the screen.

Object Manager

Object List

The Object List displays all available objects as tiles. You can click an object to navigate to its View List. Objects can be filtered by name or tags for easier searching and organization.

View List

The View List shows us a list of all our views in an object. You can also search in this list.

You can also create new Views, however this is currently limited to Timelines and Gantt charts. Support for additional view types will be added as more features are introduced to Ometa Nexus.

View Settings

Clicking on a View opens the View Settings, where you can further customize how your data is displayed. The available visualization modes depend on the type of view:

• Single Record views can be shown as a Form, Modern Form, or Card.
• Multi Record views can be displayed as a Table or Card.
• Create and Update views support only Form and Modern Form layouts.

This allows you to be flexible to further edit each view to best fit your workflow and however you want it to be presented.

After making changes, the user can navigate to "Layout" for further editing based on their selected Visualization mode.

Modern Forms

The Modern Forms of our View allows us to set up different forms for different screen sizes. This means moving the View Fields across multiple columns that the user can create without any CSL.

Note

Using the Modern Forms together with CSL custom layouting CSL.view.createViewFieldGroup is not supported.

Form Sizes

The user can set up forms with up to 3 columns for extra small and up to 4 columns for everything else. The form sizes include:

• Extra small devices (portrait phones, less than 599.98px)
• Small devices (landscape phones, 600px and up to 959.98px)
• Medium devices (tablets, 960px and up to 1279.98px)
• Large devices (desktops, 1280px and up to 1919.98px)
• Extra large devices (large desktops, 1920px and up)

The form sizes are important because they will determine which of the forms are going to be used automatically based on the screen size. Changing the window size will also determine the form that is going to be shown. The user can also decide to use one form across multiple screen sizes. This means that the largest form created by the user is going to end up being used on the bigger screen sizes.

Created Form and example in ADM

The View Fields can be added by dragging them onto a column. Toolbox elements like headers are added the same way. To remove a View Field or a Toolbox element from the column, the user has to drag them back to the View Fields List on the left.

Note

To save our form, Create and Update views require every View Field to be used in every form size. Single Record views don't have this necessity.

Here is a form that we have set up with 3 columns, 3 headers and the View Fields spread across the columns.

This is how this form we just created looks like in ADM.

Form Actions

Adding a Form Size

To add a new Form Size to the form, the user has to click on the add form size button.

A popup will show up on screen that allows you to change the screen size and the column size of this form.

Deleting a form size

To Delete a form size, the user has to open the drawer first by clicking the following button.

The user can then delete the form size by clicking the delete form size button.

A popup will follow up stating that your actions cannot be undone. This is true unless you exit the modern forms page without saving, but that means that you will lose any other changes that you haven't saved yet.

Adding and Deleting a Column

By clicking on the column settings icon (The 3 dots), the user can add or remove a column. Removing a column will move all the View Fields in that column back to the available View Fields list. Toolbox elements such as Headers will be lost.

Note

You cannot add more than 3 columns in an Extra Small Form and 4 columns for every other Form Size.

Deleting a Form

The Modern Form can be deleted to start all over again. This action is also necessary if the user wants to go back to using standard non modern forms. This can be done by clicking on the remove form button at the right side of the page.

The app will navigate back to the View List after removing a Form. This action cannot be undone. This time we mean it.

Nested Forms

Nested Forms allow us to have columns in our columns. This can be done by dragging a Nested Form from the Toolbox Options into a column. Our Nested Forms function the same as our regular columns. This means that we can drag any View Field or Header in them. We can also change the amount of columns a Nested Form has.

Note

You cannot add more than 3 columns in a Nested Form or have less than 2 columns.

Context Menu

Hovering on top, between or under items will indicate where the context menu can be opened. This allows us to add any View Field or Toolbox option without having to drag them. Adding a View Field through the context menu that was already in a column will remove it from the previous column first.

Cards

Simplified card configuration, you can now configure cards - a frequently used UI component - without the need for custom coding managed previously with the custom renderer.

Note

Beta Notice: Please note that this card configuration feature is currently in Beta. While fully functional, you might encounter minor visual or rendering imperfections. We are actively working to refine and enhance this feature for upcoming releases. Your feedback during this beta phase is highly valued!

Here are some examples of cards you can create using Ometa Nexus, all without writing any custom code:

Card Editor

The Card Editor is organized into three main sections:

1. Elements List: Displays available card elements that can be dragged into the editor.
2. Editor: The workspace where you arrange and customize your card layout.
3. Element Settings: Provides configuration options for each selected element and the card itself.

Below, we’ll explore each section in detail.

Elements List

You can build your card layout by dragging elements from the Elements List into the Editor workspace, and rearranging them as needed. Each element serves a specific purpose, such as displaying text, colors, or icons. The Row Template element enables you to loop over the data context provided by your view, allowing you to dynamically display multiple items within your card. Note that Row Template is a Multi Record exclusive feature where only one can be added per card, and it is hidden when the rendering mode is set to "Multiple" (explained later).

Editor

This is where the fun begins!

The Card Editor lets you build flexible card layouts by dragging and arranging elements from the Elements List. You can place elements such as text, colors, icons, and buttons anywhere within the card to control exactly how your data is presented.

Each element can be individually configured, including setting up click actions for interactive behavior. Click actions are supported on the main card, as well as on icons, text elements, icons within text, and buttons, allowing you to create dynamic and interactive cards without custom code.

Element Settings

The Element Settings panel provides configuration options for each element you add to your card layout. When you select an element in the editor, its specific settings become available, allowing you to customize actions, margins, paddings, colors (including dynamic color assignment based on your dataset), borders, and more.

The Card itself also has settings, such as the rendering mode. For Multi Record views, rendering mode lets you choose between displaying a single card with vertically looping data (Single Rendering + Row Templates) or multiple cards on the screen, where you can control the gap, number of cards per row, card size, and other layout options.

Context Records

Cards are highly flexible because they allow you to reference context fields from your view directly within card elements. This enables dynamic rendering of colors, text, icons, and other properties, so each card displays data relevant to its context.

To use a context field, simply reference it as {$Label/Value: ContextName} within an element. This will display either the label or value from the context record, depending on your selection.

For example, you can configure cards to show different colors and icons based on context fields, ensuring each card visually represents its unique data.

Within the Editor, you can see two columns: the first column contains a text element and an icon, while the second column holds two text elements. The icon uses a context field to dynamically display the appropriate icon based on the underlying data, ensuring the card visually adapts to different scenarios.

Both the background color and border color of each card can be dynamically set using context fields. This allows every card to visually adapt based on its data, ensuring unique appearance where needed.