Contents Now Platform Custom Business Applications Previous Topic Next Topic Getting started with update sets ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Other Share Getting started with update sets Before working with update sets, create a standard process for moving customizations from instance to instance. When working with update sets, be sure to avoid common pitfalls. For example, an update set called Incident Management 2.0 might hold a set of enhancements to incident management. While Incident Management 2.0 is marked as the current update set, all changes are tracked in it. An update set consists of: A set of record details that uniquely identify the update set. A list of configuration changes. A state that determines whether another instance can retrieve and apply configuration changes. By default, update sets only track changes to baseline applications and platform features. This allows developers to create functionality on a sub-production instance and promote the changes to another instance. Administrators have the following options with update sets. Create an update set to store local changes. Select the current update set to store local changes. Commit an update set to prepare it for distribution. Report on the contents of update sets. Compare update sets to determine what differences they contain. Merge separate update sets into a single update set. Create an external file from an update set. Retrieve update sets from remote instances. Apply retrieved update sets. Back out changes applied from an update set. Application developers have options with update sets such as: Create an update set for a specific version of an application. Specify which application tables to track in update sets. When to use update setsUpdate sets is one of available deployment options useful for storing and applying changes. Update sets tablesEach update set is stored in the Update Set [sys_update_set] table, and the customizations that are associated with the update set, which are entries in the Customer Update [sys_update_xml] table, appear as a related list on the update set record.How the system determines the default update setOnly one update set can be the default set for any scope. To set an update set to be the default set, you set the Default set field to true. Update sets for changes to applicationsThe system creates a separate update set for each application that only contains changes associated with the application. This ensures that access settings for each application are properly evaluated and applied when committing update set changes. Customizations in an update setAn update set is an XML file that contains a list of changes to an instance. Administrators can save an update set as a local file that can be transferred to another instance.Update set transfers to other instancesWhen an update set is completed, you can transfer it to another instance to move customizations from development, through testing, and into production.UI actions for exporting and importing customizations in an XML fileThe system allows administrators to directly export and import customizations as XML files.Avoid pitfalls when working with an update setBecause update sets make changes to an instance, review the following best practice information to avoid errors and performance issues. On this page Send Feedback Previous Topic Next Topic
Getting started with update sets Before working with update sets, create a standard process for moving customizations from instance to instance. When working with update sets, be sure to avoid common pitfalls. For example, an update set called Incident Management 2.0 might hold a set of enhancements to incident management. While Incident Management 2.0 is marked as the current update set, all changes are tracked in it. An update set consists of: A set of record details that uniquely identify the update set. A list of configuration changes. A state that determines whether another instance can retrieve and apply configuration changes. By default, update sets only track changes to baseline applications and platform features. This allows developers to create functionality on a sub-production instance and promote the changes to another instance. Administrators have the following options with update sets. Create an update set to store local changes. Select the current update set to store local changes. Commit an update set to prepare it for distribution. Report on the contents of update sets. Compare update sets to determine what differences they contain. Merge separate update sets into a single update set. Create an external file from an update set. Retrieve update sets from remote instances. Apply retrieved update sets. Back out changes applied from an update set. Application developers have options with update sets such as: Create an update set for a specific version of an application. Specify which application tables to track in update sets. When to use update setsUpdate sets is one of available deployment options useful for storing and applying changes. Update sets tablesEach update set is stored in the Update Set [sys_update_set] table, and the customizations that are associated with the update set, which are entries in the Customer Update [sys_update_xml] table, appear as a related list on the update set record.How the system determines the default update setOnly one update set can be the default set for any scope. To set an update set to be the default set, you set the Default set field to true. Update sets for changes to applicationsThe system creates a separate update set for each application that only contains changes associated with the application. This ensures that access settings for each application are properly evaluated and applied when committing update set changes. Customizations in an update setAn update set is an XML file that contains a list of changes to an instance. Administrators can save an update set as a local file that can be transferred to another instance.Update set transfers to other instancesWhen an update set is completed, you can transfer it to another instance to move customizations from development, through testing, and into production.UI actions for exporting and importing customizations in an XML fileThe system allows administrators to directly export and import customizations as XML files.Avoid pitfalls when working with an update setBecause update sets make changes to an instance, review the following best practice information to avoid errors and performance issues.
Getting started with update sets Before working with update sets, create a standard process for moving customizations from instance to instance. When working with update sets, be sure to avoid common pitfalls. For example, an update set called Incident Management 2.0 might hold a set of enhancements to incident management. While Incident Management 2.0 is marked as the current update set, all changes are tracked in it. An update set consists of: A set of record details that uniquely identify the update set. A list of configuration changes. A state that determines whether another instance can retrieve and apply configuration changes. By default, update sets only track changes to baseline applications and platform features. This allows developers to create functionality on a sub-production instance and promote the changes to another instance. Administrators have the following options with update sets. Create an update set to store local changes. Select the current update set to store local changes. Commit an update set to prepare it for distribution. Report on the contents of update sets. Compare update sets to determine what differences they contain. Merge separate update sets into a single update set. Create an external file from an update set. Retrieve update sets from remote instances. Apply retrieved update sets. Back out changes applied from an update set. Application developers have options with update sets such as: Create an update set for a specific version of an application. Specify which application tables to track in update sets. When to use update setsUpdate sets is one of available deployment options useful for storing and applying changes. Update sets tablesEach update set is stored in the Update Set [sys_update_set] table, and the customizations that are associated with the update set, which are entries in the Customer Update [sys_update_xml] table, appear as a related list on the update set record.How the system determines the default update setOnly one update set can be the default set for any scope. To set an update set to be the default set, you set the Default set field to true. Update sets for changes to applicationsThe system creates a separate update set for each application that only contains changes associated with the application. This ensures that access settings for each application are properly evaluated and applied when committing update set changes. Customizations in an update setAn update set is an XML file that contains a list of changes to an instance. Administrators can save an update set as a local file that can be transferred to another instance.Update set transfers to other instancesWhen an update set is completed, you can transfer it to another instance to move customizations from development, through testing, and into production.UI actions for exporting and importing customizations in an XML fileThe system allows administrators to directly export and import customizations as XML files.Avoid pitfalls when working with an update setBecause update sets make changes to an instance, review the following best practice information to avoid errors and performance issues.
