MAM: Tasks are Unable to Complete
When Users started tasks in MAM, they were unable to complete them. Changes have been made to the code in relation to the MAM UI, in order to allow tasks to move into a “Completed” state.
Locking of Masteruser Stops all the Services
If Masteruser gets locked due to failed logins all the services get stopped. In order to prevent this, we have restricted Masterusers from being locked / disabled for REST API calls.
When Users Changed an Action Associated with a Workflow, the References are Not Removed
If Users attempted to update an Action that was associated with a Workflow, they found that the old Metadata was still present in the Key field. We have made code changes, in order to reset the old Metadata key field. These old references are now getting removed successfully when Users change an Action that is associated with a Workflow.
When Users updated Metadata Definitions, a blank entry was shown in the Metadata Update page. In order to solve this problem we have disabled the second-level cache.
Backlot HTTP Publish Action
A new Action has been created, which enables you to publish Assets to Backlot, from Ooyala Flex. This new Action plugin falls under the “Publish” category.
Configuration information for this plugin can be found here.
Removal of Events Dependency on the Workflow Instance Graph
Code changes have been made, in order to remove the dependency on Events when viewing Workflows. By making this change, it means that in future we can purge any unnecessary Event data and so, we are no longer dependent on Event data in order to display Workflow nodes.
Processing of Objects in Ingest Cycles are now Asynchronous
Previously, Ingest requests would invoke spring batch Jobs which contained 1000 Objects. Each batch of Objects was processed in synchronized manner. This has now changed, so that each Job batch is processed on a parallel basis.
This change means that:
POST), the response returns immediately, and the request response cycle doesn’t have to wait.
User-Defined Object Renamed Action
A network error kept occurring when Users attempted to edit the configuration for the User Defined Object Renamed Action plugin. In order to ensure this error doesn’t occur in the future, we have made a change to the “User Defined Object” configuration field. We have simply replaced the combination select option, with a type-ahead option instead. So from now on, the User Defined Object field will be a type-ahead, instead of a combination select.
Network Error Occurs when Users Edit or Create a Series
An error was occurring when Users attempted to edit or create a Series in a hierarchy. The query that was responsible for obtaining the production classification was taking too long (approximately 3 minutes), and this was causing a Gateway Timeout error. The query was scanning all the records in the Object Table. We found that if we specified type ids directly in the query, then the query was much faster.
In order to prevent the Gateway Timeout error from happening in the future, we have created a separate query to obtain the required types. This type is used in the original query (to obtain production classification) as a named parameter. What’s New
Outbound Transfer Service
An Outbound Transfer service has been created. The purpose of this service is to manage the transfer of files from Ooyala Flex to 3rd party systems and services. This service uses the File System to perform transfers to services, over accepting files using HTTP, SCP, FTP, and any other protocol supported by the File System.
The Outbound Transfer Service is an asynchronous service that manages long running outbound media file transfers at scale.
The service will expose a REST API which enables Users to pass file transfer commands to the service. The commands are queued by the service and processed asynchronously. It will manage the lifecycle of a file transfer and emit Events and call back to Ooyala Flex Enterprise as required. File transfers will use transfer protocols allowed by the VFS File System and any other standard platform file transfer provider that will be integrated with Ooyala Flex in the future.
Two new plugins have been created, to coincide with the introduction of the Outbound Transfer service. These are as follows:
Note: A mandatory Service URL field has been added to the Configuration section for the Outbound Transfer Resource in 5.1.8. In this field, you must specify the service URL that will connect to the microservice.
FER Outbound Executor: Integration with File System and VFS Location for Outbound Transfer Service.
We have integrated the File System library with Ooyala Flex Outbound Transfer, in order to make outbound transfers possible.
Timed Database Import Action
A new Timed Action plugin has been added to query a third-party database and also allow for a custom/external JDBC driver. This plugin also handles query responses using a groovy script.
Open Session Action
The query responsible for loading the Configuration options for the Open Session Action has been optimized. This means that the Configuration page for this Action now loads quickly without any issues.
VFS Package Export: Support for Null Execution
If you do not specify any distribution details in the Configuration section for the VFS Package Export Action, the Job will execute and complete successfully, despite the fact it has done nothing.
Auto Retry Property for Jobs in the UI and API
We have added an Auto Retry property for Jobs in the UI and API. The AutoRetries field counts and then displays how many times a Job is auto retired.
Extended support for Run Rules for User Defined Object Types
We have added support for run rules for User Defined Object Types in order to check the creation time.
Removal of the Reindex Option from the Admin Section
The Reindex option has been removed from the Admin section in the Ooyala Flex console. The table in which the reindex statuses were kept, has also been removed.
Internet Explorer 11 Compatibility
Code changes have been made, so that Users can work with in-house web applications in Internet Explorer 11’s compatibility mode.
Enhancements to Custom Data Columns for User Defined Objects
Column preferences are now stored per the root Object type. This means that a User can save their columns preferences for each root User Defined Object Type (previously the column preferences would be overridden every time a User opened the tab of another User Defined Object Type.
Enhancements have also been made to the behaviour of custom search extensions. This means that custom search extensions are able to pass in the entity itself. This grants the ability to run more custom functions.