A Digital Service application is made up of data, definitions, and code. The data and definitions can be configured to suit your application requirements. For example, if you have an application for on-boarding a new hire, the data required in this application are the employee details such as first name, last name, employee ID and so on. How to display this data in your application is determined by using definitions such as view definition, record definition and so on. An application includes a set of such definitions that work with the application code and functions as per your requirements.
You can customize various functionalities and user interface of an application using the definitions through BMC Helix Innovation Studio. The following image provides a brief categorization of the available definitions:
Data definitions represent the data model or schema of an application and define the data objects that it uses.
Data definitions are of the following types (the example of the on-boarding a new hire application is continued below):
|Record is similar to a database table. A record consists of various fields.
Employee details, employee department, employee assets are different types of records you can create while on-boarding a new hire.
|Field is similar to a database column.
|The first name, last name, employee ID and employee department are the different fields of the employee details record.
Association defines the relationship between records.
|Employee details record can be associated to employee department record.
Named list is a reusable query that returns a logically-named set of data and settings.
You can create a named list for all the employees reporting to a particular manager.
Applications can be implemented to have any type of user interface as per your requirements. You can modify any aspect of the application by customizing views. Views allow you to modify the following elements:
- Arrangement of UI elements
- Color themes
- Add elements such as fields or attachments
The behavior of applications can be defined and configured in multiple ways. You can also define rules, conditions, approvals in your business processes. The standard features and elements of Business Process Model and Notation (BPMN) are used in the Process designer. Some of the features and elements are listed below:
- Flow of process activities
- Conditional gateways
- Nested processes
- Integration points