Zimbra

jeross · #1 (**permalink**) 04-14-2008, 07:34 AM

Hi,

We're currently attempting to integrate our application with Zimbra. One of the requirements we have is to create Zimbra tasks and appointments as part of the application's workflows, which we can successfully do through the SOAP api. However, for each generated task or appointment we need to maintain a link back to the "owning" workflow. So, is there a way through the SOAP api to save additional external information with Zimbra objects (tasks or appointments) and then have that external information returned when querying those objects back (again through the SOAP api)? Being able to save a single string or int would do the trick for us.

thanks
J.

jeross · #2 (**permalink**) 04-16-2008, 04:47 AM

Any advice from the Zimbra dev team? Even if this is not possible can someone let me know so we can investigate alternative approaches?

jeross · #3 (**permalink**) 05-04-2008, 01:20 AM

Can anybody help with this? Thanks!

uxbod · #4 (**permalink**) 05-04-2008, 01:57 AM

Don't forget to update your profile please as the API will have different capabilities dependant on which version of ZCS you are running

fmaguin · #5 (**permalink**) 05-05-2008, 01:35 AM

Hi Jeross,

Maybe you could have a look at the xprop element for non standard properties (see soap-calendar.txt and RFC 2445 §4.8.8.1 for more informations).
I have not tested it but I would appreciate feedback if it fits your need and if you manage to use it as I may encounter the same need soon for my dev.

HTH.

jeross · #6 (**permalink**) 05-13-2008, 05:08 AM

Thanks for spotting that. I will check it out over the next couple of weeks once I free up some time. In the meantime, do you know whether it's possible to search for all tasks/appointments with a specific extended property?

jeross · #7 (**permalink**) 05-16-2008, 09:49 AM

OK - I have spent some time checking this out. The good news is that the xprop mechanism does allow the saving of additional properties along with an appointment or task. The bad news is that I rely on the SearchRequest soap call to extract appointment/task information and it seems like the extended properties are not included in the results of that. The only soap call where I have (so far) seen the extended properties appear is with GetMsgRequest.

Does anyone know of a way of making SearchRequest return the extended properties?