I have a workflow to create a new coworker. There is a transaction block set to type atomic with two steps - the first stores a record into the BusinessPartner and OrganizationBusinessPartner tables and the second calls IdentityService.CreateUser to create a record into the OrigamUser table. In case that the creation of a user fails, because the password doesn’t match all requirements, these two steps (or better the first one) should be rolled back. That doesn’t happen, the records in the BusinessPartner and OrganizationBusinessPartner tables are there.
1 Like