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

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...

OriginalPostID-60646

OriginalPostID-60646

  Discussion posts and replies are publicly visible

Parents
  • Do you care about the group membership only while the process is active? In other words, after your process terminates, don't you want the Tempo post viewership to remain the same forever?

    If you remove users from a group (which you used as a viewer group when posting to Tempo) or delete the group itself, the user will no long have access to the Tempo post, since your Tempo post will still be targeting this group. I don't think you want so, do you? I am not quite sure how your approach is working for you.

    I don't think removing users from a group or deleting a group will solve your problem. In-fact, if you are going ahead with the dynamic group approach, you will have to keep all the groups around forever. Increasing the number of groups affects the login time for a user a little, but not necessarily a show stopper.

    But, I would highly recommend reconsidering your overall design while keeping Appian Tempo best practices (forum.appian.com/.../Tempo_Best_Practices) in mind.

    And, yes, the sub-group membership is inherited by the parent group in Appian.
Reply
  • Do you care about the group membership only while the process is active? In other words, after your process terminates, don't you want the Tempo post viewership to remain the same forever?

    If you remove users from a group (which you used as a viewer group when posting to Tempo) or delete the group itself, the user will no long have access to the Tempo post, since your Tempo post will still be targeting this group. I don't think you want so, do you? I am not quite sure how your approach is working for you.

    I don't think removing users from a group or deleting a group will solve your problem. In-fact, if you are going ahead with the dynamic group approach, you will have to keep all the groups around forever. Increasing the number of groups affects the login time for a user a little, but not necessarily a show stopper.

    But, I would highly recommend reconsidering your overall design while keeping Appian Tempo best practices (forum.appian.com/.../Tempo_Best_Practices) in mind.

    And, yes, the sub-group membership is inherited by the parent group in Appian.
Children
No Data