Workflow fails on an Avoka component which searches the LiveCycle Database for the canonical name. The workflow fails for any new groups created in LiveCycle ES 8.2.1.
The canonical name field in the EDCPRINCIPALENTITY table has been changed to record a unique alphanumeric ID instead of the common name for new users/groups.
As a workaround, create a group via API (UM’s client SDK), where you can specify your own canonical name using this value. Alternatively, have the component search for "common name", rather than canonical name.