Record the names of any other custom repository objects that you created or updated. You might have to export these objects from your current installation and then reimport them to the newer version of Waveset after upgrading.
Admin group |
Resource form |
Admin role |
Role |
Configuration |
Rule |
Policy |
Task definition |
Provisioning task |
Task template |
Remedy configuration |
User form |
Resource action |
|
The SPML 2.0 implementation in Waveset changed in version 8.0. In previous releases, the SPML objectclass attribute used in SPML messages was mapped directly to the objectclass attribute of Waveset User objects. The objectclass attribute is now mapped internally to the spml2ObjectClass attribute and is used internally for other purposes.
During the upgrade process, the objectclass attribute value is automatically renamed for existing users. If your SPML 2.0 configuration contains forms that reference the objectclass attribute, you must manually change those references to spml2ObjectClass.
Waveset does not replace the sample spml2.xml configuration file during an upgrade. If you used the spml2.xml configuration file as a starting point, be aware that this file contains a form with references to objectclass that you must change to spml2ObjectClass. Change the objectclass attribute in forms (where it is used internally), but do not change the objectclass attribute in the target schema (where the attribute is exposed externally).
You can use the Waveset SnapShot feature to copy the following, specific object types from your system for comparison:
AdminGroup |
ResourceAction |
AdminRole |
Resourceform |
Configuration |
Role |
EmailTemplate |
Rule |
Policy |
TaskDefinition |
ProvisionTask |
TaskTemplate |
RemedyConfig |
UserForm |
For specific instructions, see Step 5: Take a Snapshot.