Named and Default Update Sets

• Default > Update set > Named
• Named - Always work in a named Update Set
• Default - Default should not be changed, deleted, or moved between systems

Always work in Update set (not default)

• After go live always work ina named update set.
• Work that is not captured in an update set, must be rolled back before activating an update set to capture the work being repeated.
• Activate an update set, the redo that work to make i tmore moveable.
• if a change is made to a business rule or client script outside of a named update set, ther is no need to undo the change.
• Switch into the named update set and edit the business rule and the latest version to be written to the update set

Best Practices

• Do not open a record set in default and change the update set to your named update set
  • sn check for each recor it writes to an update set
  • if an update already exists, the update may be updated or overwritten
• Do not make the same change manually on the target system
  • if the change involves creating new record, the sys id will be diff and this can cause issues at the next updated
• All needed records
  • for features that involve many system components, update sets package all needed records
  • examples are homepages and workflows
  • These are packaged completely in update sets

Note

Update set as complete - if the default update set is marked complete, the system creates another update set named dfault1 and uses it as the default update set