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

Discussion

Discussion

Unable to Use LFDS Users for Invoke Business Process Activity

Workflow
Updated December 28, 2022
posted on December 22, 2022

I currently use Find User to populate the Process Initiator for the Invoke Business Process Step. The Laserfiche environment has been moved to it's own network and using SAML users in LFDS . AD directory is no longer available. I found how to do this with a script, but the Invoke Business Process step will only look at Find User or Find Manager tokens for the information. Is Laserfiche planning to resolve this issue?

 

1 0
replied on December 27, 2022

Hi Kathy-

I believe this has to do with the way things are licensed in LFDS. If all of your applications and users are licensed at the (root) level, they should be visible. Otherwise, it's pretty goofy and unintuitive because applications licensed at (root) cannot see users licensed at lower levels.

You'll basically need one organization below (root) where you license all your applications, and then users can be in that org or anything underneath it and still be seen. Along the lines of:

  • (root) -> don't license anything here
    • COMPANY -> license your applications here
      • DEPARTMENT 1 -> license your users here or in sub-organizations
      • DEPARTMENT 2
        • Department 2-a
replied on December 23, 2022 • Show version history

In the current (WF 11) Find User activity, it gives you the ability to select where you are searching so that you can search AD or Laserfiche.

1 0
View 2 previous replies
replied on December 27, 2022 • Show version history

Yes, but I can only see repo users, not LFDS users. Even when I explicitly add an LFDS user, the search does not find them. I need to be able to find LFDS users.

1 0
replied on December 28, 2022

It seems that I can find users in the Find User activity if I search on the account name. That will retrieve my users successfully from lfds. BUT......only if those users are NOT in an organization. So only if the users in the ROOT. 

Any ideas on how to get users from a specific organization?

0 0
replied on December 28, 2022

Hi Chris (and Kathy)-

I almost chimed in on this point yesterday but didn't have a lot of time to test it and didn't want to lead you astray. But here's what I think is going on:

I believe this has to do with the way things are licensed in LFDS. If all of your applications and users are licensed at the (root) level, they should be visible. Otherwise, it's pretty goofy and unintuitive because applications licensed at (root) cannot see users licensed at lower levels.

You'll basically need one organization below (root) where you license all your applications, and then users can be in that org or anything underneath it and still be seen. Along the lines of:

  • (root) -> don't license anything here
    • COMPANY -> license your applications here
      • DEPARTMENT 1 -> license your users here or in sub-organizations
      • DEPARTMENT 2
        • Department 2-a
1 0
replied on December 28, 2022

Thanks for the response!

Currently we have all the apps in the root and all the users in a separate organization. We have a few customers who use our licensing so keeping everything separated is essential. We are toying with the idea of moving all the users to the root and control the organizations by putting the users in groups and keeping the groups per organization. We plan on testing it out tomorrow.

 

So, I can't test your example until we get out dev migrated over to our new environment. That may be a few weeks, but look forward to trying out placing our LF server in the same org as the users and see what happens. 

 

Thanks so much!  

1 0
replied on December 28, 2022

You're welcome. In the case of keeping things super separate, you'll probably want to have separate orgs at the root level where you can license applications and users together in one org that is separate from the others. I think...luckily, I haven't had to get that complicated yet.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...