jmckay123 Absent Member.
Absent Member.
266 views

Creating a recurring appointment

I'm having trouble creating a recurring calendar appointment. See the example xml code I am sending. The
problem is that only the first instance of the recurrence shows up in the calendar. When I go to delete the entry
manually, the GW client asks me if I want to delete just that instance or all instances, so somehow it thinks the
appointment is recurring, it just does not show up. I have also tried sendItemRequest as in the documentation but
there is no difference. Any ideas?

<m:createItemRequest>
<item type="Appointment">
<container>A.Transend.PO.100.0.1.0.1@19</container>
<subject>Exchange native daily test</subject>
<place>Seattle</place>
<startDate>2019-07-08T15:00:00Z</startDate>
<endDate>2019-07-08T15:30:00Z</endDate>
<options>
<priority>Standard</priority>
</options>
<message>
<part contentType="text/plain" length="84">
RXZlcnkgZGF5IHN0YXJ0aW5nIDcvOC8yMDE5IGZvciAxMCBvY2N1cnMsIDEwYW0gdG8gMTA6MzBhbS4NCi==
</part>
</message>
<rrule>
<frequency>
Daily
</frequency>
<count>
10
</count>
<interval>
1
</interval>
</rrule>
</item>
</m:createItemRequest>

Labels (1)
0 Likes
5 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Creating a recurring appointment

You have to use sendItemRequest.
createItemRequest is used mainly for archiving.
createItemRequest is used to put an item into the user's database
without executing any business logic (such as handling recurrence).
If you use createItemRequest, only one item is created.

Make sure your namespaces are all correct.
On recurrence rules, make sure you pass <honorRule>true</honorRule>.
The GW Win32 Client uses the same recurrence logic under the covers,
but does it a different way. If you don't pass <honorRule>1</honorRule>,
the results may be unexpected.
If the sendItemRequest is successful, the sendItemResponse should have
the id's of the items created.

<?xml version="1.0" encoding="UTF-8"?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<session
xmlns="http://schemas.novell.com/2005/01/GroupWise/types">pl_EwM4KkncbEKOT</
session>
</S:Header>
<S:Body>
<ns2:sendItemRequest
xmlns="http://schemas.novell.com/2005/01/GroupWise/types"
xmlns:ns2="http://schemas.novell.com/2005/01/GroupWise/methods"
xmlns:ns3="http://schemas.novell.com/2005/01/GroupWise/events">
<ns2:item xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="Appointment">
<subject>5 time</subject>
<message>
<part>VGhpcyBpcyBhIG1lc3NhZ2UgYm9keQ==</part>
</message>
<rrule>
<frequency>Daily</frequency>
<count>5</count>
<interval>1</interval>
<honorRule>true</honorRule>
</rrule>
<startDate>2019-06-24T06:00:00.000+02:00</startDate>
<endDate>2019-06-24T06:30:00.000+02:00</endDate>
</ns2:item>
</ns2:sendItemRequest>
</S:Body>
</S:Envelope>

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<gwm:sendItemResponse
xmlns:gwe="http://schemas.novell.com/2005/01/GroupWise/events"
xmlns:gwm="http://schemas.novell.com/2005/01/GroupWise/methods"
xmlns:gwt="http://schemas.novell.com/2005/01/GroupWise/types">

<gwm:id>5CF7B9DB.domain.PO1.100.1776172.1.1652F.1@4:7.domain.PO1.100.0.1.0.1
@16</gwm:id>

<gwm:id>5CF7B9DB.domain.PO1.100.1776172.1.16530.1@4:7.domain.PO1.100.0.1.0.1
@16</gwm:id>

<gwm:id>5CF7B9DB.domain.PO1.100.1776172.1.16531.1@4:7.domain.PO1.100.0.1.0.1
@16</gwm:id>

<gwm:id>5CF7B9DB.domain.PO1.100.1776172.1.16532.1@4:7.domain.PO1.100.0.1.0.1
@16</gwm:id>

<gwm:id>5CF7B9DB.domain.PO1.100.1776172.1.16533.1@4:7.domain.PO1.100.0.1.0.1
@16</gwm:id>
<gwm:status>
<gwt:code>0</gwt:code>
</gwm:status>
</gwm:sendItemResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


If you still have a problem, send me the full SOAP trace of
the sendItemRequest and the sendItemResponse.

Preston
0 Likes
jmckay123 Absent Member.
Absent Member.

Re: Creating a recurring appointment

