Ooyala Flex Media Platform 7.2.1 Release Notes 2018-11-16

Highlights

Ooyala is excited to present the release of Ooyala Flex Media Platform 7.2.1. This release of Ooyala Flex Media Platform provides the new features and enhancements, fixes, and other changes listed below.

New Features and Enhancements

Review - Option to set a review priority in Review

We have added the ability to set a priority against a review session. This allows for:

* a workflow to indicate the priority of content review to a user. The value is available on the API/SDK for a workflow to query to make certain business decisions.
* a user to sort by the more important reviews in their queue and action them accordingly.

A priority can be set against any given review session; in addition, an active review session can be updated.

* A default priority is set if no priority has been identified.

Related changes in the FLEX Core API

We have introduced the following changes to the ``/assets/{assetId}/reviews`` and ``/assets/{assetId}/reviews/{reviewId}`` REST API endpoints:

* ``GET: /api/assets/{assetId}/reviews`` - retrieves the list of reviews for a current asset where all the reviews returned in the response now contain a new <span class="ph uicontrol">PRIORITY</span> field. Sorting and filtering by <span class="ph uicontrol">PRIORITY</span> (accepted values ``1`` to ``5``) is supported through the ``sortBy`` attribute - for example, ``sortBy=PRIORITY``.
* ``GET: /api/assets/{assetId}/reviews/{reviewId}`` - same as above but returns a response for a specific review.
* ``PUT: /api/assets/{assetId}/reviews/{reviewId}`` - this is a new method that allows you to update the priority of a review session. Only the review session initiator or a user with the correct role permissions is allowed to update the priority of a review session. An example API request for this method follows:

  {

  "type": "object",

  "required": true,

  "properties": {

  "priority": {

  "type": "number",

  "minimum": 1,

  "maximum": 5,

  "required": true

  }

  }

  }

MAM - Children Download

From the Manage page in MAM, you can now download the children of the current asset. You can only download assets if you have access.

Publish

New internal API endpoint to rebuild asset hierarchy in FLEX Publish

We have added a new endpoint to rebuild the hierarchy of a given asset, without having to republish the asset.

The new endpoint is internal and uses the ``PUT`` method, as follows: ``PUT /api/assets/hierarchy/{assetId}?token=<token>``

A successful request returns a ``204`` status code.

FLEX Publish API updated to return external IDs for UDOs

External IDs are now returned, and searchable, as part of the UDO details in the FLEX Publish API responses.

An example follows:

Request:

  <publish_url>/public/api/<object_name>/<object_id>?token=<publish_token>

Response:

  {

  "type":"PublishUdo",

  "id":166621,

  "accountId":10101,

  "title":"New Season",

  "description":"",

  "pluralName":"Seasons",

  "createdDate":"15-10-2018 21:17:14",

  "lastModified":"16-10-2018 21:57:23",

  "publishedDate":"16-10-2018 16:05:41",

  "children":[

  ],

  "tags":[

  ],

  "metadata":{

  }

  }

Resolved Issues

* File Instantly Failing in Web Transfer

Issue: File upload failed when the filename contained a “+”. The problem affected the ``Web Transfer`` service.

Resolution: The issue has been fixed.

* Getting a Null Pointer Exception when no authorisation header is used for Enterprise API

Issue: When a request was made with no authorisation header, a null pointer exception was displayed with status 500.

Resolution: The correct error, ``401 Unauthorised``, is now displayed.

* Job remains in "Running" state after deleting/stopping from Vidchecker Task Monitor

Issue: After a job was deleted, or stopped, from the Vidchecker TaskMonitor, the job remained in a “Running” state.

Resolution: Deleted or stopped jobs are now failed.

* After Purge File Only, keyframe still not deleted

Issue: When an asset was purged with the action "purge file only", the asset remained in the system, but the associated <span class="ph filepath">assetDetails</span> object was removed. However, the system was only removing keyframes when <span class="ph filepath">assetDetails</span> existed.

Resolution: Keyframes are now deleted from their physical location.

* Cache not being evicted when publishing with JEF

Issue: The cache was not being cleared for an asset when it was published with JEF.

Resolution: Cache is now cleared.

* In read only mode, a user can delete the comments written by a locked or current user

Issue: In read only mode, comments could be deleted.

Resolution: Comments can no longer be deleted in read only mode.

* ``publishedDate`` of sub-collection disappears from publish API call after republishing collection hierarchy**

Issue: The ``publishedDate`` was being neither set nor copied from the published collection on republish.

Resolution: We now set a new publish date if the collection was never published, or we copy the one that was in the published collection.

* Relationship of asset's children is not implemented

Issue: A publish API call did not display any published children of the asset.

Resolution: All published children of the asset are now displayed.

* API allows the status of an essence to be changed after the review of the asset is completed

Issue: The API did not block changes to the status of an essence, even after the review of the asset had been completed.

Resolution: Once the review is completed, the status of reviewed essences can no longer be changed.

* Publish Player fails when keyframes are published with asset

Issue: When keyframes were published with an asset, the Player Publish action was failing with an error.

Resolution: Keyframes can now be published successfully with an asset.

* Unapproved keyframe gets published

Issue: Keyframes were published even when they are not set as “approved” in Flex Publish REST calls.

Resolution: Unapproved keyframes are no longer published.

* Validation message does not display when user creates UDOT with name with capital letters via Rest API POST call

Issue: A validation message should be displayed when user tries to create a UDOT with capital letters in the name field. However, this message was not displayed.

Resolution: A validation message now displays when the name is given other than as lower case letters and hyphens.

* Hibernate exception when opening review sessions

Issue: When review sessions were opened, an error was generated.

Resolution: Opening a review session no longer causes an error to be displayed.

* Exclusive review message/notification not showing up for Image assets

Issue: When an exclusive review was started, no notification was displayed to indicate that the asset was only accessible to the reviewer. Nor was a notification displayed to other users that the asset was read-only.

Resolution: The correct notifications are now displayed.

* When import job fails, not all partial imported entities deleted

Issue: When an import job failed, some partial imported entities remained, which led to an error when the job was retried.

Resolution: Partial imported entities are now fully imported when the job is retried, which means that the job starts at the same point at which it failed before.

* Toggle task summary

Issue: Ooyala Flex loads all task instances from the database to calculate the task summary, which is a drain on memory.

Resolution: A new feature toggle has been added, which allows you to remove the task summary panel from task dashboard to save memory. In a future release, we intend to improve the Task Summary to be more efficient, so that this feature toggle becomes unnecessary.

* Metadata Designer:
* Variable renaming functionality is not working correctly from the canvas.

Issue: Variables could not be renamed in Metadata Designer.

Resolution: Variables can now be renamed.

* The backing store filter field value of a tag variable is deleted.

Issue: Sometimes, the backing store filter field value of a tag variable was deleted when clicking on another variable.

Resolution: The issue no longer occurs.

Known Issues

* Safari does not refresh the encryption key when the Flex access token expires.

When AES encryption is enabled for segmented assets, the flex_access_token is used to carry the generated key used to encrypt the segment files. In the HLS manifest, each segment has a different key URI that the player uses to extract the AES key from the token as the segment is being loaded.

This works on all browsers (Chrome, Firefox, Edge), except for Safari, which requests all the keys at once and caches them (all other browsers request the key as the segments are loaded). When the token expires and the key changes, Safari still tries to decrypt the segments with the old key.

* File transfers using File Catalyst might fail.

A file transfer might fail when it is attempted using File Catalyst - for example, from a local File Catalyst instance to a remote/server one.

Please contact your Ooyala representative for the full upgrade notes, further information about this release, and the complete list of resolved issues.