Page 1 of 1

A few suggestions

PostPosted: Wed Apr 08, 2009 9:40 pm
by smithle
Allow saving of some number dashboards; I'm having to create them each time I go back to the dashboard view

Don’t create tasks/events upon click, but upon save. If I decide not to create the event/task, I'm having to remember to go in and delete or disregard the abandoned item that it created.

Work with outlook categories (particularly for calendar items and tasks). Outlook folders aren't intuitive for events/tasks. I had to build a folder heiarchy just to get quick access to the cagetories I needed.

Re: A few suggestions

PostPosted: Wed Apr 08, 2009 11:15 pm
by Scott - CC Support
Allow saving of some number dashboards; I'm having to create them each time I go back to the dashboard view


This is oft-requested and high on our list of future features.

Don’t create tasks/events upon click, but upon save. If I decide not to create the event/task, I'm having to remember to go in and delete or disregard the abandoned item that it created.


Can you be more specific? After pressing the task or schedule button, the item is not created until it is saved.

Work with outlook categories (particularly for calendar items and tasks). Outlook folders aren't intuitive for events/tasks. I had to build a folder heiarchy just to get quick access to the cagetories I needed.


ClearContext can duplicate Topics into categories so that you can use them in Task views (ClearContext > Options > Preferences > Topic Options). You can also add Topic name to Task and Appointment views so that you can sort these items by Topic. See our user guide for more detail.

Thanks for the feedback.

Re: A few suggestions

PostPosted: Thu Apr 09, 2009 10:02 am
by Scott - CC Support
Sorry for my confusion last night:

Don’t create tasks/events upon click, but upon save. If I decide not to create the event/task, I'm having to remember to go in and delete or disregard the abandoned item that it created.


I see the behavior you are talking about, though to do date no one has reported it. We have added it to the issues to list to take a look at for a future release. Thanks for the feedback.