Notification when scheduling for another user

[Cyane]

We are just starting to get into the functionality of using the "Schedule For" option to create tasks for other users. However, there doesn't seem to be any indication that Steve has just scheduled an item for Matt. The item simply appears on Matt's calendar, and it's on Matt to notice that something new has been added.

As far as I can tell there doesn't seem to be any way to notify the user that something new has been scheduled for them, they literally just have to happen to notice that a new task has appeared on their task list or on their calendar. We worry that a lot of time sensitive things will be missed/not noticed until it's too late. (For example, Steve has scheduled an item for Matt to be done by Wednesday. Matt does not see the item on his tast list or calendar until Wednesday, and does not have enough time to complete the item by Steve's deadline).

What work-arounds have others used for this type of situation when scheduling for another user?

[dshaw111]

Hi Cyane,

It should show a message at the top of the Scheduling Window that reads " You are scheduling on behalf of xyz".

If you set an alarm for the new user before you finish re-scheduling then this should let them know of this Activity with the Alarms.

HTH

[Cyane]

Hi David,

Thanks for the response. We were hoping to avoid alarms because if one comes up when you're not at your computer, it pops up an alarm box every five minutes so when you get back to your computer an hour later, you have 20 boxes to click through in Sage to clear out.

[dshaw111]

In Act! you just get one alarms box with all the alarms in that one box.

Try it please.

[Cyane]

All of our users used the alarms for our regular appointments and calls for some time, but Sage will pop up a new alarm box every fix minutes if you do not take action on the alarm box. In the case of being away from your desk, you end up with many boxes.

Other users detailed the same issue here: http://community.act.com/t5/Act-Premium/Act-2013-Alarms-Box/td-p/219238/highlight/true

We solved it simply by turning off all alarms.