Service notice card

The screen shows the service, its status, the time to go, the schedule and the impact in one glance, clear from across a room. It fills the screen, fits any rectangle, sits in the middle, tucks into a corner, runs as one line in a corner or runs as a band along an edge. You set the service, the detail, the impact, the alternative and the contact.

Live card

This card is drawn in your browser by the same code the Players run, with sample data.

Category: Messages. Tags: Offices and workplaces, Lobbies and reception, Alerts and status, Schedules.

Layouts

This core card fits every layout: full screen, center, corner, chip, strip, or any free rectangle.

Layouts: full, free, center, corner, chip, strip. Forms: landscape, portrait.

Card layouts, themes and publishing. Browse the cards.

Data and privacy

This card uses its configured properties and live card data.

Properties

For theme, background, accent and position, see Common properties.

Set static properties in params. Bind data to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in params. Nested rows describe the contents of their parent property.

Static properties

Name	Type	Default	Values and limits	Description
`hourCycle`	string	`"24"`	`"12"`, `"24"`, `"military"`	The clock times of the schedule: 12: 2:05 PM. 24: 14:05. military: 1405 with HRS.
`presence`	string	`"window"`	`"window"`, `"always"`	window: absent until leadMinutes before startsAt, and gone lingerMinutes after the work is marked complete or cancelled (an unconfirmed end keeps the notice up). always: shown at all times.
`leadMinutes`	integer	`60`	minimum: `0`; maximum: `10080`	With presence window, how many minutes before startsAt the notice appears.
`lingerMinutes`	integer	`15`	minimum: `0`; maximum: `10080`	With presence window, how many minutes the notice stays after the work is marked complete or cancelled.
`tone`	string	`"auto"`	`"auto"`, `"cool"`, `"warm"`, `"danger"`, `"success"`, `"muted"`	auto: cool before the work, warm during it and past its planned end, success when complete, muted when cancelled.

Dynamic properties

Name	Type	Default	Values and limits	Description
`title`	string	`"Planned maintenance"`	maxLength: `120`
`service`	string	`""`	maxLength: `80`
`detail`	string	`""`	maxLength: `600`
`impact`	string	`""`	maxLength: `160`
`alternative`	string	`""`	maxLength: `160`
`contact`	string	`""`	maxLength: `120`
`startsAt`	string	`""`	maxLength: `40`
`endsAt`	string	`""`	maxLength: `40`
`updatedAt`	string	`""`	maxLength: `40`
`status`	string	`"auto"`	`"auto"`, `"complete"`, `"cancelled"`	Complete is an explicit confirmation; the end of the planned window alone does not confirm restoration.

Canvas example

Add this item to a playlist page’s primitives. Publish the playlist and assign a screen.

{
  "id": "service-notice",
  "primitive": "card",
  "card": "service-notice",
  "major": 1,
  "params": {
    "theme": "neomustard"
  },
  "rect": {
    "x": 0,
    "y": 0,
    "width": 1920,
    "height": 1080
  },
  "layer": 0,
  "content_fit": "fill",
  "data": "example-key"
}

Write live data

The canvas example binds its data field to example-key. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with feed:.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as card-data.json. The CLI reads the document itself, with no wrapper:

{
  "title": "Planned maintenance",
  "service": "",
  "detail": "",
  "impact": "",
  "alternative": "",
  "contact": "",
  "startsAt": "",
  "endsAt": "",
  "updatedAt": "",
  "status": "auto"
}

screenrig card-data put example-key --file card-data.json

Or call the API directly. The API wraps the same document in a document field. An agent token already names its project, so no project header is sent; if you send ScreenRig-Project, it must match the token’s project. Supply your API authorization through the environment; see API authentication.

curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"title":"Planned maintenance","service":"","detail":"","impact":"","alternative":"","contact":"","startsAt":"","endsAt":"","updatedAt":"","status":"auto"}}'