Skip to main content

Asset Blocks

Asset blocks are reusable ordered groups of assets. Use them when several assets should stay together as a unit instead of being scheduled one by one.

When To Use Asset Blocks​

Use an asset block when you need:

  • a fixed sequence of assets that should be reused repeatedly
  • a grouped programming package for multiple events or screens
  • a simpler scheduling workflow than adding the same set of assets repeatedly

Use a normal Asset when you only need one item.

What An Asset Block Does​

An asset block stores:

  • a name
  • an ordered list of assets
  • optional extension-backed metadata depending on the deployment

When the asset block is used in an event sequence, the block behaves as one scheduled item that expands into its internal asset order during playback logic.

Creating An Asset Block​

To create an asset block:

  1. open the Asset Blocks area
  2. use Create Asset Block
  3. give the block a clear name
  4. add the assets that belong in the group
  5. save the block

Choose names that describe the grouped purpose, not just the first asset inside the block.

Asset Block Editor Stub screenshot: Asset Block editor with a named block and several ordered assets visible. Save final image at packages/docs/screenshots/app-asset-block-editor.png.

Adding Assets To A Block​

After creating the block, add assets from the asset picker.

This lets you build a reusable content package from assets that already exist in the library.

Typical use cases include:

  • a short branded sequence
  • a client-specific ad package
  • a repeated information loop
  • a grouped set of assets that always travel together operationally

Ordering Behavior​

The order inside the asset block matters.

  • assets are arranged in a specific sequence
  • operators can reorder them
  • the block preserves that order when used in scheduling workflows

The current UI also supports asset-level actions within a block, including:

  • removing an asset from the block
  • duplicating an asset inside the block
  • opening the underlying asset details
note

Deleting an asset block does not delete the individual assets stored in SVRunner.

Viewing And Expanding Asset Blocks​

In list-style UI views, asset blocks can be expanded to show the assets inside them.

This is useful when operators need to confirm the contents of a block without navigating away from the current workflow.

Expanded Asset Block Stub screenshot: expanded asset block in a list view showing the contained assets. Save final image at packages/docs/screenshots/app-asset-block-expanded-list.png.

Asset Blocks In Events​

Asset blocks are commonly added to event sequences alongside normal assets.

This is useful because operators can schedule a whole pre-arranged content package as one item instead of rebuilding the sequence each time.

When asset blocks are used in events, their behavior is affected by the event's scheduling logic, especially:

  • occurrence type
  • sequence behavior
  • loop behavior
  • whether block rotation is enabled

Sequence Behavior And Scheduling​

Asset blocks participate in the same event sequence rules described on the Events page.

That means the event's sequence behavior can affect how the block contributes to the generated playlist when using:

  • Percent Share
  • Play Count
  • Loop-related workflows

Operators do not need to memorize the playlist internals, but they should understand that asset blocks are not immune to the surrounding event logic.

Rotate Asset Blocks In Loop Events​

Loop events include a Rotate Asset Blocks option.

When used, this changes how asset blocks are cycled over repeated loop use. This is especially useful when:

  • the same asset block is used repeatedly in a looping context
  • the installation wants variety across repeated passes
  • operators need a grouped content package without always starting from the same item

If exact repeat order matters on every loop pass, validate whether rotation should remain disabled.

Extensions​

Some deployments use extensions on asset blocks.

This can add:

  • custom metadata
  • validation
  • project-specific workflow fields

If your installation relies on extension-backed asset blocks, document the specific schema expectations for operators.

See Extensions.

Common Mistakes​

  • using an asset block where a single asset would be simpler
  • forgetting to verify the internal order before scheduling the block
  • assuming changes to the asset block only affect one event when the block is actually reused widely
  • enabling loop rotation without understanding its operational effect