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

Question

Question

Is it possible to have a Gateway make decisions based on Groups or Roles?

asked on September 21

I currently have a few workflows that have gateways that use different outflows depending on the user who started the process. Rather then needed to update these flows manually each time a user needs to be changed can it be handled using Roles or Groups?

So rather then using /dataset/_initiator="User1" or /dataset/_initiator="User2" or /dataset/_initiator="User3" could I instead uses something like /dataset/_usergroup="Group1"?

0 0

Replies

replied on September 22

Gateways only check/compare values for variables and don't run more complex actions like evaluating group memberships, so to do this, the group would need to be a variable in the forms process, and you'd probably need a lookup on the form to retrieve the group.

0 0
replied on September 22

Any idea what the lookup should point too? I've dug through a good chunk of the SQL stuff and can't find a table that list users and their groups or roles without some weird ID system in place

0 0
replied on September 22

It really depends on what you mean by "group"

Are you talking about LFDS groups, repository groups, AD security groups?

Groups are a lot trickier than other common types of data; a user can be a member of multiple groups, and group membership can be inherited from other groups, so it's not really as straightforward as a lookup.

0 0
replied on September 22

Really all of them, They get rights for the forms based on the LF Group they are in, in Forms I have similar groups and roles that they are member of and I can absolutely make AD groups if they don't already exist.

0 0
replied on September 22

Realistically, each of those will require different approaches, and none of them are going to be "easy" to accomplish.

You can create SQL lookups for Active Directory using ADSI, which would be a little easier than trying to pick apart the LF databases.

However, that is still going to leave you with the challenge of inheritance.

 

Before going down that path, I would double back and consider why your process needs to route differently based on groups and see if there's another way to accomplish that goal.

Personally, I've never had a process where I actually needed to route specifically based on a group and always found a way to do it based on something that is more easily identifiable, like their selections, department, or some external data source mapping.

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

Sign in to reply to this post.