In the interest of improving automation capabilities and streamlining Forms process creation, I would like to request that dynamic fields be triggered/populate automatically when their parent fields are configured within a Forms "Save to Repository" Service Task.

For example: I have a template setup with 1 required field that is the parent field for all other dynamic fields in the template (it's an Employee ID field, so all other metadata for a given employee should uniquely correspond to their ID in the database). This template is applied to entries created by a Forms process.

Optimally, within the "Save to Repository" Service Task in Forms, I would be able to click the "Configure fields" button, populate the Employee ID field with the {/dataset/Employee_ID} token generated earlier in the process, and this would automatically trigger the population of the other metadata fields on the template after the form was saved to the repository, thereby saving me the time of having to manually add the appropriate token to the other metadata fields, and eliminating the opportunity for me to accidentally add a wrong token to a field.