Manage Themes with Life Cycle Management

If you have Life Cycle Management (LCM; see Managing Workspaces via Life Cycle Management), the custom themes are managed together with all other elements (logical data model, data load processes, dashboards, and so on) within your LCM setup.

This is how it works:

  1. You define custom themes and upload them to the master workspace for a segment (see Create Custom Themes).
  2. You run the Rollout brick (see Rollout Brick) that synchronizes all the client workspaces in the synchronized segments with the latest version of the segment's master workspace.

    If you are at the beginning of setting up LCM at your site, this would be done by the Provisioning brick (see Provisioning Brick), which performs the initial synchronization between the master workspace and the client workspaces.

  3. You activate a theme in the client workspaces (see Create Custom Themes).

    You can simultaneously activate a theme for multiple client workspaces with the same authorization token (so-called "project group") rather than activating it in each client workspace separately. To do so, go to //{authorization_token}/config/.

    To find the authorization token, see Find the Workspace Authorization Token.

    Platform settings configured at the project group level are inherited by the underlying workspaces (including those that may be created using the same authorization token in the future). To configure a platform setting for a project group, you must be a domain admin.

  4. When you need to update the custom themes in the client workspaces, update the themes in the segment's master workspace and run the Rollout brick to propagate the updated themes to the client workspaces.
Powered by Atlassian Confluence and Scroll Viewport.