updated as originals are updated. There is one known caveat. If you attempt
to create an archive by copying the schema, be aware there is a TAG
contained in the CM 3.0 schemas which is used by the Remedy Application
Service or Approval engine which checks for apparent duplicates or
"unregistered" CM3.0 schemas. This will prevent proper DSO action.
It is best to copy the key fields needed for your archive to a new schema.
This will prevent the TAG problem. This will also minimize archiving
unnecessary data, i.e. Hidden field data used by workflow. Otherwise, works
well.
TJH
-----Original Message-----
From: lsteinem@CSC.COM [mailto:lsteinem@CSC.COM]
Sent: August 29, 1999 07:29
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Helpdesk 3.0 and CM 3.0 with DSO
Hi folks,
I'm wonder if there is anyone out there in the hugh Remedy
world who has
or
is just now doing an implementation with Helpdesk 3.0 and or
Change
Management 3.0 on different servers using DSO to synchronize
them.
Any feedback, experience or other comments about that would
really
appreciate.
We are in the process of doing that for one of our customer.
Many thanks in advance
and best regards,
Luc
Ps: you may also contact me directly to
lsteinem@csc.com