What is the challenge? |
Ability to capture structured data of our choosing on steps. For example, frameworks represent parts of or a whole system. Systems have inputs and outputs. It would be great to be able to capture inputs and outputs for a step in a structured way (especially if reporting on frameworks is enabled). |
What is the impact? |
Enhances the usefulness and real world application of steps. |
Describe your idea |
Add custom fields for steps, including a record relationship field for steps and frameworks so they can be referenced on each other. |
I would like to be able to capture a "Person responsible" field as a custom field on a Framework step. Along with some other information like whether a step is optional or mandatory and a custom field as to any excpetion cases where the step would not apply.
Right now I have to capture this as text within the description field, but they will be fields common to every step and therefore I would like to make them purpose built fields.