A ACP Configuration Types

The following are supported ACP configuration types used to propagate data.

A.1 Supported ACP Configuration Types

ACP propagates the data contents of configuration types, which are roughly the same as the Administrator nodes. Not all propagation operations are supported by all Administrator nodes. Administrator Nodes that are Not Propagated for a list of nodes that cannot be propagated.

The following table shows the list of ACP-supported configuration types and the propagation actions that are supported by each type. The corresponding administrator nodes are located in the Java Client.

Table A-1 Administrator > Data Settings > Classes

Configuration Types	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<base_class>	NA	API Name is used as the key, so Base Class and Class cannot be renamed	NA	X	NA
<class>	NA	API Name is used as the key, so Base Class and Class cannot be renamed	NA	X	NA
<subclass>	X	X	X	X

Table A-2 Administrator > Data Settings (except Classes)

Configuration Types	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<<character_set> (Exception: out-of-box character sets are not propagated.)	X	X	X	X	NA
<list>	X	X	X	X	X
<process_extension>	X	X	X	X	NA
<auto_number>	X	X	X	X	X
<criteria>	X	X	X	X	NA

Table A-3 Administrator > Workflow Settings

Configuration Types	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<workflow>	X	X	X	X	NA

Table A-4 Administrator > User Settings

Configuration Types	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<account_policy>	NA	NA	NA	X	NA
<user>	X	X	X	X	NA
<user_group>	X	X	X	X	NA
<supplier_group>	X	X	X	X	NA
<role>	X	X	X	X	NA
<privilege>	X	X	X	X	X

Table A-5 Administrator > System Settings

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<smart_rule>	NA	NA	NA	X	NA
<viewers_and_files>	NA	NA	NA	X	NA
<notification_template>	X	X	X	X	NA
<full_text_search>	NA	NA	NA	X	NA
<column_assignments> (My Assignments)	NA	NA	NA	X	NA
<unit_of_measure_family> (UOM)	X	X	X	X	NA
<company_profile>	NA	NA	NA	X	NA
<ppm_dashboard_management>	X	X	X	X	NA

Table A-6 Administrator > System Settings > Product Cost Management

Configuration Type	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<pcm_ship_to_location>	X	X	X	X	NA
<pcm_rfq_terms_and_conditions>	NA	NA	X	X	NA

Table A-7 Administrator > System Settings > Product Portfolio Management

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<ppm_cost_status>	X	X	NA	X	NA
<ppm_quality_status>	X	X	NA	X	NA
<ppm_resource_status>	X	X	NA	X	NA
<ppm_schedule_status>	X	X	X	X	NA
<ppm_default_role>	NA	X	NA	X	NA

Table A-8 Administrator > System Settings > Agile Content Service

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<acs_subscriber>	X	X	X	X	NA
<acs_destination>	X	X	X	X	X
<acs_event>	X	X	X	X	X
<acs_filter>	X	X	X	X	X
<acs_format_library>	X	X	X	X	NA
<acs_package_service>	X	X	X	X	NA
<acs_response_service>	X	X	X	X	NA

Table A-9 Administrator > System Settings > Product Governance & Compliance

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<pgc_signoff_message>	NA	NA	NA	X	NA
<pgc_compliance_rollup_scheduling>	NA	NA	NA	X	NA
<pgc_compliance_rollup_rule_setting>	NA	NA	NA	X	NA
<pgc_external_rollup_rule_setting>- in the External Rollup node folder	NA	NA	NA	X	NA
<pgc_external_rollup_scheduling> - in the External Rollup node folder	NA	NA	NA	X	NA
<pgc_supplier_declaration> - this config. type contains all data in the Supplier Declaration Process Extensions node folder	NA	NA	NA	X	NA

Table A-10 Administrator > System Settings > Event Management

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<em_event>	X	X	X	X	X
<em_event_handler>	X	X	X	X	X
<em_event_subscriber>	X	X	X	X	NA
<em_event_type>	NA	NA	NA	X	NA
<em_event_handler_type>	NA	NA	NA	X	NA

Table A-11 Administrator > System Settings > Reference Object Management

Configuration Type	Delete	Rename	Copy-Create	Copy Update	Copy-Delete
<reference_object_application>	X	X	X	X	NA

