Fields
Last updated
Was this helpful?
Last updated
Was this helpful?
Fields are a powerful and extending feature within OpenProcess.
They enable data from online forms to be mapped over into OpenProcess, as well as, enabling those licensed for OpenProcess Flex, to add subsequent data to a process after it was started.
There are four categories of Field.
1) Non-geolocation based process field (passed from a form)
2) Geolocation based process field (passed from a form)
3) Mandatory fields (added during the process completion)
4) Case Fields (only available in IEG4 applications currently)
Whilst in Process Set up, one can see the Fields tab. This illustrates the existing fields present and also provides the means to add a new field:
Once you've clicked Add Field, you are presented with the following options:
For each field you must provide:
Label - this is the user facing name that will be presented adjacent to the value of the field
Type has the following options:
This is part of OpenProcess Core so all users irrespective of licensed products will have this option.
Choice - this field type is used in mandatory fields that a user needs to complete manually. The different options provided can be used to drive different branches of a process. The following illustrates an example of a Choice field:
Geographic Location - this choice should be used where a geographical location will be passed into the process. This could be provided either by an online form or within the Start Process function. An important element of connecting the geolocation to the process is to set it in the Process Details tab. I.e. create the geographic location field and then set it here:
This will only work if eDesigner - Geopack is licensed.
Code - this is the technical and unique identifier of the field. This is used for linking to eDesigner built forms and in .
Single Line of Text - this field type will accept a string of information with a maximum of 500 characters. This is how data from online forms will be passed and can also be used to capture mandatory information where is licensed.
Note that you provide a Label for the choice, which officers will see and select as well as a value, which is the unique identifier for the choice and what will be used in branching conditions in .
This will only work where Flex is licensed.