Known Limitations
The following limitations must be taken into account when implementing a solution that uses Net Change.
Entity Delete Mode Selection
The delete mode is currently defined in the entity Net Change definition file (feature pack). Only one delete mode is defined. The actual solution does not support the selection of different delete modes per configuration.
Attachment File Support
Attachment files are not supported by Net Change.
Entity Key Modification
If you change a defined entity key after the first Net Change run, the Net Change database for this entity must be recreated. Use the Net Change Setup feature to recreate Net Change database.
storage.properties File Modification
The storage.properties file parameters determine how Net Change stores data in its reference database. The properties than can be set are data compression and encryption, repository location, storage unit interface, and block size.
The values defined in the storage.properties file (UseCompression,
EncryptionMode, StorageUnitImplementation, and
FileStorageUnit.DefaultBlockSize) must not be changed after the
first Net Change run.
If this is required, ALL Net Change database tables must be recreated. Perform an Net Change Setup on every entity subject to a Net Change process.
Multiple Database Synchronization
Net Change maintains a single database to synchronize a customer system data and a Taleo Product data. This implies installing and running a separate instance of TCC for each customer system synchronizing with a Taleo product. For example, synchronizing three different Human Resource Information System (HRIS) databases with one Taleo zone means installing and running three separate instances on TCC. The data provided for synchronization by each HRIS must be mutually exclusive to prevent reversal of operations. For example, if one system deletes an entity on an ongoing integration and the same entity exists on another system, it will be recreated when that system runs its integration.
The same principle applies to synchronizing customer HRIS data with several Taleo zones. For example, synchronizing one customer HRIS with a Taleo production zone and a Taleo staging zone requires installing and running two separate instances of TCC.