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
7 subscribers
Views
1513 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Question for the group. We are looking to create what we call a "watchers&
mikec
over 10 years ago
Question for the group. We are looking to create what we call a "watchers" process. Example: I have a process that allows a user to generate a work request. This request can be accessed, edited, add notes to it, change status, attach documents, etc. It is basically a work ticket. On many occasions the requestor wants other users to be able to "watch" the progress of this ticket. For example, if a new note is added to the request then have an email generated to everyone that is on the "watchers list" that a new note has been added to work request #34. These watchers can be added at any time to a request by anyone that has privileges. So the criteria we are looking for is as follows:
- All watchers are in the Appian system - so we can use the user field to find and select users
- Anytime a "work request is opened" a user should be able to add a user to the watchers list
- A watchers list is specific to the work request so there ...
OriginalPostID-92692
OriginalPostID-92692
Discussion posts and replies are publicly visible
Parents
0
jorgea272
over 10 years ago
I've implemented something like this before and you're on the right approach. My suggestion would be to ensure that "Add Watcher" is a quick task and that no tasks get assigned from executing this action. If a user wants to "Add Another Watcher" just tell them to execute the quick task again, because all it does is add a user a group. Also I wouldn't be too concerned about the number of groups, just ensure that you've uniquely named all these dynamically generated groups.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
jorgea272
over 10 years ago
I've implemented something like this before and you're on the right approach. My suggestion would be to ensure that "Add Watcher" is a quick task and that no tasks get assigned from executing this action. If a user wants to "Add Another Watcher" just tell them to execute the quick task again, because all it does is add a user a group. Also I wouldn't be too concerned about the number of groups, just ensure that you've uniquely named all these dynamically generated groups.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data