Email Addresses with .media Domain
If Users tried to create a new Ooyala Flex User with an email address that contained a .media domain, then Ooyala Flex would reject the email address. This has been fixed, and now email addresses with the aforementioned domain are accepted.
Add to Group Action
The Add To Group Action was acquiring locks on source and target Assets. We have made changes to the Add to Group command, so that it no longer considers the state of the lock for any member Assets in a Group.
Script Action Waits for a Lock Indefinitely
Script Actions were waiting for a Lock indefinitely. To solve this problem, we have made changes to the locking behaviour for certain Action plugins. These changes can be viewed below, in the What’s New section.
API: Workflow Definitions
The /workflowDefinitions (GET) endpoint was not returning correctly. Certain fields were not being mapped in responses, including the “objectType” and “latestVersion” fields. To correct this problem, we have added an override method to decide the entity in the Workflow Definition query.
If an Object in a hierarchy was deleted, it would still hold a Child/Parent relationship, even though it had been deleted.
To resolve this, we will no longer display the Delete button in the UI, if a parent Object type is associated with any Child Object type. From now on, you must remove any child Objects from a hierarchy, prior to deleting the parent Object type.
To find out more about Object Hierarchies, please visit the Objects section: http://help.ooyala.com/media-logistics/flex/user/53/objects.html
YouTube HTTP V3 Publish and Unpublish Actions
New Publish and Unpublish Actions have been created for the YouTube V3 API. These are:
To use the publish plugin you will need to generate OAuth credentials using Google’s API Manager, by entering the specific Callback URL you wish to use, followed by the port that Ooyala has specified. You can then download the OAuth details from Google in the form of a JSON file, and upload it to Ooyala Flex.
Note: These plugins have been created because Google has terminated their V2 APIs. This means that the V2 version of these plugins no longer work.
YouTube V3 Configuration Changes
In V3, we have implemented some configuration changes. We have streamlined the configuration process for the YouTube HTTP V3 Publish plugin, by removing the Port and Credentials Directory fields that were found in previous versions of the YouTube Publish Plugins.
Now, Instead of specifying the port and credentials directory in seperate fields in the Configuration section, you can specify these details in the Google API manager, when you go to obtain your OAuth credentials. Then, you can simply download the OAuth credentials as a JSON file and upload it in the OAuth JSON File field.
For more information about creating OAuth credentials, please consult the Publish to YouTube HTTP V3 documentation.
Enhancements to the Backlot HTTP Publish Plugin
We have made enhancements to the Backlot HTTP Publish plugin. These are as follows
Backlot HTTP Unpublish Action
A Backlot HTTP Unpublish Action has been added. This Action enables you to unpublish an Asset that you have published to Backlot. This Action relates to the Backlot HTTP Publish Action, and the HTTP Backlot Republish Action.
Note: This plugin falls under the “Unpublish” category.
Note: To Unpublish an Asset that you have previously published using the Backlot HTTP Publish Action, you must create and then select a Backlot HTTP Unpublish Action, when setting up the Backlot HTTP Publish.
Backlot HTTP Republish Action
A Backlot HTTP Republish Action has been created. This enables you to republish an Asset to Backlot, that you have previously unpublished. This Action relates to the Backlot HTTP Unpublish, and Backlot HTTP Publish Actions
**Note:**This plugin falls under the “Republish” category.
Note: To Republish an Asset that you have previously published using the Backlot HTTP Publish Action, you must create and then select a Backlot HTTP Republish Action, when setting up the Backlot HTTP Publish.
Ability to Disable or Change Locking for Specific Actions
We came across a problem, in which Script Actions were waiting for a Lock indefinitely. To solve this problem, we have made changes to the locking behaviour for certain Action plugins. From 5.3.2 onwards, the default locking behaviour can either be disabled or overridden in the Configuration section, for the following Actions:
Users can specify what type of lock is required for the above Action plugins. There are three locking options that Users can specify. These are as follows:
Note: If Users don’t make any changes to the locking behaviour for the above Actions, the default behavior will remain in place.
All Services Now Use the Resource Library for Redis Connections
All services that use Redis, now have their connections managed via the Resource Services library.
The following services have been updated to use the Resource library for their Redis connection: