Cisco Cisco StadiumVision Director
© 2010-2011 Cisco Systems, Inc. All rights reserved.
Page 6 of 47
-
The Cisco StadiumVision Director user interface now allows users to delete
unwanted proof of play data.
•
Content Staging Enhancements
The content staging interval is now configurable. The registery value
"staging.interval" is set to 24 hours by default. You can change the interval using
the Management Dashboard. To extend this value to beyond 7 days, you must
also increase the "script.keepScriptInstancesDuration" registry value to more
than the default value of 7 days. For example, to set the content staging interval
to 14 days, update the "staging.interval" value to "336" hours and also increase
the "script.keepScriptInstancesDuration" to "14" days.
"staging.interval" is set to 24 hours by default. You can change the interval using
the Management Dashboard. To extend this value to beyond 7 days, you must
also increase the "script.keepScriptInstancesDuration" registry value to more
than the default value of 7 days. For example, to set the content staging interval
to 14 days, update the "staging.interval" value to "336" hours and also increase
the "script.keepScriptInstancesDuration" to "14" days.
•
PoS Demo Capability
To allow account teams and partners to demonstrate the PoS and commerce
features of Cisco StadiumVision, you can now cache information from a “live”
PoS implementation (such as Quest or Micros) for use in a stand-alone
demonstration. The data can be used to illustrate the in-suite ordering
capabilities of Cisco StadiumVision, but cannot be used to actually generate an
order.
features of Cisco StadiumVision, you can now cache information from a “live”
PoS implementation (such as Quest or Micros) for use in a stand-alone
demonstration. The data can be used to illustrate the in-suite ordering
capabilities of Cisco StadiumVision, but cannot be used to actually generate an
order.
•
Dynamic Content Replacement
During an event, you can now replace content in an event script with other
content. The “new” content must exist elsewhere in the event script (as the
content must be prepositioned on the DMP.
content. The “new” content must exist elsewhere in the event script (as the
content must be prepositioned on the DMP.
Note: You cannot replace content in an event script with other content that does
not already exist on the DMP to an event script. Nor can you add new content to
an event script during an event.
not already exist on the DMP to an event script. Nor can you add new content to
an event script during an event.
Proof of play support has also been updated to support the dynamic
replacement of content.
replacement of content.
•
Renamed Templates and Actions
To address a potential problem regarding duplicate template names. the action
names for default templates of the form Set L-Wrapper have now been
converted to be consistent with the action names for user-defined templates,
which is Set template-name. Below shows the mapping between previous and
new names:
names for default templates of the form Set L-Wrapper have now been
converted to be consistent with the action names for user-defined templates,
which is Set template-name. Below shows the mapping between previous and
new names:
Old Action Name
New Action Name
Set L-Wrapper
Set 3-REGION-1366x768
Set Full Screen Video
Set FULLSCREEN-1366x768
Set Full Screen Message
Set 3-REGION-SINGLE-1366x768
Set Single Height L-Wrapper
Set 3-REGION-DOUBLE-1366x768
Set Double Height L-Wrapper
Set MESSAGING-1366x768