Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. System-wide - applies to all protocols

  2. Collection Protocol level - overrides the system setting for that protocol

Collection Protocol Level

...

To import/export workflows:

  1. Go to the collection protocols overview page.

  2. Click on the 'More' button.

  3. Select Export Workflows or Import Workflows.

...

Custom Fields In CP level JSON (v9.0)

CP JSON is enhanced to show the custom fields. This is to avoid any additional configuration for custom fields within the dictionary. 

The UI automatically appends the CP-specific custom fields and are displayed on add/edit/overview pages.

Note:

...

If you make any changes to the fields in the form, it is reflected on data entry screens.

...

If you want to add skip logic, download the form xml → add the skip logic → import the xml. Please refer to the skip logic for more details.

...

...

This will only work if you have not manually configured the custom fields within the “dictionary” section.

System Level

...

Once JSON is created for the data dictionary, you can set it for all CPs at the system level. Refer to the steps:

...

  1. Go to CP Overview → More → Import workflows

  2. Choose the file EmptyWorkflow.json and import it. Once you import this, the CP level workflow will be erased.

...

System Level

If you want to replace the file uploaded at the system level with the default file attached: Navigate to Settings → Biospecimen→ System Workflows

...

Custom

...

Fields Configuration

CP Level (v9.0)

The UI automatically appends the CP-specific custom fields and are displayed on add/edit/overview pages. This is to avoid any additional configuration for custom fields within the dictionary. 

  1. If you make any changes to the fields in the form, it is reflected on data entry screens.

  2. If you want to add skip logic, download the form xml → add the skip logic → import the xml. Please refer to the skip logic for more details.

  3. Once the field is deleted, the previous data entered for the field is also deleted.

  4. This will only work if you have not manually configured the custom fields within the “dictionary” section.

System Level

System-level JSON is enhanced to show the custom field in any CP to avoid the CP-specific dictionary configuration for custom fields. The UI automatically appends the CP-specific custom fields when a system-level dictionary is used for displaying the add/edit/overview pages. This is subject to the condition that the system-level dictionary doesn't have any custom fields in it.

This allows you to define a system-wide dictionary and yet will enable you to define CP-specific custom fields without requiring them to create/maintain a CP dictionary.

Info

Pre-requisite:

...

CP should not have any CP level workflow attached so that it will use the system level workflow as default.

This feature is supported at the below levels.:

  1. Collection Protocol Custom Fields

  2. Registration Custom fields

  3. Visit Custom fields

  4. Specimen Custom fields

...

Default JSON Files

...

Default JSON files for the configuration that contains - dictionary (all fields for the participant, visit, and specimen), default participant-list, and specimen-list columns and filters are added below

...

  1. Participant centric workflow:<your openspecimen domain>/rest/ng/docs?filename=participant-centric-workflow.json

  2. Specimen centric workflow: <your openspecimen domain>/rest/ng/docs?filename=specimen-centric-workflow.json

Expand
titleClick here to see all example

...

JSON codes...

...

Child pages (Children Display)