Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Overview

You must migrate to the 2022/06 bsn.cloud APIs if you want to use any of the Series 5 players (except the AU335, which is supported in bsn.cloud 2020/10 APIs). In previous versions, these players will show up as "unknown" and new video walls, 8K images and other Series 5 related features are not supported. See https://www.brightsign.biz/brightsign-players/series-5/ for more information about Series 5 players.

Series 5 Changes

The 2022/06 API supports BrightSign Series 5 players with the following changes:

Business Operations Appliance Changes

In previous API versions, the business operations listed also included non-applicable operations. We addressed this usability bug by providing new information in the OperationAppliance property as shown below:

  • Business Operations Entity (2022/06)  was extended by the [OperationAppliance] Appliance property.
  • The OperationAppliance enumeration was defined. It may have one or more unique { "Instance", "Collection", "Unknown" } values:
    • The "Instance" value indicates that the given business operation applies to specific entity instances.
    • The "Collection" value indicates that the given business operation applies to collections of entities in a network and associated folders.

Please update your client and display as follows:

  • Where you define instance-specific permissions, display only BusinessOperations which have "Instance" values. In BrightAuthor:connected, this would be in entity properties panels such as Content, where you can define object permissions for specific instances.
  • Where you define permissions or collections of entities, display only the BusinessOperations which have "Collection" values. In BrightAuthor:connected, this would be in Admin > Roles & Permissions, where you create custom roles and define player permissions.

HTTP Conditional Request Support

Most of our entities already support conditional requests according to rfc7232, but conditional request were missing for the following three entities and have now been implemented:

Network Settings Structure Fixes

We provided new information in some entities (LastModifiedDate and AutomaticSubscriptionsManagementEnabled), which can be implemented if you wish. Other minor fixes have also been implemented:

  • Network Entity (2022/06) was extended by the [DateTime] LastModifiedDate property
  • Network Settings Entity (2022/06);
    • The [bool] AutomaticSubscriptionsManagementEnabled property has been added to the structure.
    • The [bool] AutomaticTaggedPlaylistApprovementEnabled property has been renamed to AutomaticTaggedPlaylistApprovalEnabled.
  • Network Subscription Entity (2022/06):
    • The [DateTime] LastModifiedDate property is no longer nullable.
    • The GET ~/2022/06/REST/Self/Networks/{networkId}/Subscription/ and GET ~/2022/06/REST/Self/Networks/{networkId}/Subscription/methods set the Last-Modified HTTP response header to the [DateTime] LastModifiedDate property value of the returned entity.
    • The PUT ~/2022/06/REST/Self/Networks/{networkId}/Subscription/ and PUT ~/2022/06/REST/Self/Networks/{networkId}/Subscription/methods accept the optional If-Unmodified-Since HTTP Request Header and evaluate condition against the target entity.
  • Player Subscription Entity (2022/06) was extended by the [DateTime]LastModifiedDate property.

ON THIS PAGE








  • No labels