Object Properties

One of the most important concepts to understand in the Ooyala Flex platform is that nearly everything is an object. There are various object types in Ooyala Flex. Examples include assets, workflows, and tasks. Objects in Ooyala Flex comprise the following properties:

Table 1.
• Many built-in object types have dashboard section views (assets, workflows etc.)
• You can use "New" in the Navigation panel, to create a new object. Or you can use the API.
• Objects always have their own immutable and unique system-assigned id.
• Objects have a name and a description.
• Objects always have only one owner.
• Objects always belong to only one account.
• Some object can be nested in hierarchies.
• An object has "created" and "last modified" dates.
• All object types can be searched by the same set of fields (general search options).
• Some objects can be enabled, disabled and deleted (deleted objects can still be searched).
• Some objects can be started and stopped.
• Some objects can be imported and exported.
• Objects support attachments, user comments and history.
• Objects support references to other objects.
• You can add and remove shortcuts to objects.
• You can follow and un-follow an object, and be notified of changes made (as well as comments added).
• You can view object history.
• Some objects have metadata schema (custom data) associated with them.
• Some objects allow you to create variants, so you can create custom sub-types.
• Some objects have context where environmental variables can be stored and read.
• Some object support being approved and un-approved.
• Some objects can be locked and unlocked.

Note: Within the body of this guide we may use the words item or items. These words carry the same meaning as object.

One of the benefits of nearly everything being an object is that once you learn one Ooyala Flex object type, such as an asset, you've automatically learned a lot about all other object types in Ooyala Flex.

It's worthwhile taking the time to learn the properties of objects listed above as it is the key to understanding Ooyala Flex. One benefit of Ooyala Flex's object-based approach is that the screens for objects are similar across object types and it also makes the API very easy to use.

For example the summary screen for an asset has similar fields and layout as workflow instance summary screen.

Was this article helpful?