BCS Service SDK
BcsService 3.6.x for BCS 6.x
Component | Version |
---|---|
BcsService.exe | 3.6.384.0 |
Dependencies
BcsService 3.6.x isn't compatible with BCS 5.x
Component | Min. Version |
---|---|
BCS | 6.0.417.0 |
Audio32.dll | 2.12.221.0 (as minimum, part of release 2019.2) |
DigaSQL | 3.14.3466.0 |
EndPoints.dll | 1.0.8.0 |
BcsHelpers.dll | 1.0.24.0 |
RtfQuillDeltaConverter.dll | 1.0.57.0 |
.NET | 4.8 |
Known issues
- If client locked BCS node and then unexpected terminated (e.g. killed in Task Manager) locked node will be unlocked only after client connection inactivity timeout is exceeded
New features
- GetConsistencyCheckResults request
- GetDayTemplates request
- GetConsistencyCheckResults request supports more parameters
- GetShowTemplates request
- GetPreproductions request
- GetJingles request
- PutMoveBlock request
- PostDatabaseObject request support show & day templates
- PostNode request support new parameters nodeIdIsNext, insertBlock, checkOnly, noShortLockWait
- PutNode request support new parameters useOnlySpecifiedDataInRoot, moveTrackToSnapshot, noShortLockWait
- GetPrograms request support parameter to provide only accessible BCS programs
- MoveNode and CopyNode requests insert and moved nodes after the target node by default for backwards compatibility
- GetNode request supports fields list & transactionId parameters
- Authorization with AccessToken for GetPrelistenFile, GetWaveFormFile, GetFile and GetThumbnail requests
- Support transactionId in delete notification if node was deleted from another BCS Service client
- Always generate unique connection identifier for compatibility with BCS WebSocket API
- Send client connection identifier in lock & unlock notifications if lock & unlock was initiated from another client
- Send multilock notification in the same format as all other notifications
- Calculate loudness state for metadata from BCS notifications. Warning! Using this feature can be very unperformable by slow hardware
- Support transaction identifiers in node notification requests
- XML -> JSON conversion is compatible with Consistency Check Task format
- Support Ping-Pong mechanism for WebSocket connections
- Active scan WebSocket clients to identify dead connections
- Human-readable error message if BCS 6.x has WebSocket implementation incompatible with .NET WebSocket client
- Global error list with human-readable error messages
- Move log of periodic request for access to internal structures from debug to trace log level
- Separate handling out of memory workflow
- Detailed information about allocated file handling tasks
- Detailed information about allocated connections from client
- New call log system based on external automatic logger "Calls Logger"
- Information about adding/removing file handling tasks in cache in debug log
- Information about connections cache & identifiers cache
- Memory consumption watcher
Fixed Issues
- SGU-5033: Properly handle OIDC connection request if the user matched to OIDC token was already logged
- SGU-5033: Send notifications to clients via internal queue to prevent stopping receiving BCS notifications while loudness calculation
- SGU-5268: Send notifications to clients if notification was initiated on higher level as notified node only with affected BCS metadata
- SGU-5469: Remove end '/' character from parent node id in InsertNode notification if node was inserted as a first child
- Add default values to DeleteNodeNotification request
- Properly handle WebSocket commands with data in XML format
- SGU-5555: Properly formatted root tag in JSON format
- SGU-5617: Don't require isParent parameter as mandatory in PostNode request if the parameter nodeIdIsNext is specified
- SGU-5617: Properly handling CheckOnly parameter in PostNode request
- OIA-1026: Allow to copy nodes into Jingles, DayTemplates, ShowTemplates, Preproductions
- SGU-5471: Return HTTP error codes matched to internal BCS errors
- SGU-4672: More clear error messages
- Human-readable error message by invalid ContentType header
- No unnecessary day initialization when reading special locations in BCS program
- SGU-5546: Handle delayed DigaSQL initialization by slow workstations
- More debug information about detected BCS programs
BcsService 3.5.x BCS v5.x
Component | Version |
---|---|
BcsService.exe | 3.5.342.12 |
Dependencies
BcsService 3.5.x is compatible with the BCS 6.x. but only with x32 version and if the BCS is configured to use the old communication method
Component | Min. Version |
---|---|
BCS | 5.9.381.1 |
Audio32.dll | 2.12.221.0 (as minimum, part of release 2019.2) |
DigaSQL | 3.14.3466.0 |
IBCS.dll | 4.0.125.0 |
EndPoints.dll | 1.0.8.0 |
BcsHelpers.dll | 1.0.24.0 |
RtfQuillDeltaConverter.dll | 1.0.57.0 |
.NET | 4.8 |
Known issues
- If client locked BCS node and then unexpected terminated (e.g. killed in Task Manager) locked node will be unlocked only after client connection inactivity timeout is exceeded