Forum Discussion
Solved
Restricting mappings one to one
When mapping an item from the "Validate" step in the workflow, it is possible to save the mapping to an "(unassigned)" item. Is it possible to restrict the storage of the mapping so that it cannot b...
Hi Sara,
Unassigned is a valid and out-of-the-box option that is always available. It cannot be removed from the list.
This is one of these cases where it sounds like it could be addressed via user training especially considering that the worst case scenario is that the user will see a new error after the incorrect mapping and will have to map it correctly in order to successfully validate i.e.: no harm to the system/data.
From a technical point of view, you could, however, potentially track the save changes action and raise an error / exception using the WcfEventHandler preventing the unassigned option from being selected by, for example, a non-admin user.
Hi,
The issue here is that an user has saved a mapping of one account to the "unassigned" element, and the error is because there is no account with that name in the model.
What I wanted to know is if there is a way to prevent users from saving a mapping to an "unassigned" element or saving the mapping without a target member.
I hope I have explained myself.
Thank you.
