OMNIA 3 Application Introduction
Business applications, in the OMNIA platform, are generated from the model. They can be used via the API directly or via the user interface.
2. Understanding the menu
Via the user interface, when you login and select a tenant, you will be shown a default menu in the sidebar that allows you to access the different options.
The organization of the menu is:
- Homepage: A shortcut back to the homepage.
- Documents: Contains all of the modeled Documents.
- Configuration: Contains all of the modeled non-document entities: Agents, Resources and Generic Entities.
- Series: Contains all of the modeled Series.
- Dashboards: Contains all the modeled Dashboards.
3. Using the application
Every application modeled will have its own usage flow and criteria. However, the general logic will be:
- Agents, Resources and Generic Entities must be created first, as they can depend on each other, but cannot depend on Commitments, Events or Resources.
- Every Entity instance of a specific type must have a unique Code. On most Entities, the Code is inserted manually by the user, and it can be suggested with behaviours. For Documents, non-root Generic Entities, Events and Commitments, it’s automatically calculated by default - be aware that Documents’ Code is automatically calculated by concatenating their Serie and Number when saved, even if you change Code’s value.
- Every Document has a Serie associated. This means that you must configure that document’s serie before being able to create documents.
- Commitments and Events cannot be created separately, and only exist in the context of documents. Generic Entities may also, if marked as non-root, be in this scenario, except they can exist in the context of any other document type.
- After having all this information, you can create Documents. Commitments and/or Events are displayed as “lines” in the form, if using the application via the OMNIA UI.