Can this issue be reproduced in a sandbox workspace? No
Does this issue represent a regression? Did it previously work? No
Description
We have an internal rule in our Seam code that prevents two access codes with the same PIN code from existing on the same device. If this error condition is triggered, we assume it's an error in our access code update and this can cause a failure to update in our other access codes as well.
This rule can be triggered if a user externally modifies a code and sets the PIN to a value that is already being used by another Seam access code.
E.g.
User has Access Code A with value 1111 and Access Code B with value 2222
User externally modifies Access Code A and sets the PIN code to 2222
Error is triggered in our access code update job which can cause updates to fail for other codes on the device
Steps to Reproduce
Create multiple access codes for a device on Seam
Externally modify an access code to have the same PIN value as another Seam access code
Access codes can stop syncing properly for the device
Expected behavior: update should succeed, but warning should be placed on the externally modified access code indicating that it is a duplicate code
Actual behavior: update fails and access codes can stop syncing properly for the device
Prerequisites
Description
We have an internal rule in our Seam code that prevents two access codes with the same PIN code from existing on the same device. If this error condition is triggered, we assume it's an error in our access code update and this can cause a failure to update in our other access codes as well.
This rule can be triggered if a user externally modifies a code and sets the PIN to a value that is already being used by another Seam access code.
E.g.
Steps to Reproduce
Expected behavior: update should succeed, but warning should be placed on the externally modified access code indicating that it is a duplicate code
Actual behavior: update fails and access codes can stop syncing properly for the device