Currently, object data such as custom fields on projects can be mapped through to the document template. What I believe would be a fairly broadly applicable use case is to have the ability to map those same attributes to the questions on the forms.
Example Scenario:
A manufacturing process requires custom calibration of a particular machine per job. This calibration information is captured in a custom field when the job is first created. As part of the QA process, a technician is required to fill out the form and sign it to acknowledge they have completed the necessary calibration steps.
To make things simpler for them, instead of having a question like
'Have you calibrated X setting to value found in custom field 1?',
it would be smoother to have a question like
'Have you calibrated X setting to [project custom field 2]'
where the value in brackets is replaced by the data in the custom field for that job, such as '21mm'.
Currently, object data such as custom fields on projects can be mapped through to the document template. What I believe would be a fairly broadly applicable use case is to have the ability to map those same attributes to the questions on the forms.
Example Scenario:
A manufacturing process requires custom calibration of a particular machine per job. This calibration information is captured in a custom field when the job is first created. As part of the QA process, a technician is required to fill out the form and sign it to acknowledge they have completed the necessary calibration steps.
To make things simpler for them, instead of having a question like
'Have you calibrated X setting to value found in custom field 1?',
it would be smoother to have a question like
'Have you calibrated X setting to [project custom field 2]'
where the value in brackets is replaced by the data in the custom field for that job, such as '21mm'.
0 Votes
0 Comments
Login or Sign up to post a comment