Allow enable/disable the propagation of Contributed Fragments on the instance startup

Context

As an Admin I want to enable/disable the propagation of changes for the Contributed Fragment on the startup, so that, I need a new Intance Setting to configure it.

Based on the OutofMemoryError Bug and the findings when looking for a solution, it becomes necessary to find a way to prevent the automated propagation of Contributed Fragments when customers re-deploy their portal.

Acceptance Criteria

1. Enable an Instance Setting –>Page Fragments called "Propagate Contributed Fragments Changes During Deploy Process Automatically" that allows control of whether the automatic propagation process on startup is triggered or not.

2. This setting will be active by default - therefore there are no breaking changes for current customers.

3. This setting includes a description for the end-user about what means Contributed Fragment.

4. If disabled:

   • Contributed fragments will not be propagated when the portal is re-deployed.

   • Al new "Propagate Changes" button will appear. This button will allow customers to manually propagate contributed fragments. This button will trigger the propagation of ALL contributed Fragments in ALL sites (just like when you re-deploy). This process runs in async, users will be able to move out of this setting screen and the process will not stop.

   • Show a Modal warning with several warnings to users (copies defined in Design deliverables), with options to Continue or to Cancel the action.

   • Warnings:

     1. Work loss if pages are opened for edition by content creators

     2. Possible performance problems.

     3. Note that all sites will be affected by the propagation.

   • Once the propagation is ended, show a Dismissible Alert and a Feedback Alert (TBC) indicating the success or error.

   • If the process was successful the button appear disabled until a new deployment (TBC).

   • If the process was unsuccessful, the button appears enabled.

Design Deliverables

Figma

Definition of Done (DoD)

• All Acceptance Criteria were passed;

• Make sure that the expected automated tests were created (unit/integration/functional) and passed successfully;

• Validated by QA and Product Manager;

Testing Scenarios

TBD

Notes

QA NOTE: Keep in mind this story should also fix bug

Test Scenarios