1 of 1 people found this helpful
Nope. But two suggestions. The fairly easy one would be to hook up the RSS generator to a query which displayed the messages you wanted to send out. Then people could subscribe to this feed and get notifications that way.
A more complex method is something I did for a client and you'd have to be quite keen to do this :-) I replaced notifications in a process with some bespoke work that used event manager and some hefty calculation work to throw the information I wanted to email and the list of people out to an external table. This table was then processed externally and sent the emails based on the data in the event manager queue.
I have kinda gone down the route of the second suggestion, by using an external system to monitor and email when status is at a certain point.
Will be great when it is part of LDSD itself.
Dave, I'm just about to revisit this in 7.5 sp1 for this first time since 7.2.4, so still no reminders\notifications in the article process?
Our requirement was quite simple, to enable people who'd had an article rejected to get a notification so they could amend it accordingly, as with most manual processes, people forget and it leads to inconsistencies.
That's a no I'm afraid and it doesn't appear to be different in the 7.6 beta.
Is there an ER for this? I would vote for it
Karen, the ER states its on the roadmap but when is this likely to happen? As a number of people have noted, this is a major restriction in the knowledge management process, LANDesk have banged the KM drum at various user groups but they don't seem to be investing in this area of the product.
Yes the ER will definitely be on Product Management's radar due to the number of votes. I've just voted on it too as I agree it would be a useful addition. I am not able to give out details about the roadmap for future releases as yet, I would recommend that you please talk to your Account Manager to see if they can give you some early information on this.
I have seen databases where customers have used some clever process design in order to workaround this by using another unused reminder object from an object which inherits from process. For example, by using the call reminder object. I have also seen that other customers use scheduled queries or create knowledge automatically via incidents/problems so use the reminders within these processes. If you haven't already done so, these are options that you may want to consider in the meantime.
EDIT 1st May 2015: I just wanted to direct any future visitors to have a look at this workaround:How to add notifications to your article process.