Ooyala Flex 5.5.5 Release Notes 2017-10-12

Purpose

Ooyala Flex 5.5.5 is a maintenance release to fix issues found in production.

What's New

REST API

We have added an endpoint to the REST API,  that returns a list of variable value options that are available for a specific object variable.

Table 1.
Resource Endpoint Method
actions: /actions/{actionId}/variables/{variableId}/values get

MAM: Default 'Groups' Drop down

From this point onwards we are using browser local storage to store the last selected group in MAM. If a user selects a specific group from the Groups drop down, when they next login, that group will be displayed by default.

Note: This is browser specific. So if you switch to a different browser, the same group will not be displayed.
Note: The browser only remembers the group for 30 days.

Log the reason why a media file fails to validate

Media file validation fail events are now displayed in the History tab for pre-ingest validation jobs.

Issues Fixed

Not able to enable newly created users with UTF characters in username

Usernames containing UTF characters apart from ‘<’, ‘>’, ‘/’, and ‘\’ could not be enabled.Resolution: Usernames containing any UTF characters apart from the above can now be used.

Metadata multicity 0..1 issues

Some users were having issues with certain metadata fields, if they had a multiplicity of 0..1.

Resolution: We have made changes to the code that prevents the addition of empty objects, and head elements for a field with no children and which have multiplicities of  0..* or 0..1.

Remote SSH Command Line message - increase text size

The action configuration of the Remote SSH Command Line Message action truncated long command strings, causing the job to fail.

Resolution: The Command field type was a string and was only capable of keeping 500 characters, so a longer command could not be stored in this field. The Command field type was changed from string to text, so that a larger number of characters can now be stored in the field.

Searching for jobs and workflows by ID doesn't show results

When users searched for jobs and workflows by ID, it was found that the search results were not displayed, unless the drop down button next to the search was selected or if a specific ID was selected.

Resolution: The search results are now displayed correctly.  Jobs and workflows can only be searched for by ID, when a valid number is specified in Search For box, irrespective of whether an ID is selected or not.

Not able to execute action visibility

If an action was created, and visibility for this action was given to an account, when a holder of this account tried to execute that action in MAM, the action page only displayed a loader.

Resolution: The action now displays as expected.

Searching for an asset by name returns no results

Some users found that when they searched for assets by name, it would return no results.

Resolution: This has been fixed, and asset search results are appearing correctly.

Email containing a password link doesn't contain a username

Some users received emails with password links for Ooyala Flex accounts. Upon opening the email, they found that a username was missing, and so they were unable to login.

Resolution:  This has been fixed, and usernames are present in new user emails.

Searching for an existing asset returns no results

When some users searched for specific assets, they found that the assets didn’t show up in the search results, despite the fact these assets existed.
Resolution: This issue has been fixed and the search results are now returning correctly.

Bulk Delete Doesn't Work

Users found that the bulk delete functionality in Core was not working correctly.

Resolution: We have added a Delete button to the bulk delete operation. This means that users can delete bulk workflows which have been cancelled.

Visibility set on an action in Ooyala Flex UI doesn’t apply in MAM
The visibility that is set in Ooyala Flex did not apply in MAM.
Resolution: The proper permissions now apply in MAM.

Character encoder misinterpretations

Users found that an action in a workflow was misinterpreting the REST response, and this was scrambling some special characters. This was due to a discontinuation in the character encoders.

Resolution: We have added a UFT-8 encoder which is used while converting the response from the HTTP call.

Unable to log in when special characters characters are used

Users found that they were unable to log in to Ooyala Flex if login names contained certain special characters.

Resolution: We have restricted the following characters from being used when creating a login username:

  • #
  • &
  • =
  • ?
  • +
  • '
  • "
  • %

PositiveValueValidationHandler class is not working in forms

tv.nativ.mio.metadata.variable.def.validation.PositiveValueValidationHandler was added to the class in the Metadata Integer field. This worked in the Ooyala Flex UI, but did not work in the upload form.

Resolution:  This has been fixed, and is now working in the upload form.

Appendix

Table 2.
Service Version Notes
flex-admin-app 2.0.303.1  
flex-authentication-service 7.2.166.1  
flex-authorisation-service 2.0.206.3  
flex-dataaggreggation-service 1.2.230.7  
flex-divarchive-service 2.1.271  
flex-events-service 2.1.145.6  
flex-fastobject-service 3.2.193.1  
flex-forms-service 0.0.43  
flex-imageproxy-service 3.2.173  
flex-indexelastic-service 5.7.196.1  
flex-job 5.5.5.128  
flex-mam-app 4.2.364.3  
flex-master 5.5.5.128  
flex-metadatadesigner-app 2.1.651  
flex-metadatamerge-service 2.2.201.2  
flex-outboundtransfer-service 2.0.119.1  
flex-publish-service 9.3.203.4  
flex-reviewer-app 3.0.250.1  
flex-searchelastic-service 4.2.282  
flex-streamprocessor-service 1.1.75  
flex-tag-service 1.0.471  
flex-thesaurus-service 0.1.726  
flex-webtransfer-app 7.0.327  
flex-workflowdesigner-app 7.1.148  

Was this article helpful?