Advanced Request Offering Control Question Mapping
Now the image above shows an example of a question whereby a we only want the highlighted question to trigger the display of a further question. We do not care about the answer of this question in the context of the request but are forced to map it in a visible display area on the request form due to the limited options available in the multiple mappings.
From a bit of testing I've found that mapping these unwanted fields to the user input box doesn't (visibly) cause any issues and more importantly doesn't affect the user input area on either the portal or console views. If this is a supported location for mapping these questions then it solves the niggle I have described above, if it isn't supported then another option is needed.
Now onto my next point. We provide some additional text within the description field where we are storing the collected information to make it more user friendly.
From what you can see above, I've provided some descriptive text to display what the question was in front of the mapped prompt. Ideally that descriptive text (for example the internal message or expiry date) should only be displayed if the prompts are not empty (they only appear if prompted to) to keep the description clean and relevant for the options the user has selected. Something like this would ensure that the returned descriptions are clean and user friendly.
Whilst there are ways around the above by using Orchestrator/SMA/Powershell to just update the description with the values which are present, it would be good to use/extend the ARO functionality to do this. Happy for any input or suggestions on the above.