Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
8 subscribers
Views
1340 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
We are on 7.11 cloud. We have a process set up that will create a New
aksharc
over 8 years ago
We are on 7.11 cloud.
We have a process set up that will create a News Feed. I have used Post Event to Feed smart service to create a news feed. In that service, the value of Viewer attribute is set dynamically based on what user had selected in the form. Now, once the feed is created, it is locked. I mean, no other participants can be added after the feed is created.
Is there a way, that user can add more participants after the feed is created? Note that the viewer will always have a value.
Thank you in advance.
Akshar.
OriginalPostID-191406
OriginalPostID-191406
Discussion posts and replies are publicly visible
Parents
0
sikhivahans
over 8 years ago
@aksharc Hi, as said by other practitioner that the post won't be locked isn't true as per my knowledge. It will be definitely locked, because once when you automatically publish an event to feed by targeting it to a particular audience, you can't update the viewers, that is, whatever has been provided to it, whether User(s) or Group(s) objects set is final.
And re the question 'Is there a way, that user can add more participants after the feed is created?', here goes 2 options (though not elegant) as far as my knowledge is considered:
1. As said by @brettf. The advantage of this approach is that, the maintenance is quiet simple. But the downside of this approach is that, once if the users are removed from the group, they can't access the feed entry at all. Let's say a user has participated in 50% of the process and has been removed. Also let's assume that the user has made some valuable comments and attachments. When the user is removed from the group he or she won't be able to access the information or see the work which he/she did while ago.
2. An other option is to create a new post as and when the target audience change, and continue posting messages to the latest event always. Still you can stick with the creation of dynamic group here (or you can eliminate group creation and just make use of an User or Group of multiple type variable, but I generally prefer to Group, as it's management seems quiet simple to me), and the group management of adding or removing the viewers is the same. The advantage of this approach is that each and every user who has been a part of the process some time ago, can review the work(that is go through their/ team's comments, access the files which they have shared or the team has shared etc) IF needed by accessing the feed entries posted in the past. It means that the user won't lose access completely once when he or she is removed from the accessing the post.The downside of this approach is that, creation of a new post is slightly cumbersome when compared to the above approach. Just to make a note, as far as I remember, news feed requirements in the Lead Designer Credentials (some time ago) are specified on these lines.
I am not sure if any other approach exists, but probably opting for an approach completely depends on the use case and the client requirements.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
sikhivahans
over 8 years ago
@aksharc Hi, as said by other practitioner that the post won't be locked isn't true as per my knowledge. It will be definitely locked, because once when you automatically publish an event to feed by targeting it to a particular audience, you can't update the viewers, that is, whatever has been provided to it, whether User(s) or Group(s) objects set is final.
And re the question 'Is there a way, that user can add more participants after the feed is created?', here goes 2 options (though not elegant) as far as my knowledge is considered:
1. As said by @brettf. The advantage of this approach is that, the maintenance is quiet simple. But the downside of this approach is that, once if the users are removed from the group, they can't access the feed entry at all. Let's say a user has participated in 50% of the process and has been removed. Also let's assume that the user has made some valuable comments and attachments. When the user is removed from the group he or she won't be able to access the information or see the work which he/she did while ago.
2. An other option is to create a new post as and when the target audience change, and continue posting messages to the latest event always. Still you can stick with the creation of dynamic group here (or you can eliminate group creation and just make use of an User or Group of multiple type variable, but I generally prefer to Group, as it's management seems quiet simple to me), and the group management of adding or removing the viewers is the same. The advantage of this approach is that each and every user who has been a part of the process some time ago, can review the work(that is go through their/ team's comments, access the files which they have shared or the team has shared etc) IF needed by accessing the feed entries posted in the past. It means that the user won't lose access completely once when he or she is removed from the accessing the post.The downside of this approach is that, creation of a new post is slightly cumbersome when compared to the above approach. Just to make a note, as far as I remember, news feed requirements in the Lead Designer Credentials (some time ago) are specified on these lines.
I am not sure if any other approach exists, but probably opting for an approach completely depends on the use case and the client requirements.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data