Hi, Everyone I am trying to incorporate security on feeds that are b

siddharthg521 over 11 years ago

Hi, Everyone

I am trying to incorporate security on feeds that are been posted to tempo.My objective is that only those users should be able to see the feeds on tempo that are been stored in process variable (pv!users) .If that process variable is updated and any user is removed or added than the users in that updated process variable must only see the feeds related to that process.(Removed users should no longer see the feeds and newly added users should see the respective feeds.)

When I am passing togroup(pv!users) to the viewers group of "Post feed to Tempo" Smart service, irrespective of who are the users present in the process variable, all users are able to see the feeds on tempo.

I have also tried to use "Tempo Audience Group" that is by default present in People Tab, and have passed in Viewers group of Smart service, but that will create a group for each instance of my process at root directory of Groups.

Hence, along with the abov...

Discussion posts and replies are publicly visible

Parents

0 Abhishek Shadangi
Appian Employee
over 11 years ago

Hi Siddharth, togroup(pv!users) does not create a dynamic group -- togroup() is meant to convert groupID to an Appian Group. More so, you cannot control security of a Tempo Event by using just a process variable (pv!users).

Having said so, you seem to be on the right track based on your last approach. You can certainly create a Custom Group per workflow (instance of the main process). You can then user Add and Remove Group Members Smart Services to control the group membership.

Note the caveat:
1) User must logout from the Tempo Web UI for the Group Membership changes to take into effect, or system will automatically update his/her Group Membership if the user is idle for 20 minutes (system default for Group Membership cache update).
2) If the users are using mobile interface #1 comment still applies.

Please let me know if you have questions.

Questions: Using this approach, how many groups you think you will end up creating in the Production in a year? In other words, how many instances of the main process are you expecting per year?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Abhishek Shadangi
Appian Employee
over 11 years ago

Hi Siddharth, togroup(pv!users) does not create a dynamic group -- togroup() is meant to convert groupID to an Appian Group. More so, you cannot control security of a Tempo Event by using just a process variable (pv!users).

Having said so, you seem to be on the right track based on your last approach. You can certainly create a Custom Group per workflow (instance of the main process). You can then user Add and Remove Group Members Smart Services to control the group membership.

Note the caveat:
1) User must logout from the Tempo Web UI for the Group Membership changes to take into effect, or system will automatically update his/her Group Membership if the user is idle for 20 minutes (system default for Group Membership cache update).
2) If the users are using mobile interface #1 comment still applies.

Please let me know if you have questions.

Questions: Using this approach, how many groups you think you will end up creating in the Production in a year? In other words, how many instances of the main process are you expecting per year?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data