honorRule sounded like the magic keyword, but it still makes no difference to me, I still get just that initial instance. Following is the exact data I'm uploading and what I get back:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:t="http://schemas.novell.com/2005/01/GroupWise/types"
xmlns:m="http://schemas.novell.com/2005/01/GroupWise/methods">
<soap:Header soap:encodingStyle="">
<session>OpV2CTzoqx2tUKds</session>
</soap:Header>
<soap:Body>
<m:sendItemRequest>
<item type="Appointment">
<subject>Exchange native daily test</subject>
<place>Seattle</place>
<startDate>2019-07-08T15:00:00Z</startDate>
<endDate>2019-07-08T15:30:00Z</endDate>
<options>
<priority>Standard</priority>
</options>
<message>
<part contentType="text/plain" length="84">
RXZlcnkgZGF5IHN0YXJ0aW5nIDcvOC8yMDE5IGZvciAxMCBvY2N1cnMsIDEwYW0gdG8gMTA6MzBhbS4NCi==
</part>
</message>
<rrule>
<frequency>
Daily
</frequency>
<count>
10
</count>
<interval>
1
</interval>
<honorRule>true</honorRule>
</rrule>
</item>
</m:sendItemRequest>
</soap:Body>
</soap:Envelope>


Response:

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Header soap:encodingStyle="">

</soap:Header>

<soap:Body>

<gwm:sendItemResponse xmlns:gwm="http://schemas.novell.com/2005/01/GroupWise/methods" xmlns:gwt="http://schemas.novell.com/2005/01/GroupWise/types">
<gwm:id>
5CF7A108.Transend.PO.100.16E7773.1.352.1@4:7.Transend.PO.100.0.1.0.1@16
</gwm:id>
<gwm:status>
<gwt:code>
0
</gwt:code>
</gwm:status>
</gwm:sendItemResponse>

</soap:Body>

</soap:Envelope>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Creating a recurring appointment

A few things.
You don't have a default namespace.
In my example, it is
'xmlns="http://schemas.novell.com/2005/01/GroupWise/types"'

You don't have the xsi prefix:
'<ns2:item xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="Appointment">'

Do you have actual <CR><LF> / whitespace in your rrule elements?
<frequency>
Daily
</frequency>

I believe it needs to be something like:
<frequency>Daily</frequency>

Preston



>>>


> honorRule sounded like the magic keyword, but it still makes no
> difference to me, I still get just that initial instance. Following is
> the exact data I'm uploading and what I get back:
>
>
> Code:
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> <?xml version="1.0" encoding="utf‑8"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:t="http://schemas.novell.com/2005/01/GroupWise/types"
> xmlns:m="http://schemas.novell.com/2005/01/GroupWise/methods">
> <soap:Header soap:encodingStyle="">
> <session>OpV2CTzoqx2tUKds</session>
> </soap:Header>
> <soap:Body>
> <m:sendItemRequest>
> <item type="Appointment">
> <subject>Exchange native daily test</subject>
> <place>Seattle</place>
> <startDate>2019‑07‑08T15:00:00Z</startDate>
> <endDate>2019‑07‑08T15:30:00Z</endDate>
> <options>
> <priority>Standard</priority>
> </options>
> <message>
> <part contentType="text/plain" length="84">
>
> RXZlcnkgZGF5IHN0YXJ0aW5nIDcvOC8yMDE5IGZvciAxMCBvY2N1cnMsIDEwYW0gdG8gMTA6M
> zBhbS4NCi==
> </part>
> </message>
> <rrule>
> <frequency>
> Daily
> </frequency>
> <count>
> 10
> </count>
> <interval>
> 1
> </interval>
> <honorRule>true</honorRule>
> </rrule>
> </item>
> </m:sendItemRequest>
> </soap:Body>
> </soap:Envelope>
>
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
>
>
> Response:
>
>
> Code:
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> <?xml version="1.0" encoding="UTF‑8"?>
> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
>
> <soap:Header soap:encodingStyle="">
>
> </soap:Header>
>
> <soap:Body>
>
> <gwm:sendItemResponse
> xmlns:gwm="http://schemas.novell.com/2005/01/GroupWise/methods"
> xmlns:gwt="http://schemas.novell.com/2005/01/GroupWise/types">
> <gwm:id>
>
> 5CF7A108.Transend.PO.100.16E7773.1.352.1@4:7.Transend.PO.100.0.1.0.1@16
> </gwm:id>
> <gwm:status>
> <gwt:code>
> 0
> </gwt:code>
> </gwm:status>
> </gwm:sendItemResponse>
>
> </soap:Body>
>
> </soap:Envelope>
>
>
> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑


0 Likes
jmckay123 Absent Member.
Absent Member.

Re: Creating a recurring appointment

It was the white space in <frequency>. Odd, because in the other directory, the API delivers all data with white space, but no matter.
I also found that createItemRequest will work fine for recurring events. And it's excellent that the API delivers the ids of each instance,
I assume I can use these to update deleted or changed instances.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Creating a recurring appointment

Using createItemRequest will bypass other logic
(such as rule processing).
It would be safer to use sendItemRequest (even
on personal / posted items).

You might come across some issues using the id's
returned. They can be used to identify the items,
but there might be some issues using the id's for
accessing the items.


>>>


> It was the white space in <frequency>. Odd, because in the other
> directory, the API delivers all data with white space, but no matter.
> I also found that createItemRequest will work fine for recurring events.
> And it's excellent that the API delivers the ids of each instance,
> I assume I can use these to update deleted or changed instances.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.