In contrast to the generic URI template preview provider, the generic preview URL service provider does not provide the URL to the previewable content. Instead the URL to an external preview URL service is provided, which is responsible to deliver the effective preview url for the content.

The url to the preview service is configured very similar to the generic URI template preview provider. The provided url of the preview url service is extended by client side runtime query parameters for example like this:

https://my-preview-url-service.de/previewurl/550?contentType=CMChannel&previewDate=XXXX&
      view=XXX&userVariant=&userVariantTS=1592902149681&p13n_test=true&contentTimestamp=48634
    

In this example, the full querystring was appended by the studio client to the url of the basic preview url service ('https://my-preview-url-service.de/previewurl/550').

The appended querystring is added at runtime and cannot be altered. An external preview url service has to implement this 'contract'. This means, if the service wishes to support e.g. the preview date, he has to use the predefined date format and the query parameter name 'previewDate'.

Figure 7.11.  Studio with multiple Previews

In order to enable the generic preview URL service provider, add a struct to the 'previews' array with these keys: