Custom fields

Dastra gives you the ability to customize your forms endlessly

This feature is still in beta. It may still have some instabilities.

When to use custom fields?

There may be some information specific to your industry that is not present in the native fields of the treatment register, such as rights exercises, tasks, etc.

Dastra will allow you to create custom form fields that you can easily add to enrich the data entered.

Here is an example of a field configuration for the actor:

/IMAGE

And here is the result in the form:

/IMAGE

Functionalities concerned

Please note! Not all features are concerned by custom fields

You can customize the following forms:

• Treatment sheets

• Exercise of rights

• Tasks

• Assets

• Actors

• Measures

• Data sets

• Data fields

• Violations

• Risk assessments

Limitations on the number of fields

The amount of custom fields is limited depending on the plan you use. We invite you to consult the application's pricing page for more information on this subject.

Available field types

Dastra offers several types of custom fields:

• Simple text

• Long text

• Rich text

• Whole number

• Decimal number

• Date

• Date and time

• Check box (multiple response) (unfilterable)

• Check box (single response)

• Single selector

• Multiple selector

• Check box (Yes/No)

Using custom fields

You can:

• View and edit custom field data in the forms of each module

• Custom fields can be displayed in all the application's visualization tables. To display them, click on the table column settings button

• Custom fields are present in all Excel data exports. For more information on exports, see the page on exports
• Custom fields can be present in HTML, Word and PDF exports as an option (by checking the "Exportable in reports" box on the field in question)

• With the exception of multiple response fields, custom fields are all filterable via the advanced filter system
• Custom fields can be updated en masse in data tables

• Custom fields can be imported via flat files using the import system
• Custom fields are accessible and modifiable via all APIs. To do this, you will need to use the variable name assigned to each column. See the section on API modifications of custom fields

Setting up custom fields

• Go to your Workspace

• Click on the Workspace Settings menu on the left

• Click on the Custom fields menu

• Choose the module in which you want to add a custom field

• Fields must be created in groups. These groups can be positioned in a certain way in the form Click on "Create a group of fields"

Fill in the name and location in the form that you want

For some elements, it is possible to define the location you want in the form!

• Once the group is created, you can now drag and drop the field types you want to set up!

Fill in all the information! Click on save and that's it!

• Your first personal data field is in place!

• You can drag and drop to reorder the fields as you see fit.

Handling custom fields in APIs

Dastra allows you to retrieve, modify and create via the Rest API all entity values that include custom fields.

A "customFields" property will be available in all entities you retrieve in get in Dastra.c:

 {
   "id": 1234,
   "label": "Test asset",
   etc...
   "customFields": {
     "dpo_name":"jean-marc le dpo",
     "dpo_email":"[e-mail]",
     "dpo_habilitations": ["Expert","Consulting","Data Mapping"],
     "has_large_dataset":false,
     etc...
   }
 }s

To modify this property, you just have to post (POST) or modify (PUT) the element by updating the elements of the collection.

To collect the name of the custom variables, you must go to the custom fields configuration page.

Attention, all custom fields will be validated by the server. If a colonen is not present in the configuration, it will be automatically deleted.

If a field is not valid (for example, if it's not filled in even though it's marked as mandatory), it will raise an exception with the code 400

Limitations

You cannot filter custom fields of the multiple type (checkbox (Multiple) and selector (Multiple)). This is a known limitation that we are working on.