The best solution is to not rely on free text.... so instead of helping with that (hint: evaluation paths) I will suggest a different approach:
Tell the functional consultants/HR people that they must define a customer-specific relation for the HR Administrator, and use this relationship to define who is HR Administrator, as you refuse to rely on something as unreliable as a text field to find your workflow's agents. I would suggest a relationship between organisation unit and position, but that's up to you.
Use transaction OOAW to define a new evaluation path which takes you from an organisation unit to the position (or person, or whatever) representing the HR administrator, via your customer-specific relationship.
Another alternative is to use a job (object type C) and let the HR people ensure that the position of the HR Admin is linked to this job. Then you can either specify the job as possible agent of the task and just send the work item to the whole organisation unit, or you can create your own rule function which will find all positions and remove those that are not linked with the correct job.
There are probably other options as well. Anything but relying on a text field...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.