• State Not Answered
  • Replies 13 replies
  • Subscribers 8 subscribers
  • Views 3733 views
  • Users 0 members are here
Related Discussions
Home » Discussions » User Interface

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

siddharthg521
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
  • 0
    Appian Employee
    Currently, there is no way to programmatically update the Group Membership Cache without logging out or waiting for the idle time (20 mins) of the cache.

    I understand that you may be finding it a bit challenging without an automatic way of updating this Cache, but if you consider the real world (in Production), it is generally not an issue. Such a pattern of changing group membership in Process works well in Production, as users eventually either logout or stay idle for 20 mins for his/her group membership changes to take effect. Especially with Tempo Event security, it will work just fine, unless you absolutely need the Events to show up real-time in the user's Tempo interface -- but think of the Production environment while designing your system, and not of the Development environment.

    Please let me how what works the best for you, and we may be able to suggest something else. Hope this helps!
Reply
  • 0
    Appian Employee
    Currently, there is no way to programmatically update the Group Membership Cache without logging out or waiting for the idle time (20 mins) of the cache.

    I understand that you may be finding it a bit challenging without an automatic way of updating this Cache, but if you consider the real world (in Production), it is generally not an issue. Such a pattern of changing group membership in Process works well in Production, as users eventually either logout or stay idle for 20 mins for his/her group membership changes to take effect. Especially with Tempo Event security, it will work just fine, unless you absolutely need the Events to show up real-time in the user's Tempo interface -- but think of the Production environment while designing your system, and not of the Development environment.

    Please let me how what works the best for you, and we may be able to suggest something else. Hope this helps!
Children
No Data

© 2024 Appian. All rights reserved.