Hide an AVEVA owned Template Fragment but allow to be applied to any given CL

As a Solution Owner,

I/we can Enable an ISM Fragment template so that a Customer can use it without being able to amend the structure of it,

so that they can enable the use of the template on the project without breaking it by accident

As a Product Owner,

I/we can Enable an ISM Fragment template so that a Customer can use it without being able to amend the structure of it,

so that they can enable the use of it to enhance the use of my Product without breaking the template by accident

Description/Business Need

To enable the utilisation of the API AAV-1800 by a specific product or solution a customer may need to enrich their class library with defined Extensions or Config Schema that can be applied onto their Class Library. Currently we would utilise a fragment to create this schema template which is shown in the Catalogue as a Class Library, this means that a customer may have this fragment template visible in their Class Library meaning they can amend the structure. Removing the visibility of this fragment in the catalogue, but still enabling the ability to make it part of the Class Library Composition, will mean AVEVA will has full control of this Fragment providing its use without potential misuse. Managing version control and the fragment itself will need to be managed by the solution that owns the template. The delivery of a given fragment is currently envisioned to be delivered by Deployment - this may need to reviewed when assessed for Acceptance Criteria