As a Site Template Administrator, I want to have the site template propagation run parallel to multiple sites

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Completed
• Affects Version/s: None
• Fix Version/s: 7.2.X, 7.3.X, 7.3.6 CE GA7, Master
• Component/s: Site Templates
• Labels:
  • 7.4
  • 7.4-must
  • 7210-sp-pending
  • 7310-sp-pending
  • fc_20_10
  • fc_20_11
  • fc_20_12
  • fc_21_01
  • fc_21_02
• Branch Version/s:
  7.3.x, 7.2.x
• Backported to Branch:
  Committed
• Epic Link: Improve site template propagation performance
• Sprint: Staging Iteration 1 - Pumukli, Staging Iteration 2 - Kalánka, Staging Iteration 3 - CáPeti, Staging Iteration 4 - CáPali, Staging Iteration 5 -Mekk Elek, StagingIter6 - Ho Ho HoHorgász, StagingIter7 - Törpapa
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/96250

Motivation

We want to change the working method of the site templates to similar to staging.

Currently, the necessary site template propagation happens when an End User accesses a site page that connects to a site template and the End User must wait till the whole propagation process ends.

One of the steps of improving the site template propagation performance is to make parallel propagation processes to multiple sites multi-threaded. The multiple propagations to different sites should go in parallel asynchronous background tasks.

During the propagation, the End Users should not experience slower page load like it is now.

Acceptance Criteria

Design & UX