We are currently using HRSD with Employee Forms to capture end-user (employee) responses (e.g., Yes/No) and map those responses to specific fields on the HR Case in order to control subsequent activity sets. (Some forms leverage the OOTB Employee Forms provided by the Experience Pack.)
However, when using the Condition Builder on Employee Forms (e.g., Opened for is (dynamic) Me, State is one of …), if multiple cases for the same requester meet the conditions simultaneously, the system cannot uniquely identify the target record. As a result, the form cannot be displayed or saved, and the mapped values are not written back to the HR Case. My understanding is that Employee Forms assume a single record, so mapping fails when multiple matches exist.
I would like guidance on the following:
- Best practices for implementing a solution that ensures uniqueness when collecting employee responses and updating cases without using Employee Forms.
- Recommended design patterns for continuing to use Employee Forms while avoiding or resolving multiple matches—for example:
- Explicitly passing a unique key
- Strengthening condition expressions
- Introducing a selection UI when necessary
Could you share practical examples, recommended approaches, and key considerations for these scenarios?
