I am trying to send email's to members of a group by using the token foreachuser_current user_email but the token is always empty when working with windows users. Is this only a feature for repository users?
Question
Question
Workflow - foreachuser_current user_e-mail is only for Repository Users?
Replies
Are these Windows users in a repository trustee provider or in an Active Directory trustee provider?
Where can I see that? They are added under Windows Accounts in the admin console. They are in a Laserfiche Group also created in the Admin Console. They are Active Directory users.
From the Workflow Designer, go to Tools\Configure Trustee Providers, then click Manage.
Most likely you're using a repository trustee provider, so Workflow is looking for that information in Laserfiche (where it's stored in the user attributes: "[Workflow]E-mail"). That has to be set manually as the Laserfiche does not look user properties up in Active Directory. You can set it either in the LF Admin Console or from the Configure Trustee Providers dialog mentioned above.
If you would like Workflow to look up that information in Active Directory, you want to set up an Active Directory trustee provider in Workflow.
Ok, I do have an AD trustee provider configured there. I use that with the Find User task, to make sure I get their AD email.
In this case though I am in a For Each User loop, cycling through each user in a Laserfiche Group. But I can't figure out where to set which trustee provider I want to use within the loop.
Edit: Realized I can find the user again within the loop, and then specify the AD trustee provider. Then use the token from find user instead of for each user. Seems like I have a ton of activities lined up just to send an email though, not sure I am doing this right.
Here is what I am trying to accomplish:
I don't want to manually enter user emails into a static TO: field within every workflow. So I create groups within the Administration Console to define user roles. Now when I need to email someone, I just tell workflow to email the user within that group. Now if someone else takes over their role, the LF Admin can simply swap out the user within the group, we don't need to go digging through workflows looking for every static entry of their email.