Select from dropdown list connected to data in the platform
V
Vague Gerbil
I want to create a field in a questionnaire where I want the user to be able to select responsible user from a drop down list catching the data of existing users.
M
Main Newt
Product requirement: Dynamic drop-down fields and data links in questionnaires
I've already upgraded this requirement as it addresses an important use case for structured data collection via questionnaires.
Objective of the request
------------
It should be possible to link questionnaires more closely with existing platform data. There is currently no option to connect fields directly to existing entities. The goal is to provide drop-down fields that get their values from existing platform data.
Using Existing Entities
---------------------
As a first step, it would be sufficient if entities from Formalize were available directly as selection options in drop-down fields. This would allow users to select existing objects in the questionnaire instead of manually entering values.
Since we manage several hundred processes in the system, these are automatically imported into Formalize via interfaces. It is therefore important that the drop-down fields can directly access this existing data and do not rely on manually maintained lists.
Dependent drop-down fields (cascading dropdowns)
------------------------------
In addition, it should be possible to configure dependent drop-down fields. The selection in one field influences the options available in the next field.
Example: If a contract is selected, the next field should only display systems that are assigned to that contract.
This reduces misallocations and makes it easier to select large amounts of data.
·
·
·
Reply
M
Main Newt
Use case: upstream and downstream processes
-------------------------------
One specific use case concerns the modelling of process dependencies.
In a form, you should:
select a process first
two more drop-down fields should then be available:
Upstream processes
Downstream processes
The selection options in these fields should be based on existing processes in Formalize.
Since we map several hundred processes in the system, these are imported into Formalize via interfaces. It is therefore particularly important that these drop-down fields can directly access the existing process data.
Automatic creation of relationships
---------------
In addition, it should be possible to automatically create relationships between entities based on form responses.
example:
A process is selected in the form
In addition, upstream or downstream processes are defined
After submitting the form, a corresponding relationship between the processes is automatically created
As a result, process dependencies could be recorded in a structured manner without having to manually update these relationships.
There is another use case in BCM. Here, we want to use forms to capture relationships between processes and supporting systems.
The form should:
a process is selected
a system is then selected
additional information about the relationship between process and system is collected
After submitting the form, a corresponding relationship between process and system should be created automatically.
Reference for possible implementation
-----------------------
The Assets Object Custom Fields from Jira Assets can serve as a reference for a possible implementation. These enable object-based drop-down fields and dependent selection logics and are a good example of this type of functionality.
converted_text