Currently, we have a convention of storing the correlating id along with the regex pattern rule id in the Detection.RedactionToken property. This change puts the correlating id itself into its own property. This allows that data to be generated but for users to prefer an alternate redaction token in the masking scenario.
This change also fixes non-determinism in tests, which I'd previously attempted to change but simply used the wrong mechanism to ensure a non-zero/default value for initial property values.
Detection.CrossCompanyCorrelatingIdproperty.Currently, we have a convention of storing the correlating id along with the regex pattern rule id in the
Detection.RedactionTokenproperty. This change puts the correlating id itself into its own property. This allows that data to be generated but for users to prefer an alternate redaction token in the masking scenario.This change also fixes non-determinism in tests, which I'd previously attempted to change but simply used the wrong mechanism to ensure a non-zero/default value for initial property values.