Table A-12 Administrator > Server Settings

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<server_location> (Locations node)	NA	NA	NA	X	NA
<server_file_manager> (Locations > File Manager tab)	X	X	X	X	NA
<server_database> (Database node)	NA	NA	NA	X	NA
<server_preference> (Preferences node)	NA	NA	NA	X	NA
<server_task> (Task Configuration node)	NA	NA	NA	X	NA

Table A-13 Administrator > Search

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<searches>	X	NA	X	X	NA

Table A-14 Administrator > Analytics and Reports

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<reports>	X	NA	X	X	NA

The following tables contains the configuration types that have corresponding administrator nodes in the Web Client.

Table A-15 Tools and Settings > Administration

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<tab_display_configuration>	X	X	X	X	NA

Table A-16 Table View Personalization

Configuration Typs	Delete	Rename	Copy-Create	Copy-Update	Copy-Delete
<global_views>	X	NA	X	X	NA

The following sections provide additional data regarding configuration types, match keys, subobjcts, and deep compare.

The following sections provide additional data regarding configuration types, match keys, subobjcts, and deep compare.

A.2 Configuration Types and Match Keys

This table lists the configuration types and whether the match key is the key used to match objects between Agile instances. In some cases, the key value can be changed, but generally the key is intended to be static.

Configuration Type	Match Key
Classes
<base_class>	API Name
<class>	API Name
<subclass>	API Name
Data Settings
<auto_number>	API Name
<character_set>	API Name
<criteria>	API Name
<list>	API Name
<process_extension>	API Name
Workflow Settings
<workflow>	API Name
User Settings
<account_policy>	API Name
<privilege>	API Name
<role>	API Name
<supplier_group>	Name
<user>	User ID
<user_group>	Name
System Settings
<company_profile>	API Name
<ppm_dashboard_management>	API Name
<full_text_search>	API Name
<column_assignments> (My Assignments)	API Name
<notification_template>	API Name
<smart_rules>	API Name
<unit_of_measure_family>	API Name
<viewers_and_files>	API Name
Product Cost Management
<pcm_ship_to_location>	Name
<pcm_rfq_terms_and_conditions>	API Name
Product Portfolio Management
<ppm_cost_status>	API Name
<ppm_quality_status>	API Name
<ppm_resource_status>	API Name
<ppm_schedule_status>	API Name
<ppm_default_role>	API Name
Agile Content Service
<acs_destination>	API Name
<acs_event>	API Name
<acs_filters	API Name
<acs_package_service>	API Name
<acs_response_service>	API Name
<acs_subscriber>	API Name
Product Governance & Compliance
<pgc_signoff_message>	API Name
<pgc_compliance_rollup_scheduling>	API Name
<pgc_compliance_rollup_rule_setting>	API Name
<pgc_supplier_declaration>	API Name
Event Management
<em_event>	API Name
<em_event_handler>	API Name
<em_event_subscriber>	API Name
<em_event_type>	API Name
<em_event_handler_type>	API Name
Server Settings
<server_location>	API Name
<server_file_manager>	API Name
<server_database>	API Name
<server_preference>	API Name
<server_task>	API Name

A.3 Renaming Subobjects

Additionally, some Administrator objects have subobjects that can be renamed. In order to update the subobject correctly, ACP requires a key map for these subobjects.

Without the map, ACP considers these subobjects to be different: the subobject with the old key is deleted and the subobject with the new key is created.

Configuration Type	Subobject Type	Method for Rename
<base class>	LifeCycle Phases	Subobject Map (API Name)
<class>	Attributes	Subobject Map (API Name)
<class>	LifeCycle Phases	Subobject Map (API Name)
<subclass>	Attributes	Subobject Map (API Name)
<subclass>	LifeCycle Phases	Subobject Map (API Name)
<list>	List Entries	Subobject Map (API Name)
<workflow>	Workflow Statuses	Subobject Map (API Name)
<unit_of_measure_ family> (UOM)	UOMs	Subobject Map (API Name)
<column_assignments> (My Assignments)	Column	Subobject Map (Name)

A.4 Configuration Types as Evaluated by Deep Compare

This table indicates how Deep Compare (the script and the report) evaluates the configuration types tab by tab and exactly what Deep Compare distinguishes about each configuration type. As explained in the "Compare Details" heading, attributes on the General Information tab of all configuration types are considered by Deep Compare, while Where Used and History tabs are not compared.

