As usual, @Oshyan you’re feedback is thoughtful, actionable and delivered graciously, thanks.
And thanks also to @B_Sp @HereBeBeasties et al. for providing a view ‘from the trenches’, here and elsewhere.
2 Likes
The concept of watchers could be implemented quite easily, if the comments field also appeared in the changed field drop down.
If, we could trigger an automation when a comment is added.
e.g.
entity comment are updated
trigger notification to users in field (e.g. watcher)
New comments can trigger a rule, you just need to use the ‘Entity linked to…’ option and choose the Comments field.
(they behave like a one-to-many relation field in that sense)
3 Likes
OK this is good - many thanks, for context:
The comment looks like:
The automation setup looks like:
The message template looks like:
{! Comments:Document Secret !}
<%
const fibery = context.getService('fibery');
const lastComment = Entity.Comments[Entity.Comments.length-1];
%><%= await fibery.getDocumentContent(lastComment['Document Secret'], 'md') %>
2 Likes
Following up on this, this solution has worked well and is universally liked by the team.
One small thing I’ve noticed, is that if the comment contains an @, the the comment contains the users (I assume) guid/uuid?
e.g. @laurence Are you able to make the server virtual directory…
1 Like
Quick update: now that it is possible to trigger automations based on changes to rich text fields, it is possible to create a fairly complete ‘watcher’ functionality.
You can create a to-many relation field linking a database to the User database, and then define an automation that will trigger on any field change, and send a notification to the Users who have been added to this field.
Couple this with the ability to notify when Comments/References are added, and I think it becomes pretty usable.
Better than nothing, but still kind of a lot of work to setup and maintain across a large Workspace, given the lack of centralized script management.
If we had a Rules trigger for “When any field is updated” that would go a long way toward making this approach less of a maintenance headache – as would having centralized script management!
3 Likes
I agree. It’s good of you @Chr1sG to continue to explain in detail how to get close to this functionality, but for simplicity sake, and for those who don’t have time to dig into automations, I’d simply like to be able to “watch” any entity I choose, by simply being offered an option to “watch” it, just like I can “favorite” them. This is a common feature in a ton of other Fibery competitors. I’m confident you guys will get there, and I hope that’s when you do your mass reset on Notifications that there’s been a lot of discussion around lately…
1 Like
For creating a rule, I would love to have a filter option for “Modified by”.
Use case
As head of a team, I’m responsible for project controlling. I want to be notified if a field (etc.) is updated on an entity where I’m not the assignee. But only if someone else has updated it. If I updated it - I know already 
Solution
Filter: Where → Modified by → is not → me.
This would be a great help for anyone trying to stay on top of everything their team is doing (on some stuff…very selectively…otherwise 
)
1 Like
Related?
1 Like
If you just want to be able to see what has been changed in a given database without the notifications, the Audit Log may be the route, assuming you are the admin. They have a filter on that that will give you that info easily.
Alternatively, you could probably setup a basic automation rule to notify you when an entity is updated, by selecting the users who it could be assigned to (aside from yourself) – also probably good to add “is empty” as an option unless things are autoassigned. [Note: The does not contain filter might also be the better option, as you should be notified if someone changes something on things multiple people including yourself are assigned to]
Personally, I’m considering looking at trying out the feed view as a potential way to monitor daily activity within fibery.
2 Likes
Hi Joe, thanks for the suggestions, unfortunately they are not applicable for our use case. It’s more in line with the related topic @ChrisG posted (“Watcher of an entity”).
@anna is there something you need above and beyond what is discussed in the topic I linked to?
If not, are you happy that we merge them?
You can merge them, thanks!
Hi
I created a “Notify me of new Comments” Automation for everyone who is “watching” an entity. (i add users as watchers automatically when people leave a comment in a relation to “Users” field)
Now all users get notified of a new comment on an entity they are watching. great. BUT assignees get this notification twice (once with the fibery internal notification, once from my setup notification [including the comment text btw])
as i cannot filter out “if author is assignee” in the comments, I odnt see a way to block this …
as i dont want to setup notifications for all other databases - and still want to get notifications about stuff (setting of notifications is “on”) - how can i filter these double notifications out?
as I dont want to “assign” a task to everyone who comments on it … i dont really know how to solve this otherwise…
also the internal notification makes the new comment glow in yellow … while my own notification isnt …
AND it would be great if both are actually LINKING to the comment and scroll there automatically
1 Like
Hi!
We’re currently working on a new Watcher functionality as an active action, so hopefully that would solve the issue you have now
5 Likes
Implementation started this week. Thank you for the patience.
5 Likes
Not sure if this if planned for, but would be useful to be able to filter by “Where watchers includes (me|user)”. Also be able to access/modify watchers in automations.
1 Like
Watch action for automations is in scope, Filter is not yet (but we do have such feature).
2 Likes