Cool Solutions

BrainStorm Cool Tip: Accept Proxy Appointments from Your Home View



April 3, 2007 9:14 am





Welcome to BrainStorm Cool Tips. New tips will be posted regularly to help you more effectively use GroupWise. If you have any suggestions for tips, please feel free to let us know by emailing


  1. The user for whom you want to accept appointments has given you proxy access rights.
  2. The multi-user view of your calendar is set up to show the proxy’s calendar.

Create the Home View Panel:

  1. Click the panel menu arrow at the top right of any of your existing Home View Panels.
  2. Select Add Panel.
  3. Click New Panel.
  4. Name the new panel according to the proxy?s name.
  5. Click Change Folder.
  6. Select your GroupWise Calendar.
  7. Click OK.
  8. Click More Display Settings.
  9. In the View by menu, select Calendar.
  10. In the Calendar Views menu, select Multi-User.
  11. Choose the calendar items you wish to display.
  12. Choose the number of days you wish to view at one time.
  13. Click OK.
  14. Click OK again to exit the Create Panel dialog.
  15. Click Add to add the panel to your Home View.

Accept or Decline Appointments:

  1. Right-click the unaccepted appointment. Unaccepted appointments will appear in italics.
  2. Select Accept or Decline.
  3. The appointment will also show that it is accepted or declined on the person’s calendar for whom you have proxy rights.

To be able to accept or decline appointments as they come in, subscribe to the proxy’s notifications (see this previous BrainStorm Cool Tip: ) and choose accept or decline on the notification.

(Click the play button below to see a flash demonstration of this tip.)

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.