Refer to the exhibit. A macro and a UI extension (also called In-Room Control) are being developed. What is the reason for the error displayed in the console?

Question

Exhibit

Options

• AWidgets of type "Slider" are not supported on the device.
• BThe UI extension was not exported to the device.
• CThe name of the widget in the macro and the UI extension must match.
• DPromises are not supported for this device.

• A
  3% (1)
• B
  90% (35)
• C
  5% (2)
• D
  3% (1)

Explanation

Option B is correct because a UI extension must be exported (deployed) to the device before any macro can interact with its widgets. When the UI extension exists only in the editor but hasn't been pushed to the device, the macro's attempt to reference those widgets fails - the device has no record of them, producing the console error.

Why the distractors are wrong:

• A is incorrect - Slider widgets are a fully supported standard widget type in Cisco RoomOS UI extensions; there is no platform restriction on them.
• C is incorrect - while widget ID names in the macro do need to match the UI extension, a name mismatch produces a different kind of error (widget not found by ID), and would only matter after the extension is already on the device.
• D is incorrect - the RoomOS macro environment is JavaScript-based and supports Promises natively; this is not a platform limitation.

Memory tip: Think "deploy before you develop against it." The macro talks to the device, not the editor - if the UI extension never left the editor, the device is blind to every widget in it, and any macro referencing them will immediately error out.

No community discussion yet for this question.