As an administrator I can create fragments in the "global" content repository to make them available for all sites

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.X, Master
• Component/s: Fragment Administration
• Labels:
  • 7.2-sp1-could
  • fc_19_07
  • fc_19_08
  • fc_19_09
  • test_manual_done
  • test_map
• Epic Link: Sharing fragments across sites ("global" content repository)

Context

As an administrator I can create fragments in the "global" content repository to make them available for all sites, so that it is possible to share fragments across sites (without having to deploy them as contributed fragment collections)

Acceptance Criteria:

• Given a collection of fragments has been created in the global repository, when a site admin goes to the "Fragments" application then the collection is visible in the left menu with a visual indication that the collection is inherited (this could be an icon which, when hovered shows information about the source content repository/site)
• Given a collection of fragments has been created in the global repository , when a site admin goes to the "Fragments" application and clicks the fragment then the fragment should be shown in "view" mode, without allowing any modifications (optionally, do not allow clicking on the fragment and show a lock icon or similar)
• Given a collection of fragments has been created in the global repository, when a site admin goes to the "Fragments" application then the user should be able to make a copy of the fragment into a collection specific to the current site.*
• Given a collection of fragments with some resources used by one of its fragment has been created in the global repository, when a site admin goes to the "Fragments" application, within the collection and executes the action to copy the fragment into another collection then the resources referenced from the fragment should be copied into the target collection (unless a resource of the same name exists)***
• Given a collection of fragments with one draft fragment has been created in the global repository, when a site admin goes to the "Fragments" application AND the user clicks on the collection then the draft fragment should not be shown.
• Given a site with a page that uses a fragment which is "inherited" from the global repository when the site is exported as a LAR and imported into a different site which does not "inherit" the fragment then the import should succeed and the page should still work with a copy of the fragment code.
• Given a collection of fragments that has been "inherited" from the global repository when a site administrator accesses the collection within their site then they can export all the fragments of the "inherited" collection or specific fragments.
• Given a collection of fragments in global when the "Propagate Fragment Changes automatically" configuration option is enabled at a system or virtual instance level AND a change is made in a to fragment in the collection in global **then the changes are automatically propagated to all pages that are using the fragment.

Design Deliverables

TBD

Features that don't need to be implemented (yet)

• Ability to view usages of fragments within the global content repository (to be implemented in LPS-100540)
• Ability to propagate changes to fragments within the global content repository to all the sites that might use them (instead, each site should propagate the changes within the site)