This content has been marked as final. Show 3 replies
One of the major flaws of GTC. All the data is contained in the GCD table as well. Most the time you can make changes here, but if you plan to use the GTC tool, it will reset each time you try and make a change, and it will also clear your Lookup.USR_PROCESS_TRIGGERS if it is a trusted one. Just be very careful.
This is indeed a major flaw for GTC. Below I found this issue in a Oracle doc.
Doc Link: http://docs.oracle.com/cd/E14571_01/doc.1111/e14309/aptrouble.htm
Below is a description of this issue from the Oracle documentation
Customization work done on objects of a generic technology connector would be overwritten if you perform a Manage Generic Technology Connector operation.
You can use the Design Console to customize connector objects that are automatically created during generic technology connector creation. However, after you customize connector objects, if you perform a Manage Generic Technology Connector operation, then all the customization done on the connector objects would be overwritten. Therefore, Oracle recommends that you to apply one of the following guidelines:
Do not use the Design Console to modify generic technology connector objects.
The exception to this guideline is the IT resource. You can modify the parameters of the IT resource by using the Design Console. However, if you have enabled the cache for the GenericConnector and GenericConnectorProviders categories, then you must purge the cache either before or after you modify IT resource parameters. See "Purging the Cache" in the Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for information about running the PurgeCache utility.
If you use the Design Console to modify generic technology connector objects, then do not use the Manage Generic Technology Connector feature to modify the generic technology connector.
Connector objects that are automatically created are not deleted even if the generic technology connector creation process fails.