Deep Compare- Supported Configuration Types	Compare DetailsDeep Compare will take care of Rename / Subobject Mapping / Ignore References.History tabs are not considered for comparison.
<account_policy>	All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Each attribute of this configuration is treated as an individual object.
<acs_destination>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<acs_event>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<acs_filter>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Filter tab: All attributes of the Source object are compared with all attributes of the Target object, if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<acs_package_service>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<acs_response_service>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<acs_subscriber>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Subscriber Details tab: Subscribers Details will be compared based on the Destination(s) match. If source Destination(s) matching with target Destination(s), then other properties i.e., Filter, Roles(s), Format, Language, and Site are compared; otherwise comparison are ignored. However, the report clearly tells that which is a source only object and target only object.
<auto_number>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab: Deep Compare has entries for each Subclass if it does not exist in the source or target.
<base_class>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Life Cycle Phases tab: Life Cycle Name (primary key) is the key value to compare other Life Cycle Phases. All differences are shown in the report including Source Only and Target Only lifecycle names. Process Extensions tab: All names of source process extension (primary key) are the key values to compare all names of target process extension. Classes and Event Subscribers tabs: These tabs are not considered for comparison.
<character_set>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<class>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Life Cycle Phases tab: Life Cycle Name (primary key) is the key value to compare other Life Cycle Phases. All differences are shown in the report, including Source Only and Target Only lifecycle names. Process Extensions tab: All names of source process extension (primary key) are the key values to compare all names of target process extension. Attributes <User-Interface Tabs> tab: Each attribute of a source object is compared to each attribute of the target object by using attribute name. If a match is found, then all properties of that attribute will be compared and reported to Deep Compare if differences are found. If source flex attribute does not exist in the target instance or vice versa, then such difference will be noticed in Deep Compare. However, vice versa of this case is not reported. Only attribute name (regardless of properties change) of source and target will be reported in Deep Compare if you rename out-of-the-box attribute at target/source. However if you use Subobject Map for Attributes, then all properties of that attribute will be compared and reported same if difference found. Classes tab, Event Subscribers tab, and Attachments tab are not considered for comparison purposes.
<company_profile>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<criteria>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Criteria tab: It compares at Criteria Level. If criteria attribute of source and target names are found to be same, then Adv Compare will try to find out any other(Join Operator, Relational Operator and Value) differences in the same level. If there are differences that will be shown in the report otherwise it is not shown in the report. However if Attributes names are different at source and target , then SOURCE ONLY and TARGET ONLY columns will have an entry with reported values. Where Used tab is not considered for comparison.
<em_event>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<em_event_handler>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<em_event_subscriber>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<em_event_type>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<em_event_handler_type>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<full_text_search>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<list>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. List tab: Case 1: List entries of Source or Target are Empty. Deep Compare will show the List Entries/<Empty> of source/target by using delimiters. Delimiters are: | ("pipe" character) - Separates list entries till leaf node, e.g., a|b|c ; (semicolon) - Separates set of list entries separated by pipe, e.g., a|b|c;d|e|f Case 2: List of Source and Target is cascade list. Each list entry of Source is compared with Each list entry of Target by considering the child -parent relationship hierarchy. Not only used List-Name for comparison but also used parent-child relationship hierarchy irrespective of same name existence across List unless sub objects map specification. If source has list entry A and target does not have same entry, Deep Compare will specify "Target Only"/"Source Only" in Status column. Case 3: List of Source and Target is not cascade list. Same as Case 2 except child-parent relationship hierarchy. Case 4: List of Source or Target is cascade list. If any one of Source and Target has cascade list and other has non-cascade list, Deep Compare simply names what are cascade and non-cascade lists (does not show any list entries). The difference column will NOT show a comparison.
<my_assignments> or <column_assignments>	All attributes of the Source instance are compared to all attributes of Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<notification_template>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is not considered for comparison.
<pcm_rfq_terms_and_ conditions>	Text of RFQ Terms and Conditions will be compared.
<pcm_ship_to_location>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<pgc_compliance_rollup_ rule_setting>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<pgc_sign_off_message>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<pgc_supplier_ declaration>	It compares selected process extensions of source and target.
<ppm_cost_status>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<ppm_dashboard_ management>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Tables tab: Deep Compare will try to find a source attribute in target attributes list, if there is a difference between them, then that property will be noticed in report.
<ppm_default_role>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<ppm_quality_status>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<ppm_resource_status>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<ppm_schedule_status>	General Info tab: Over Due Type will be compared. Status tab => General Information tab: Same as above description.
<ppm_ui_configuration_ data>	Content: Attribute Groups: It compares only Selected Attributes and Attribute Groups. Tables: It compares only Selected Columns and tables. Action Groups: It compares only Selected Actions and Action Groups. Layout: It compares only Form and Defined Layouts.
<privilege>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is also considered for comparison.
<process_extension>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Where Used tab is also considered for comparison.
<role>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Privileges tab: Compares all names of source Privileges to the all names of target Privileges, Deep compare will make an entry if there are intersected values are present. Users tab: Compares all names of source Users to the all names of target Users, Deep compare will make an entry if there are intersected values are present. User Groups tab: Compares all names of source User-Groups to the all names of target User-Groups, Deep compare will make an entry if there are intersected values are present.
<server_database>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<server_file_manager>	File Manager tab: Same as General Information tab. Vault Configuration: Deep compare will make an entry if the combination of Vault Type, Description, Base Storage Dir, Purge Dir, and Category gets changed at source or target.
<server_location>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<server_preference>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<server_task>	Task Configuration tab (same as General Information tab): All attributes of the Source instance are compared to all attributes of Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<smart_rule>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<subclass>	Same as Class configuration.
<supplier_group>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report.
<unit_of_measure_ family>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. UOM: It will compare each entry of Source UOM to the each entry of target UOM.
<user>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Preferences tab: Same as General Information tab. Escalations tab: Deep Compare will give only intersected CRITERIA name and NOTIFY USERS separated by":" in the respective columns of the report as separate entries (Source Only and Target Only). However if the CRITERIA name is same at Source and Target but the NOTIFY USERS name(s) is (are)changed in either, then Deep Compare will treat them as a DIFFERENCE value, hence only one entry will be allocated to show the both (source and target)values User Groups tab: Deep Compare will give only intersected USER GROUP name and STATUS separated by":" in the respective columns of the report as separate entries (Source Only and Target Only). However if the USER GROUP name is same at Source and Target but the STATUS name is changed in either, then Deep Compare will treat them as a DIFFERENCE value, hence only one entry will be allocated to show the both (source and target)values Share, Relationships, Subscription and Attachments tabs: These tabs are not considered for comparison.
<user_group>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Escalations tab: Deep Compare will give only intersected CRITERIA name and NOTIFY USERS separated by":" in the respective columns of the report as separate entries (Source Only and Target Only). However if the CRITERIA name is same at Source and Target but the NOTIFY USERS name(s) is (are)changed in either, then Deep Compare will treat them as a DIFFERENCE value, hence only one entry will be allocated to show the both (source and target)values Users tab: Deep Compare will give only intersected USER name and ROLES separated by":" in the respective columns of the report as separate entries (Source Only and Target Only). However if the USER name is same at Source and Target but the ROLES name is changed in either, then Deep Compare will treat them as a DIFFERENCE value, hence only one entry will be allocated to show the both (source and target)values. Share, Relationships and Attachments tabs: These tabs are not considered for comparison.
<viewers_and_files>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Banners and File Association tabs: Compares all names of Source file types to all names of the Target file types. Deep Compare creates an entry if at least one name has been changed at Source or Target. It also compares selected autogenerated Thumbnails. Watermark tab: compares each Watermark of Source to each Watermark of target.
<workflow>	General Information tab: All attributes of the Source instance are compared to all attributes of the Target instance; if Source data does not match Target data, these differences are recorded in the Deep Compare report. Status tab: compares all statuses and its associated Criteria.

A.4.1 Log and Report Files for Deep Compare

• Verbose Log: This log is really not necessary as Deep Compare does not do any update or create actions on Agile instances. This file is empty.

• Error Log: This log file is created in the current project directory with a default filename of deep_compare.err.

• Console (stdout) Log: The following message displays during execution of Deep Compare command.

ACP DeepCompare SUCCEEDED - Completed with no errors or notes.

================DEEP-COMPARE REPORT======================

Report Generation in Progress, Please Wait...

Report Generated Successfully...

Please Check The Report @ D:\ACPWorkDir9.3.3\project2\deep_compare.xls

Error Level = 0

• Process Log: This log file is created in the current project directory with a default filename of deep_compare.log.

• Deep Compare report: The Excel report file is created in the current project directory with a default file name of deep_compare.xls.