Copying a custom content version to begin a new release

This is the process for starting a new release cycle for a closed custom content version.

  1. Expand the content version folder and select the version to copy.
  2. Click Copy.
  3. Perform one of these steps:
    • If you are patching a content version, specify the existing originator and a new originator version.
    • If you are forking a content version, specify a new originator and a new originator version.
  4. Click OK.
  5. Select Portal Configuration > Content Activations.
  6. Perform one of these steps:
    • If you patched the content version, the originator is the same, so in the Version column, select the new version number.
    • If you forked the content version, the originator is new, so click New and select the originator and version you just created. Give it the highest priority and click OK.
  7. Click Save.
  8. Activate managed schema, if applicable.
  9. Select Portal Configuration > Developer Options.
  10. Click Enable Portal for Development.
  11. Specify this content version as the editable originator, specify a default feature, and click Save.
    Note: If this is the only enabled-for-development content version activated for the portal and it is at the highest priority, it is specified automatically.