Create or edit View Definition
Create View Definition
To create a View Definition, go to, Dashboard > Views > Add new
Edit View Definition
To edit a view definition, go to, Dashboard > Views > select View Definition > click Edit View Definition in the top right corner.
View Definition details
These fields are displayed when the user creates a record.
|ID||Required. A unique ID for the view definition used in the API. Once created this field cannot be modified.|
|Base record||Required. Select the base record.|
Enter a tooltip that is displayed when viewing the details of the record.
Required. Joins enable you to join the "from/base" record to the "to" (base) record. It connects one or more records in order to provide a collated view of data.
To relate between two tables requires you to determine the join condition. Click theoption to create a join condition. The following options display:
Click Save to save your input.
Setting permissions for a view definition allows you to view or edit permissions after the initial save. If no permissions are set, a warning is displayed. For more information on permissions, see Permissions.
Ensure that you set the required permissions for a view definition before you save it. If you fail to do so, users (including the creator of the view definition) are not allowed to view or edit it configuration of the definition.
To add permissions click the Enter the name of the group and select the required permission settings:button. The Add permissions box displays.
Adding read permission for a group allows you to:
The write permission for a group allows users of that group to alter the definition of the view type.
Allows you to set listing permissions for the record. The following options are available:
This allows you to set when logs for users actions like reading/listing a view definition should be generated.
Log reads can now be set on the view definition pages by any user who has permission to write/edit the selected view definition type. By clicking on the Audit logging switch you can set when logs should be made for this view definition. To create the logging permissions select the table you would like to record, who made the read (Log actor to) and what fields they accessed. You can choose to monitor log reads by a specific user or all users. Please note that this is separate to the inherent logging as part of the blockchain and is designed to facilitate the use of history as part of access control or triggers.
The following options are available:
You must create fields for the view definition to be able to save it. An error is displayed if you click Save before defining fields for the view definition.
Once you have created a record definition, make sure that you create fields. To add a field, click on the Click to add a field option in the right-pane.
|Required. The name for the field.|
Select the column in which the field should be displayed. The options are Left and Right.
In the Display Order field, you can also set the order in which the fields must be displayed. Select Display in tables if you want this field to be displayed when the records are listed.
|Tooltip||The tooltip is displayed when viewing the details of the field.|
|Display Name||Enter an alternate display name|
Mapped field: This displays the information from a field within one of the record definitions making up the view.
Switch case: A switch field works down a series of matching expressions and returns a value specified, or if none is matched, a default value. For instance, we might set switch cases of
Calculated field: A calculated field performs mathematical or string operations on one or more fields aggregated or unaggregated from the underlying data. For instance, we might sum
Record type: The drop-down displays the "base" and "where" record in the list.
Field: From the drop-down select a field either from the "from/base" table or from the "where" table to display its contents when the view is generated.
Tokenise values: The drop-down displays different hash functions. Select an option from the list or select Don't tokenise value if you do not want to encrypt the field value.
Set an override minimum security score to view this data when it contextually matches one of the following:
Separate permissions are required to read and write data. There are situations, especially in BPM workflows, where users may require only write access and no read access.
Click thebutton. The Add permissions box displays.
On this screen, you have to first select to "who" the permission is applied, and then, select "what" permission should be applied:
Click Save to save and apply the settings.
Copying and pasting permissions
Creating and applying complex permission can be time-consuming and therefore to simplify this, you can use the Copy/Paste option.
Once you have applied the required permission settings to a field, you can Copy the settings and apply to all other required field using the Paste option.
Click Save to save your changes. Click Revert changes to undo the current changes and revert to the last saved version.