* Configuration changes are promoted based on individual objects. For example, if two projects modify the same object (such as a report), both sets of changes to the object will be promoted when either project involving that object is promoted.
* Some data will not be promoted when T2P is run. This includes the details about the last and next run for autoloaders and scheduled exports, as well as associated organization IDs in signup pages and autoloader configurations.
* This article pertains to the online version of T2P, not the desktop tool. The online version of the T2P tool is not intended to replace the Desktop version at this time. Each functions a bit differently, and you can choose whichever one best suits your preferences for the time being. For example, the project-based T2P does not connect to both databases simultaneously. Instead, whenever a configuration change is made anywhere in the system, it is logged as a candidate for promotion. You then export these changes to the target instance, where you can review and select which changes to promote. In a future release we plan to introduce the ability to roll back changes in the Testing environment for cases where you choose not to promote a change.
<!-- * When a change is promoted, the update log will display the name of the person who performed the promotion, not the individual who originally made the change in the Development environment. To determine who configured a specific change, refer directly to the Development environment. While you can still promote the change log using the desktop tool, we plan to enable change log promotion within the project-based tool in a future release. -->
===Importing Changes from Another Environment===
To import changes within the target environment, follow these steps:
To import changes within the target environment, follow these steps:
# Go to '''Menu''' Icon > T2P (located under the “System Process” section) > '''Import''' tab
# Review the list of packages imported and their status.
# For any packages that have a status of '''Promotable''', click the '''View''' button (has an eye icon) to view the details of the changes in the package.
# Check or uncheck any changes from this package that you want to import into your current environment and then click the '''Promote''' button to apply those changes. Note changes in the package are compared with what is configured on the target environment. Only the differences are listed on the compare page.
# Back on the '''Import''' tab that displays the list of packages, click the '''Export''' button for the package you promoted once you are done testing on this environment to send this package of changes to the next environment Example move from test to production.
# (Optional) you may also view packages already promoted to get more details.