Many changes have been made to Ooyala Flex in relation to the 5.3.0 release. In these release notes, you will be provided with a detailed overview of each of these changes. These changes include: the introduction of MAM, a new micro service based architecture, removal of the Java Applet applications and the addition of their HTML5 equivalents, further integrations with third-party applications, an upgraded Configuration Manager, and new REST Endpoints. These additions to Ooyala Flex in the 5.3.0 release, will extend the functionality, improve various areas of the product, and make it easier to use.
Core
Modules
User defined objects are not displayed on Web Transfer
Architecture
The architecture for 5.3.0 has changed, and now utilizes a micro-service based approach. This micro-service approach means:
An Overview of each Service:
Applications
This is displayed within the console as the specified display name and respective values.
For further information on the Metadata Designer, please consult the 5.3 seires Metadata Designer Guide
For more information regarding the Workflow Designer, please consult the 5.3.0 Workflow Designer guide.
This should return the display value of the variable: 10:00:00:00@25. When accessing the variable via the new Groovy Scripting SDK: The field can be accessed (e.g. getValue(), setValue()) by passing in the display value (hh:mm:ss:ff@fr).
A new field has been added to the Transcode plugins, which reads the transcode profile as JSON. This is available in the following Action Plugins:
When setting the tv.nativ.mio.enterprise.script.classloader.reset system property to “true”, the class loader will always be reset when executing any script from that point onwards.
Note:This should be set back to “false” after it is cleared.
A new field has been added to the Transcode plugins configuration section, which reads the transcode profile as JSON. This is available in the following Action Plugins:
Ooyala Flex now supports External IDs. The support for external IDs has been introduced in the following areas:
**Note:**You can also edit the key value pairs for external IDs, by clicking the Edit option, located in the top-right of the summary panel.
REST API: In the REST API, you can: Add, view, edit, and delete existing Objects resources e.g. /objects/123456; You can retrieve a specific Object via an external ID. For example: /objects;vindiciaId=123; and accessible for reading on the specific entity resource e.g. /assets/123456/workflows/234567.
Search: You can search for existing external IDs in the Ooyala Flex console UI. The following examples of queries can be performed:“amazonObjectId:xyz-123”, “123”
Per-Account Configuration and Constraints: There are several rules that need to be followed when creating external IDs. An external ID value cannot be empty and cannot contain spaces. An external ID key cannot be used if the same key already exists for the same Ooyala Flex Object.
If the account of the Ooyala Flex Object has a property defined called {{tv.nativ.mio.externalid.keys}} it is expected this will be a comma separated list of valid external ID keys. If this property is defined, then an external ID key must be in this list for it to be valid.
Note: If the {{tv.nativ.mio.externalid.keys}} property is modified after external IDs have already been set on Objects, any invalid external IDs will remain on the Objects. However, when attempting to modify/edit the external IDs on an Object instance, the invalid ones will need to be removed.
Note: The Account configuration should be taken from the Account that the Object belongs to, and not the Account of the User accessing the Object.
Note: When you upgrade to 5.3.0, any existing external references will be converted into external IDs. Example: “externalReference”: “3431”
Ooyala Flex has integrated with FileCatalyst, providing accelerated Asset uploads alongside the web uploader. In order to make use of this integration, you will need to have FileCatalyst credentials.
There are a number of prerequisites that you must take into account, if you intend to use the FileCatalyst Uploader. These are as follows:
Please consult the 5.3.0 FileCatalyst Integration guide for further information.
FileCatalyst Limitations
Managing the storage and life cycle of your Assets is now much easier, as Ooyala Flex has integrated with DIVArchive, via the creation of three new DIVArchive Action plugins. These plugins give you the ability to archive your Assets, delete them from archive, and restore them back to the configured storage.
The DIVArchive integration includes the introduction of the following new Action plugins:
Note: Despite the fact that the DIVArchive plugin falls under the “Archive” category, the DIVArchive Action is distinctly different and therefore unrelated to the standard Ooyala Flex Archive Action.
DIVArchive Limitations
You can archive child assets separately from their parent. This comes with a limitation. If you want to restore a child Asset, you can only do this in one of two ways:
Note: You cannot restore a child Asset via its parent. You must go directly to that particular child Asset, and then carry out the restore.
Content-Type Header for GET Requests
You no longer need to specify the Content-Type header (application/vnd.nativ.mio.v1+json) when performing GET Requests in the 5.3 series.
External ID Endpoints
New REST API endpoints have been added to the Core REST API for 5.3.0. Some of these endpoints specifically support MAM functionality, and some of these are solely related to Core. Below, you can see the endpoints that have been created, along with the requests that can be made for each one:
The following endpoints relating to External IDs have been added for all Object Types throughout Ooyala Flex, including User Defined Object Types.
Example: In the REST API, the following GET request could be made. This GET request would provide you with the external ID for a specific Group.
/groups/{groupId}/externalIds/{key}
Table 1. External ID Endpoints
Resource | Endpoint | Method |
---|---|---|
External IDs: | /externalIds | Get / Post |
External IDs: | /externalIds/{key} | Get / Put / Delete |
Copy Endpoints
A copy endpoint has been added for all Object Types throughout Ooyala Flex.
The following endpoint enables you to copy an Object via the REST API.
The only two fields that must be filled in when copying an Object via the REST API are as follows:
Table 2. Copy Endpoints
Resource | Endpoint | Method |
---|---|---|
All Object Types: e.g. Assets, Metadata Definitions, Workflow Definitions… | /copy | Post |
Asset Endpoints
There are a number of endpoints that have been added in the REST API, which relate to the newly introduced MAM application. This includes REST API endpoints relating to Assets, Collections, Wizards, and Object Types.
Table 3. Asset Endpoints
Resource | Endpoint | Method |
---|---|---|
Assets: | /mediaRegion | Get / Post / Put |
Assets: | /placedMediaRegions | Get / Post |
Assets: | /{placedMediaRegionId} G | et / Put |
Assets: | /{assetId}/proxies | Get |
Assets: | /assets/{assetId}/keyframes/{keyframeId} | Get / Put /Post / Delete |
Collections: | /collections | Get / Post |
Collections: | /collections/{collectionId} | Get / Put / Delete |
Collections: | /collections/{collectionId}/items | Put / Get |
Collections: | /collections/{collectionId}/comments | Get / Post |
Collections: | /collections/{collectionId}/comments/{commentId} | Get / Put / Delete |
Collections: | /collections/{collectionId}/followers | Get |
Collections: | /collections/{collectionId}/attachments | Get / Post |
Collections: | /collections/{collectionId}/attachments/{attachmentId} | Get / Put |
Collections: | /collections/{collectionId}history | Get |
Collections: | /collections/{collectionId}/references | Get |
Collections: | /collections/{collectionId}/metadata/{variableInstanceId}/comments | Get / Post |
Collections: | /collections/{collectionId}/subCollections | Get |
Collections: | /collections/{collectionId}/keyframe | Post / Put / Delete |
Wizards: | /wizards/instances | Get |
Wizards: | /objects/{id}/wizards/instances | Get |
ObjectTypes: | /objectTypes/objects | Get |
ObjectTypes: | /objectTypes/user | Get |
ObjectTypes: | /objectTypes/asset | Get |
MAM is a user-centric Media Asset Management application which is powered by the Core module. The interface is focused on just the functionality that a user requires, this includes secure search, management, metadata update, and clipping and rough-cut editing on your assets directly from your web browser.
MAM enables you to do the following:
Known Issues for MAM
Limitations for MAM
For proxy recommendations and more information relating to MAM, please consult the MAM Guide
The interface for the Reviewer application has been completely redesigned. So that is it sleeker, easier to use, and more visually appealing.
Reviewer is an application that enables you to quickly and securely review, approve, and submit time-coded comments against your uploaded Assets anywhere, at any time, as long as you are connected to the internet.
The new Reviewer UI comes with the following improvements:
For more information on Reviewer please consult the Reviewer 2.0 Guide
Limitations for Reviewer 2.0
Ooyala Flex Configuration Manager is a stand alone tool which helps you remotely configure Ooyala Flex environments. An Ooyala Flex environment is a running instance of Ooyala Flex e.g. Manage Resources, Index, and Jobs. An environment could be used for development, Quality Assurance, User Acceptance Testing, or Live Production.
With the release of Configuration Manager 2.0, there are a number of improvements and additions that have been made. These are as follows:
Newly Supported Objects:
New Commands
A new command has been added which automatically sets up a repository. In the previous version of Configuration Manager, you were required to manually set up your repositories by creating a file structure. Now, you can simply run the following command, with the required information included.
repository –defaultPath <absolute_dir> –defaultRepository <name_of_repository>
A new command has been added which enables you to set up an environment structure inside your repositories.
<name_of_environment> –endpoint –username –password
Note: You still have the option of manually setting up a repository, and manually configuring your environments without using the two aforementioned commands.
A new command has been added which is used to map Accounts, Visibility, and Owners from one environment to another.
{ “sourceUuid”: “targetUuid”: }
A new command has been added, which gives you the ability to list out all of the dependencies of a given configuration. This is a useful command, because when Users are moving Objects such as Workflows or Actions from one environment to another, dependencies may need to be taken into account. For example:
dependencies –environment target –uuid 1bd12345-d6e0-789d-bbd0-be1011a12fef
**Note:**All new commands have been added to the help list, with explanations of each command.
Change to the Run-Rule Expression textbox for Resources
A change has been made to the Resource creation screen, in order to show/hide the run rule text box. This is in relation to whether or not the plugin selected is a Process Resource. For example: If the plugin selected is a Process Resource, then the run rule textbox will be visible, and if it is an IO Capacity resource the run-rule text box will be hidden.
Note: The run-rule textbox will be hidden by default.
Storage Resource Configuration
The File Details Check field in the Configuration section for Storage Resources, is no longer mandatory, and so this field will be collapsed by default from now on.
Search
Jobs and workflows are only searchable by ID. This also means that they won’t be available in the global search.
Plugins
Below is a list of plugins that have been deprecated or renamed.
Renamed Plugins
All of the following renamed plugins are available for the 5.3 series:
Table 4. Renamed Plugins
Plugin | Notes |
---|---|
Create VFS Placeholder Asset | The “VFS” prefix has been removed from the name of this plugin. |
Default Decision Action | The “Default” prefix has been removed from the name. |
Default Script Action | This plugin has been renamed “Internal Script Action” |
Ooyala HTTP Request Message Action | This plugin has been renamed “Backlot Message Action” |
Scripted Decision Action | This plugin has been renamed “Internal Scripted Decision Action” |
Scripted Wait Action | This plugin has been renamed “Internal Scripted Wait Action” |
VFS Archive Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Attachment Import | The “VFS” prefix has been removed from the name of this plugin. |
VFS Baton QC Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Copy Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Create Proxy Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Delete Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS ICR QC Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Image Transcode Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Loudness Analysis QC Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Move Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Multiple Profile Create Proxy Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Multiple Profile Transcode Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Package Export Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Publish Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Transcode Action | The “VFS” prefix has been removed from the name of this plugin. |
VFS Vidchecker QC Action | The “VFS” prefix has been removed from the name of this plugin. |
Mio Http Transfer | This plugin has been renamed “HTTP Transfer” |
Timed Script | This plugin has been renamed “Timed Internal Script” |
Script Executor | This plugin has been renamed “Internal Script Executor” |
Deprecated Plugins
The following plugins have been deprectated for 5.3.0:
Table 5. Deprecated Plugins
Plugin | Notes |
---|---|
Baton QC Action | |
Bulk Import System Action | No longer available from 5.3 onwards. |
Create Placeholder Asset | No longer available from 5.3 onwards. |
Default Archive Action | No longer available from 5.3 onwards. |
Default Copy Action | No longer available from 5.3 onwards. |
Default Create Proxy Action | No longer available from 5.3 onwards. |
Default Delete Action | No longer available from 5.3 onwards. |
Default Move Action | No longer available from 5.3 onwards. |
Default Publish Action | No longer available from 5.3 onwards. |
Default Re-publish Action | No longer available from 5.3 onwards. |
Default Rename Action | No longer available from 5.3 onwards. |
Default Transcode Action | No longer available from 5.3 onwards. |
Default UnPublish Action | No longer available from 5.3 onwards. |
File Asset Import Action | No longer available from 5.3 onwards. |
ICR QC Action | No longer available from 5.3 onwards. |
Image Transcode Action | No longer available from 5.3 onwards. |
Import Attachment | No longer available from 5.3 onwards. |
Loudness Analysis QC Action | No longer available from 5.3 onwards. |
Matrox Export Action | No longer available from 5.3 onwards. |
Multiple Profile Create Proxy Action | No longer available from 5.3 onwards. |
Multiple Profile Transcode Action | No longer available from 5.3 onwards. |
Omneon Export Action | No longer available from 5.3 onwards. |
Package Export Action | No longer available from 5.3 onwards. |
Process Ingest Action | No longer available from 5.3 onwards. |
Update Metadata Action | No longer available from 5.3 onwards. |
Vidchecker QC Action | No longer available from 5.3 onwards. |
Workflow Ingest Action | No longer available from 5.3 onwards. |
FTP Transfer | No longer available from 5.3 onwards. |
Inbox | No longer available from 5.3 onwards. |
QC Resource | No longer available from 5.3 onwards. |
Shared Folder | No longer available from 5.3 onwards. |
Storage Resource | No longer available from 5.3 onwards. |
Transcode Resource | No longer available from 5.3 onwards. |
Vantage Workflow Resource | No longer available from 5.3 onwards. |
Group Wizard Task | No longer available from 5.3 onwards. |
The Desktop Transfer Agent
Ooyala Flex no longer supports the Transfer Agent. From 5.3.0 onwards, only the Web Uploader will be supported.
Java Applet Support
The versions of the Workflow Designer and the Metadata designer that utilize Java Applet, are no longer being supported. These are replaced by HTML5 equivalents. This means that the loading times for those applications will be much faster.