Content authors can create future version of the channel(s), known as Screens Launch and further set the live date for this launch. This allows allows the content to be live in devices or players on the specified live date.
With the help of Screens Launch, authors can preview each channel in the launch and should be able to initiate a request for review. Approvers group will get notification and can approve or reject the request. When the live date is reached, the content plays in the devices.
For example, if the author wants to create future versions of c1, c2 (channels), a launch is created and a live date is set (for instance, Nov 10th 8:00 AM). Any further updates in the content is sent out for review.
Once approved and on live date (Nov 10th, 8:00 AM), this launch plays the content on the devices or players.
Before you start leveraging Screens Launch in an AEM Screens project, make sure you understand the concept of Grace Period and its relevance.
Running an experience on the set live date on the player involves:
promotion of the launch (typically takes a few seconds)
publishing the resources to publish instances (typically takes a few minutes, depends on the size of the channels or assets that needs to be published)
time taken by the update offline content to complete (typically takes a few minutes)
time taken by the players to download the content from the publish instance (typically takes minutes depending on the bandwidth and size of the assets that needs to be downloaded)
any time differences of the server and the player
In order for the player to be able to start playing the content on the set live date, we need to start the preceding activities before the live date.
If the live date is Nov 24th, 9:00 AM and grace period is 24 hours, then the above sequence of actions will start at (live date - grace period), that is, Nov 23rd, 9:00 AM server time. This gives 24 hours time to complete all the above mentioned actions and the content will reach the players. Players will understand that this is a launch content, so the content will not play immediately, but players will store this content as a future version and will start playing exactly at the set live date on the player’s time zone.
For example let’s say, server is in PST and the devices are in EST, max time difference is 3 hours in this case and assume that promotion will take 1 min and publishing from author to publish takes 10 min and player can download the resources typically in 10-15 min. Then grace period = time difference (3 hours) + time to promote the launch (1 min) + time to publish the launch (10 min) + time to download at player (10-15 min) + buffer (to be safe, say 30 min) = 3 hours 56 min = 14160 seconds.
So, whenever we schedule any launch live, the promotion will start early by this offset. In the above equation, most of the items does not take much time, we can use a decent guess for this offset once we know the maximum time difference between the server and any player.
Out-of-the-box, the grace period for Screens Launch is set to 24 hours which means that when we set live date for any launch for the resources under /content/screens, the promotion will start with this offset.
This section explains how you can update an out-of-the-box Grace Period to 10 minutes.
/apps/system/configand right-click and paste.
/apps/system/config/com.adobe.cq.wcm.launches.impl.LaunchesEventHandler.configto open the file in the editor in CRXDE Lite. It must show the grace period for the path /content/screens/ as 86400. Change that value to 600.
Now the content in the text file should look similar to:
launches.eventhandler.launch.promotion.graceperiod=[ \ "/content/screens(/.*):600", \ ]
Since you have set the Grace Period to 10 minutes in the preceding example, when you set live date for any launch for the resources under /content/screens, the promotion will start with this offset.
For example, if the live date is set as Nov 24th, 9:00 AM and grace period is 600 seconds, the promotion job will start on Nov 24th at 8:50 AM.
This section demonstrates how to implement Screens Launch in your AEM Screens project.
Follow the steps below to implement Screens Launch functionality to your AEM Screens project:
Create a sequence channel in your AEM Screens project, for example LaunchesDemo --> Channels --> FutureLaunch, as shown below.
You must create a launch from a pre-existing channel in your AEM Screens project.
Select the channel FutureLaunch and click Create Launch from the action bar.
The Create Launch wizard opens. Either you can select the channel that is already visible in the wizard or click + Add Channels to add the channel for which you want to create the launch.
Click Next from the Create Launch wizard. The Include subpages option is selected by default.
You can use + Add Channels option to add another channel for which you want to create the launch for.
To use Add Channels option, navigate to the channel for which you want to create the launch for and click Select.
The Select option will be disabled if you try to select multiple channels or a folder for adding the launch.
Once you have selected the channel/channels, click Next.
Enter the Launch Title as SummerPromotions and you do not need to set the Launch Date, as shown in the figure below. Click Create.
Enabling or checking the option Inherit source page live data allows the channels to be created as live copies in the launch. If any changes are made in the original channel, those changes are automatically applied to launch channels.
Disabling or unchecking Inherit source page live data allows the channels to be be copied without any live relationship in the launch. So, if any changes are made to the original channel, those changes are not applied to launch channels.
You can set the live launch date in this step or can set it up later while editing the properties of the launch once it has already been created.
Understanding Launch Promotion Scope
Promote full launch: All the channels of the launch are promoted at the set live date.
Promote modified pages: Only modified launch resources will be promoted. It is recommended to use this option when the launch review is not required.
Promote approved pages: This option requires the launch approval workflow to run on the launch channels. Only approved pages will be promoted at the set live date.
Launch live date respects player/device’s timezone rather than server’s.
You will see that your launch is created. You can either click Open to view the pages in the editor or click Done to navigate back to your project.
Clicking Done allows you to navigate back to your FutureLaunch channel.
After the launch is created, you can update the properties such as live date, launch title and promotion scope by using Launch Properties.
Follow the steps below to edit the launch properties:
Navigate to the channel FutureLaunch, (that is the pending launch) and select the channel, as shown in the figure below.
Click on Dashboard from the action bar and you see the PENDING LAUNCHES panel from the channel dashboard.
Select the launch and click Launch Properties from the PENDING LAUNCHES panel.
After you have created the launch, you can add or remove channels to the existing launch using Edit Launch option.
Once you are done, click Save to navigate back to FutureLaunch channel.
You can promote the launch manually using the Promote Launch option from the PENDING LAUNCHES panel.
You can choose the resources you want to promote as part of this manual promotion in the Launch Promotion Wizard.
You can delete the launch using Delete Launch option from the PENDING LAUNCHES panel.
This action will delete all the descendants (nested launches) also.