Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference

Repository Guide

Repository Guide

Changing Folder Status

Changing Folder Status

To configure operations that users can perform, you can change the folder status. To change the folder status, edit the folder in the Repository Manager. You can configure a folder with one of the following statuses:
  • Active.
    This status allows users to check out versioned objects in the folder.
  • Frozen, Allow Deploy to Replace.
    This status prevents users from checking out objects in the folder. Deployment into the folder creates new versions of the objects.
  • Frozen, Do Not Allow Deploy to Replace.
    This status prevents users from checking out objects in the folder. You cannot deploy objects into this folder.
You might change the status of a folder to serve different purposes depending on the configuration of the environment and the development processes. For example, an environment uses a development repository for creating and testing metadata, and it uses a production repository for running the workflows and sessions. In the development repository, you might change the status of a folder from active to Frozen-Do Not Allow Deploy to Replace in a code freeze situation. This prevents other users from checking out objects in the folder and creating new versions. Both of the Frozen statuses allow the Repository Manager to add objects in the folder to a deployment group.
In the production repository, you might change the status of a folder from active to Frozen-Allow Deploy to Replace to ensure that copy deployment group operations successfully complete. The Frozen-Allow Deploy to Replace status prevents other users from checking out objects in the folder, but it allows the Copy Deployment Group operation to create new versions of objects. The Frozen-Do Not Allow Deploy to Replace status prevents the Copy Deployment Group operation from creating new versions of the objects.
Before you change the status of a folder, you might want to verify that other users do not have objects in the folder checked out.

0 COMMENTS

We’d like to hear from you!