Skip to main content
    Country/region select      Terms of use
     Home      Products      Services & solutions      Support & downloads      My account     

developerWorks  >  Lotus  >  Forums & community  >  Best Practice Makes Perfect

Best Practice Makes Perfect

A collaboration with Domino developers about how to do it and how to get it right in Domino

Keith Smillie had a question about the above error message, which occurred when he tried to add an "on behalf of" name to an agent by just creating a $OnBehalfOf text item.

The "On Behalf Of" value is stored in the agent design note item $OnBehalfOf, and is a text value. However, it is not valid to store a value in this item unless the "ODS version" of the design element is such as to support this feature. If you refer to the C API guide, the relevant structure is ODS_ASSISTSTRUCT, whose wVersion element must be 2 or higher. This binary structure is stored in the $AssistInfo item of the agent design note. At this time, there are no differences between the ODS formats besides this version number, but consult the latest API documentation to make certain.

There are a few different ways to fix this problem:

  • Edit the agent in Domino Designer.
  • Use LotusScript or Java to delete the $OnBehalfOf item from the agent note (You will need a NotesNoteCollection to get the note ID of the agent so that you can open it as a NotesDocument).
  • Use the C API for Notes to adjust the version number in the $AssistInfo item.
  • Export the agent to DXL, modify the DXL, and re-import it to update the agent.
Note: The latest version of the C API toolkit and documentation, is available in the Downloads section of the Lotus developerWorks website, under Downloads, Toolkits.

Andre Guirard | 12 May 2008 05:03:00 AM ET | Home, Plymouth, MN, USA | Comments (1)


1) out of office
Romi Bassett | 6/5/2009 1:05:40 PM

I'm a novice at this but had to share an easy fix to a related error to this post. I was getting a Domino Designer error: "This agent contains an illegally added 'On behalf' attribute. To make the agent valid, please remove it. OK" " on an Out of Office Agent of a user.

All we did to fix it was:

1. delete the Out of Office Agent;

2. refreshed the design so the template including the Out of Office Agent was reapplied;

3. enabled the Out of Office Agent in the client; and

4. then in Designer, on the Design Properties of the Out of Office Agent, we made sure the "Prohibit design refresh or replace to modify" was checked (having it unchecked is why we think it became corrupt or "on behalf'd".

Hope this helps someone out there.


 Add a Comment
Comment:  (No HTML - Links will be converted if prefixed http://)
Remember Me?     Cancel

Search this blog 


    About IBM Privacy Contact