FASTER THAN EVER BEFORE
Features enables you to bring your vision to life
An object can be eg. assets, users, services, products, systems, computers, groups, software, cost centers, invoices, etc. Every object can be role based and searchable within a specific workspace. Objects can also have releated actions, cost, attachments or attributes.
Actions are functions related to a object and be connected to forms, dashboard, search results or external systems. Here is where we associate a object to automation. These can be role based.
Workspaces are a view or a filter objects for a specific use case, role, system and contains. The workspaces are role based and act as a portal within Onify. A workspace can also have shortcuts and bulletins.
Forms is a way to gather information to use in a automation (script, workflow). Onify has a built in form editor where customers can create and customize forms for any need. The forms are flexible and support both simple and more advanced form elements.
Dashboards is used to present information in a easy way. It can contain information from multiple sources and gives the user a good overview for eg. an employee or a customer. Onify includes a dashboard editor where customers can design their own dashboards.
Guides are a way to “guide” users in the right direction and help them make the right decision using a simple interface. This way users does not need any special skill to come to the correct place in Onify for their request. Guides can also be chained together.
Shortcut gives the user a easy “link” to different features in Onify like forms, dashboards, search, etc. Shortcuts also support badges to give the user more information about what is behind the link. Shortcuts can be added on a workspace or in the shortcuts menu.
Bulletins informs users about specific information and events and can be manually created and updated via the API. Bulletins can have diffrent status like informational, warning or critical. Bulletins can be visible in a workspace or in a search result.
The agent(s) is the part that does the integration and takes care of reading and writing to different systems, both on-premise and in the cloud. The Onify agent interacts with either scripts, systems or workflow engines. The agent is responsible for indexing objects (via the Connector) and automating processes.
The Connector is the component that index data into Onify. It indexes things like objects, users, events, options, etc. The connector supports multiple data sources like SQL, LDAP, REST, etc. Pipelines are created to streamline the indexing process using a chain of tasks that can be reused.
Workflows is a presentation of a specific workflow or process that can be initiated from Onify or a external system. This gives the user a clear view of where the process is. The process state and status can then be updated using the API.
Events is events that are releated to something in Onify, like objects or processes. It could be eg. events for a employee about changes done during the employees lifecycle.
Options is a way to manage lists especially for forms and can easily be managed in the admin interface. These can be role based and can be updated via the connector.
Strings is how we translate things in Onify. Strings can be used to translate forms, dashboards, options, bulletins, etc.
Domains is used to connect Onify to different federation (single sign-on) solutions. Using domains Onify can be multitenant and users from different domains can get different access. Onify supports both SAML2 and OAUTH2 for single sign-on like Active Directory, Google, Office 365 / Azure or Shibboleth.
Users are users logging in and using the system. How they login is configured in each domain. Each user has one or more roles that gives them access to different parts of Onify. It is also possible to add custom attributes for users and give access to objects based on these custom attributes. Onify is not the master for users, they normally comes from customer IDM solution.
Almost everything in Onify can be role based, like objects, workspaces, forms, dashboards, options, etc. Roles can be manually created or updated via API.
Onify has build in audit. This eg. means that if some submits a form, Onify will automaticlly store a audit record for this. No need to build your own audit system for your processes. These audit records can also be used in eg. Power BI or Qlik Sense for analysis.
Resources are custom files (eg. images, icons, css), temporary files and templates (forms and dashboards) used in Onify.