Summary
In Archer Release Version 6.12 P4, Archer fixed a data feed user mapping issue. This changed the behavior of mapping all-numeric UserNames. Prior to v6.12 P4, a data feed processing an all-numeric UserName would try to “match” against the UserID first, and if unsuccessful would then match against UserName.
Beginning with v6.12 P4, a data feed will match against UserName first, regardless of whether it is all-numeric or alpha-numeric. If it is all-numeric, and doesn’t find a match for the UserName, it will fall back to the UserID and attempt to match there.
Customers who have taken actions to make the data feed pull the UserID instead of the UserName (to ensure accurate matching), will need to undo those customizations. (For example, a customization of the XSLT to pull the UserID rather than the UserName would need to revert to the UserName.)
We apologize for inconvenience caused by not delivering this update at the time of the Version 6.12 Patch 4 release.
