You are viewing limited content. For full access, please sign in.

Question

Question

Self-hosted Workflow - Get user first and last name from LFDS

asked on April 17

Hello,

I have a vehicle inspection form that drivers fill out every day. These drivers login to Forms via LFDS, and there is a field that captures their display name by default:

This value gets saved to a field in the repository when the form is submitted. This value matches the Display Name property in LFDS for a given user - it's their first and last name.

I also have a workflow that creates an HTML table and lists each driver who submitted an inspection the day before. This works fine as I don't need to query LFDS for anything here; it's just a Search Repository activity based on template name and yesterday's date, and I can get the driver name from the document.

 

What I'd also like to do is include a list of drivers who did not submit an inspection yesterday. I thought I'd be able to do this by first building a list of all drivers by using the Find Group activity in Workflow, as every driver is in the same LFDS group. Then, when iterating through the search results, I could use a token function to remove that driver name value from the list of full drivers, and by the end, I'd have a list of drivers who did not submit an inspection.

The problem seems to be that Workflow treats the Display Name and Account Name the same - it's the domain\username value instead of the Display Name from LFDS. 


I see some options about "additional properties" and I see the first name and last name there, but I can't figure out how to make these available to me as a token. Any advice? Workflow version is 11.0.2209.835

0 0

Replies

replied on April 17

Well, I might have figured something out by getting the list of users from LFDS, then querying AD.


Does anyone know if it takes a bit for LFDS to sync with Workflow? I've removed some users from this group in LFDS, but they still show up in the list retrieved from LFDS.

0 0
replied on April 17

Workflow does not cache any data from LFDS. If you have Active Directory group sync set up in LFDS and you removed the users from the group in AD, then that may take until the next sync to be reflected in LFDS. 

0 0
replied on April 17

I believe I found out that the group that Workflow was finding was a repository group with the same name, not the LFDS group. I made sure the domain accounts in each group matched up, and now I'm getting the result set I would expect. So the issue was on my end the whole time :)

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.