Configurability is a primary design principle behind Verne. An understanding of the key configuration concepts will aid everyone that is involved with a Verne implementation, from UI design to Infrastructure design. The relationship between the configurable elements is illustrated below.
Configuration of Business Services
One of the most fundamental concepts in Verne is that of a Business Service. The business service is a transaction on the register which allows a user to interact with the register. Typical interactions include creation, retrieval, update, removal or searching of the Entity Type primary to the particular register.
Verne enables, through the configuration of these business services, the implementation of all functionality related to managing a specific register type. This includes the implementation of registry components such as data input forms, business workflows, user dashboards, compliance and notification regimes, output documents and many other registry-specific components.
Configuration of a Business Service in a nutshell
Configuration of a Business Service typically involves the configuration of a UI form to capture user-entered data. The UI form is made up of a number of Form Fragments or reusable Components and includes various Business Rules to validate and enrich the data. The various pieces of data that are captured are represented in configuration as several data objects called Domains. The Domains are usually related to one another and therefore are versioned together in the form of a Dataset. Additional configuration maps this Dataset to a structure that allows the data to be stored in a data store. Once a Business Service is submitted and approved and all validation and business rules have been executed, it is applied on the register and generates a Filing. This is the complete and final representation of the submitted transaction and its data. In addition to the online workflow, a Business Service can be configured to be exposed as a Web Service to be consumed by third-parties to write transactions and query data in the register programmatically.
For a more detailed description of each of the configuration concepts shown in the diagram, see the Configuration Concepts page.
