Retain GroupWise
GroupWise Item Date Handling
This information was received from a Novell GroupWise agent developer:
Internally the field for startDate is BEGIN_SECS. All items have a BEGIN_SECS field. In Cornell, we will expose that field on all items as <begins>.
There are three fields dealing with when the item was created / delivered:
- created
- delivered
- begins
On non calendar items, created and begins should be the same value (they might be off by a few seconds). Created and delivered have a bigger chance of being off by a few seconds.
Some items don't have a internal stored value for delivered. In that case we will return first BEGIN_SECS as delivered otherwise we will use created.
In the case of delivered, you don't know what value it represents. It would be safer to use created as the alternate of startDate. In talking with another developer, he said delivered date is the preferred field to use for non calendar items.
User Authentication Into Retain
You can't have two users in gw with the same userID and get retain to auth properly. Retain takes the userid and pwd it's been given and asks the POA to perform an auth. The POA has no idea which jdoe it's supposed to try and it will only try one. You'll either get an ambiguous user error from the POA (which doesn't show in the Retain UI) and the login will fail or it will only try the first jdoe. Once the POA confirms the auth it passes back the GW GUID to Retain. Retain takes this GW GUID and looks up the Retain UUID. That's the retain mailbox you'll be logged into. This worked fine in v2 but v3 broke it and there were two different fixes made to v3 to fix this. [SOURCE: Ernie Riedelbach 6/24/15]
