as it is currently not supported to set the account name for service accounts to read only, we need to find a workaround to enforce our naming convention.
Therefore we thought about two options:
1. Regex to check account name => not possible as this option validates all accountnames within a security system and therefore also the personal ones, which have a different naming convention
2. Via workflow: We try to realize it via workflow, but therefore we would need to add a if-else clause to check, if the account name set within the request follows a defined convention. Is this possible to query that attribute account name within the workflow to perform a validation?
was also my assumption, but isn't it the case, that during a pending request, the account data is still not available in the accounts table.
The check needs to happen directly after submitting the request and where the workflow kicks in, which would means neither the accounts table attributes nor the tasks table attributes are queryable. We would need to check the accountname defined during the request. Is there also some table for this?