Motion v4.7 - Imagine Communications

Operations Reference

Motion v4.7 21-August-2015

Revision: Release

Motion v4.7 Operations Reference

© 2015 Imagine Communications Corp. Proprietary and Confidential 21-August-2015 | Page 2 of 180

Publication Information © 2015 Imagine Communications Corp. Proprietary and Confidential.

Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal.

This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.

Trademarks Product names and other brands (such as ADC™, D-Series™, Nexio®, Nexio® Insight, Nexio® Motion, PowerSmart®, Versio™) are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies.

Contact Information Imagine Communications has office locations around the world. For domestic and international location and contact information see: http://www.imaginecommunications.com/contact-us/

Support Contact Information For domestic and international support contact information see:

Support Contacts (http://www.imaginecommunications.com/services/customer-care.aspx)

eCustomer Portal (http://support.imaginecommunications.com)

Academy Training (http://www.imaginecommunicationsacademy.com)

http://www.imaginecommunications.com/contact-us/

http://www.imaginecommunications.com/services/customer-care.aspx

http://support.imaginecommunications.com/

http://www.imaginecommunicationsacademy.com/

Motion v4.7

Operations Reference Contents


Contents

About Motion 4 ................................................................................................... 10

Overview ................................................................................................................................................. 10

Login Information Displayed on UI ..................................................................................................... 10

The Device Repository ........................................................................................................................ 11

The Resource Manager ...................................................................................................................... 11

The Workflow Builder ........................................................................................................................ 12

The Workflow Scheduler .................................................................................................................... 13

Monitoring.......................................................................................................................................... 14

System Management ......................................................................................................................... 15

Motion Architecture ............................................................................................................................... 15

Architecture........................................................................................................................................ 15

Scalability............................................................................................................................................ 16

Multiple Site Support ......................................................................................................................... 16

Cloud Support ..................................................................................................................................... 17

Management of Device Failures......................................................................................................... 17

Technology Future-Proofing ............................................................................................................... 17

Pre-requisites to Operation .................................................................................................................... 17

Client Installation and Startup ............................................................................. 18

Install Motion 4 Client ............................................................................................................................ 18

Client Requirements ........................................................................................................................... 18

Before You Begin ................................................................................................................................ 18

Installing the Client Software ............................................................................................................. 18

Upgrading Motion4 Server and Client .................................................................................................... 19

Motion 4.7 Upgrade Note .................................................................................................................. 19

Launch Motion4 ...................................................................................................................................... 20

Motion v4.7



Managing Resources ............................................................................................ 22

About Resource Manager ....................................................................................................................... 22

UI overview ........................................................................................................................................ 22

About Configuring Resources ............................................................................................................. 23

About Upgrading Actions ................................................................................................................... 24

Operations .............................................................................................................................................. 24

Import or Export Repository Settings ................................................................................................. 25

Declare a Device Location .................................................................................................................. 25

Declaring a Device .............................................................................................................................. 26

Declaring a Device Manager............................................................................................................... 28

Making an Association ....................................................................................................................... 29

Creating Load Balanced Groups ......................................................................................................... 29

Save a Draft of Parameter settings .................................................................................................... 32

Publishing the Device bin ................................................................................................................... 32

Building Workflows .............................................................................................. 34

Using the Workflow Builder ................................................................................................................... 34

User Requirements ............................................................................................................................. 34

Key components ................................................................................................................................. 34

About Designing Workflows ............................................................................................................... 35

Help Tools ........................................................................................................................................... 38

Available Activities .................................................................................................................................. 40

Workflow Activities ............................................................................................................................ 40

Human Activities ................................................................................................................................ 43

Resource Activities ............................................................................................................................. 43

Integration Activities .......................................................................................................................... 74

Operations .............................................................................................................................................. 81

View Workflows ................................................................................................................................. 81

Create a Workflow ............................................................................................................................. 82

Create a Workflow Group .................................................................................................................. 83

Edit a Workflow .................................................................................................................................. 85

Import/Export Environment Variables ............................................................................................... 91

About Setting Priorities on Workflows ............................................................................................... 93

Motion v4.7



Staff Management and Task Creation ................................................................................................ 95

Using a Device in a Workflow ................................................................................................................. 96

Set a Workflow to Start Automatically ................................................................................................... 97

Prepare your workflow....................................................................................................................... 97

Publish and Execute a Workflow ........................................................................................................ 99

How Workflows Appear to a User ........................................................................................................ 103

Pre-Configure Workflow Macros ..................................................................................................... 103

Create, Modify and Delete an Action ............................................................................................... 103

Scheduling and Triggering Workflows ................................................................ 107

Schedule Workflow Operations ............................................................................................................ 107

Schedule a Workflow ....................................................................................................................... 107

Update a Scheduled Workflow ........................................................................................................ 108

To Delete a Scheduled Workflow ..................................................................................................... 109

Workflow Trigger Operations ............................................................................................................... 109

Configure a Trigger ........................................................................................................................... 110

Test the trigger ................................................................................................................................. 111

Motion4 Monitoring .......................................................................................... 112

About Monitoring ................................................................................................................................. 112

Global Monitoring ............................................................................................................................ 112

Workflow Monitoring ....................................................................................................................... 115

Monitoring Device Status ................................................................................................................. 116

Monitoring Device Storage Status and Files on Devices .................................................................. 116

Process Explorer Operations ................................................................................................................ 117

Diagnostic Logging Default Settings ................................................................................................. 118

Using Process Explorer ..................................................................................................................... 118

Storage Explorer Operations ................................................................................................................ 121

Using Storage Explorer ..................................................................................................................... 122

Execute an Action ............................................................................................................................. 123

Task Assignment Operations ................................................................................................................ 123

Using Task Assignment ..................................................................................................................... 124

System Management ......................................................................................... 125

Motion v4.7



System Settings ..................................................................................................................................... 125

To Launch System Settings ............................................................................................................... 125

Action Configuration ............................................................................................................................. 126

Open the Action Config Management console ................................................................................ 127

Create a new action ......................................................................................................................... 128

Make a copy of the Action ............................................................................................................... 130

Create an AddressBase from the endpoint alias .............................................................................. 130

Appendix A: NET Framework and Visual Basic Reference .................................. 132

Background ........................................................................................................................................... 132

What is the .NET Framework? .......................................................................................................... 132

What is object-oriented programming?........................................................................................... 132

Classes and objects ............................................................................................................................... 132

Types in the .NET Framework .......................................................................................................... 132

Classes and structures .......................................................................................................................... 133

. NET Framework Class Library (FCL) ................................................................................................ 134

Structures ......................................................................................................................................... 134

Enumerations ................................................................................................................................... 135

Literals .............................................................................................................................................. 136

Visual Basic Operators .......................................................................................................................... 136

Assignment Operators...................................................................................................................... 137

Arithmetic operators ........................................................................................................................ 137

Comparison Operators ..................................................................................................................... 139

Logical Operators ............................................................................................................................. 139

Classes .................................................................................................................................................. 141

Objects, Properties, Methods ............................................................................................................... 141

Objects ............................................................................................................................................. 141

Properties ......................................................................................................................................... 141

Methods ........................................................................................................................................... 142

The String class ..................................................................................................................................... 142

Arrays vs. Collections ............................................................................................................................ 142

Arrays ............................................................................................................................................... 143

Collections ........................................................................................................................................ 143

Motion v4.7



Static classes and class members ......................................................................................................... 145

Appendix B: Device Protocol Parameters ........................................................... 146

Use Notes.............................................................................................................................................. 146

Default Settings & Tool Tips ............................................................................................................. 146

Handling Out-of-Date Definitions .................................................................................................... 146

AmberFin Connection ........................................................................................................................... 147

Protocol ............................................................................................................................................ 147

Antivirus Connection ............................................................................................................................ 148

Protocol ............................................................................................................................................ 148

Digimetrics Aurora Connection ............................................................................................................ 150

Avid Connection.................................................................................................................................... 151

Protocol ............................................................................................................................................ 152

Spying ............................................................................................................................................... 152

Triggers ............................................................................................................................................. 152

Protocol-specific spy parameters ..................................................................................................... 153

Baton QC ............................................................................................................................................... 153

Deployment ...................................................................................................................................... 153

Protocol ............................................................................................................................................ 154

CIFS Connection .................................................................................................................................... 155

Protocol ............................................................................................................................................ 156

Spying ............................................................................................................................................... 156

Triggers ............................................................................................................................................. 157


Digital Rapids Connection ..................................................................................................................... 158

Protocol ............................................................................................................................................ 158

DIVA Connection ................................................................................................................................... 159

Protocol ............................................................................................................................................ 160

Spying ............................................................................................................................................... 160

Triggers ............................................................................................................................................. 161


FIMS Transfer Connection .................................................................................................................... 162

Protocol ............................................................................................................................................ 162

Motion v4.7



Flip Factory Endpoint Connection ........................................................................................................ 163

Protocol ............................................................................................................................................ 163

FTP Connection ..................................................................................................................................... 164

Protocol ............................................................................................................................................ 165

Spying ............................................................................................................................................... 165

Triggers ............................................................................................................................................. 165


Instant Online Connection .................................................................................................................... 167

Protocol ............................................................................................................................................ 167

K2 Summit Connection ......................................................................................................................... 168

Protocol ............................................................................................................................................ 169

Spying ............................................................................................................................................... 169

Triggers ............................................................................................................................................. 169


mCapture Connection........................................................................................................................... 171

Protocol ............................................................................................................................................ 171

Nexio Connection ................................................................................................................................. 172

Protocol ............................................................................................................................................ 172

Spying ............................................................................................................................................... 173

Triggers ............................................................................................................................................. 173


Protocol-specific get extended metadata parameters .................................................................... 174

Selenio Flex Connection ....................................................................................................................... 175

Protocol ............................................................................................................................................ 175

SGL Connection ..................................................................................................................................... 176

Protocol ............................................................................................................................................ 177

Spying ............................................................................................................................................... 177

Triggers ............................................................................................................................................. 177


Vantage Endpoint Connection .............................................................................................................. 179

Protocol ............................................................................................................................................ 179

Passing Variables .............................................................................................................................. 179

Motion v4.7



Appendix C ......................................................................................................... 180

Device Endpoint URI Examples ............................................................................................................. 180

Motion v4.7

Operations Reference About Motion 4


About Motion 4

Overview Motion4 is a new workflow engine that services the requirements to integrate staff, devices, and applications into a holistic workflow. Sometimes referred to as an enterprise bus, the product ostensibly provides the integration and workflow structure for discrete modules that form part of the content management and digital supply chain.

The application includes the following fundamental modules:

The Device Repository.

The Resource Manager.

The Workflow Builder.

The Workflow Scheduler.

The Motion Monitor.

System Management.

Login Information Displayed on UI The following basic Login information is displayed in the upper right of the UI:

Credential (Login and group)

versioning (what version client connects to what version server)

Service Name selected at logon

The UI will display…

if there is no invenio

Current user: N/A

if connected to Invenio and the user name is set

Current user: User Full Name

if connected to Invenio and the user name is not set

Current user: userloginname

Motion v4.7



The Device Repository This system module is where devices are setup based on the license key pertaining to devices and integration sets which have been purchased. It allows the system administrator to configure devices, task and messages, and then is able to publish them to the Resource Manager.

The Resource Manager The Resource Manager along with the Workflow Builder can be considered the heart of the application. The Resource Manager is designed to handle queues and priorities of jobs related to devices until these devices are available to process the job. In addition, it load balances common device types and manages the throughput of work to the devices based on their configuration and loading parameters. For example, if one device were to go offline, then the Resource Manager would take the responsibility for re-prioritizing files to the remaining online devices.

Motion v4.7



The Workflow Builder As the name suggests this module is responsible for the building of workflows that integrate staff tasks, devices, and information from third party applications into a holistic workflow. It is designed to deliver tasks to staffing through the Insight UI along with the relevant data needed to service the task.

It hooks in devices such that a human task can be linked to a device, e.g. Get tape being a staffing task that would drive ingest and transcode functions of a device.

Metadata sets could come from a third party system, e.g. get tape, the id of which comes from a dedicated tape library management system.

Motion v4.7



The Workflow Scheduler This module allows users to schedule work, whether on a consistent basis, one time basis, or on a scheduled basis.

Schedules The Schedules page is for set up and management of scheduled workflow execution. On the menu bar the user can add, edit and delete schedule items. Selecting the Add button brings up the workflow tree with groups so the user can select the desired workflow. After that a window pops up where the user can set up the input of the workflow.

Currently, it is possible to select one of the following schedule options: Once or Daily.

Task Assignment This graphical component is present in both in Motion4 standalone client and Insight Client. It is a powerful tool for cooperation within/between departments where users can see tasks assigned to their groups, accept them, and when a task is completed, update the task status.

Example of User view:

Example of Admin View: Note the available filter options.

Motion v4.7



Monitoring This user application allows an operator to monitor tasks, devices, files status, and the status of a particular workflow or set of workflows. It gives an overview of all the staff, applications, and devices that form part of the infrastructure set which deliver the workflows and processing capability of tasks and workflows.

The Process and Storage Explorers These graphical components are present in both in Motion4 standalone client and Insight Client. They allow an operator to monitor tasks, devices, files status, and the status of a particular workflow or set of workflows.

Process Explorer:

Storage Explorer:

Motion v4.7



System Management Three modules comprise this functionality: System Settings, Actions Configuration, and User Management.

System Settings: This module is used to perform a system backup or to restore a system.

Actions Configuration: Actions are basically shortcuts to workflows, which can be executed on certain MediaFiles. With this module Actions can be configured and saved on the server to make it accessible to all users.

User Management: <This module is under development. > This module is used to manage users and groups, assign roles and manage membership.

Motion Architecture Motion is designed to meet a number of key performance and functional requirements. These include:

System scalability based on use of Microsoft Clustering technology.

A system that manages device failures and re-prioritizes the workflow against remaining devices. Only when using load balanced groups.

A technology set and architecture that provides customers a sense of a safe investment for a 10 year window.

Architecture The following architecture diagram outlines the general view of the application.

Motion v4.7



Scalability Motion supports several installation configurations:

Single PC/Laptop: A demo system only with limited number of supported workflows and devices. A Virtual Machine (VM) will be used for this.

Small server: A small system with two servers using MSCS clustering for fail-over, possibly with dedicated SQL server. This system supports a moderate number of workflows and devices.

Big system: <This scenario has not been validated.> This consists of 3 to up to 40 servers using Cooperative clustering for sharing the workload between servers. Cooperative clustering is active-active clustering; this means each server is handling part of workload.

Multiple Site Support Motion can support one main site and several secondary sites. Every motion service is available on the main site while device manager servers and dedicated devices can reside on secondary sites. Motion can work with secondary sites in connection limited environments; only HTTP connection is required for secondary sites.

Motion v4.7



Cloud Support <This is targeted for a future release.>

Motion 4 provides support for software services residing in Cloud. Some devices can be implemented as software-only devices (no media specific hardware is required); this device software can be implemented as a service running as a Cloud service. Motion provides built-in support for Cloud services. Processing intensive functions such as transcoding and quality check will be implemented as Cloud services.

Management of Device Failures Motion provides health-checking infrastructure for continuous monitoring of the states of individual devices. When a device in the system is detected as offline or malfunctioning, it is reported to Resource Management. The information used to re-schedule tasks for other devices (if possible) and is displayed on monitoring UI’s.

Technology Future-Proofing Technologies used for Motion development are:

C# with .NET Framework 4.5

SOA architecture using WCF

REST API in with next release

NLB clustering for some services

MSCS clustering for some services

Cooperative clustering for MSCS clusters in next release

WPF windows UI

Cloud aware design (entire system can be moved to cloud with small efforts that match to the particular cloud service)

Pre-requisites to Operation The following must be implemented prior to using Motion4:

A properly installed Motion4 system. Installing a Motion4 system is the subject of the Motion4 Installation Guide.

An Insight user account. Motion4 relies on Insight core functionalities to control user access to the system based on Insight user’s permissions.

Using the Workflow Builder feature of Motion 4 requires some Visual Basic Programming knowledge.

See also Pre-Configure Workflow Macros.

Motion v4.7

Operations Reference Client Installation and Startup


Client Installation and Startup

Install Motion 4 Client This section describes how to install Motion Client 4.5. This process applies to all versions of Motion Client, unless otherwise documented.

Client Requirements Operating Systems:

• Windows 7 (with latest SP and all the security updates) • Windows 8 (with latest SP and all the security updates) • Windows Server 2012 (with all the security updates)

Software:

• MSXML 6.0

• Microsoft® .NET Framework 4.5 with latest Service Pack (restart required) • Magellan Diagnostic Logger

Before You Begin Before Installing Motion Client, uninstall any previous version of Motion Client.

Note: With Motion 4.7 and higher the WorkflowDesignerAuthOff reg. key is kept on uninstall so it doesn’t need to be re-created. On another install, the client/server version values do still update, and WorkflowDesignerAuthOff does NOT get inserted on install.

Installing the Client Software 1. Double-click on the Motion Client v4.5 .msi file to start the installation process. The Client

Setup Wizard opens.

2. On the Welcome screen click Next.

3. On the Custom Setup screen specify the location where the client will be installed.

(Default location: C:\Program Files (x86)\Imagine Communications\Motion\Client).

• Click Next to continue. • (Option) Click Reset to reset install parameter original settings. • (Option) Click Disk Usage to review space usage on the specified install location Note: On installation device controllers are deployed in their own individual folders.

Motion v4.7



4. On the User information screen specify the Motion 4 Server address and then click Next to

continue.

5. On the “Ready to install” screen click Install. The installation should complete successfully.

6. On the Completed screen click Finish to conclude the installation.

Upgrading Motion4 Server and Client For details on upgrading Motion4 Server and Client see the “Upgrading Motion4 Server and Client” section in Nexio Motion Server Installation Guide (version 4.7 or higher).

Motion 4.7 Upgrade Note During an upgrade Motion will attempt to load a workflow in the invariant culture. If that fails, it will try loading it in the system culture. Motion will also save all new/updated workflows in the invariant culture. While this will work in most cases, it will still fail if the user tries to load an old workflow created on a system that had a culture that was not the local system's or the invariant.

This means that after upgrading to 4.7, the workflow needs to be exported from that system to be importable on all (4.7+) systems. Alternatively 4.7 can be installed on a separate system, the language settings changed to Portuguese (or other required language), the workflow imported, and then the workflow exported. The resulting workflow will be importable on all 4.7+ systems, regardless of language settings.

Motion v4.7



Launch Motion4 Use the following procedure to launch Motion 4 Client.

1. From the desktop select the Motion Client icon ( ). This launches the login screen.

2. On the login screen specify the following:

• User Name: Enter your user name • Password: Enter your password

• Service Name: Select an available service from the dropdown. • (Optional) Check “Remember me” to have the system remember your credentials for

future access.

3. When finished click Login.

• A loading bar indicator at the bottom of the Motion 4 Login screen indicates progress. The operator does not have access to the UI until loading is completing an the system is fully initialized.

• This launches the Motion Client.

Motion v4.7



Motion v4.7

Operations Reference Managing Resources


Managing Resources

About Resource Manager The Resource Manager along with the Workflow Builder can be considered the heart of the application. The Resource Manager is designed to handle queues and priorities of jobs related to devices until these devices are available to process the job. In addition, it load balances common device types and manages the throughput of work to the devices based on their configuration and loading parameters. For example, if one device were to go offline, then the Resource Manager would take the responsibility for re-prioritizing files to the remaining online devices.

The Resource Manager has the following key roles:

It allows setup of device resources and connection parameters.

It manages queues and priorities for each resource

• Every job assigned to a device must be queued until the device becomes available • Several queues are created to manage priorities of the jobs

It manages special resources that are the Load Balanced groups. A load balanced group is a pool of resources of the same type.

• The load is balanced to each resource of the group accordingly to the state of the device (queue length, CPU usage, etc.) and the limits defined in the resource repository.

• The group also handles device disconnection/failure to offload this device jobs to the remaining devices in the group.

When a job reaches the beginning of a queue, the Resource Manager delegates this job to a Device Manager to actually perform the job.

UI overview From left to right there are 4 different panels:

Device Templates: This panel shows supported devices and a template associates a device model with specific protocol. It provides default values for these protocols. These predefined templates can be dragged into the draft editor, and draft devices can be saved here in the custom folder.

Published: This panel shows the live repository - the list of resources currently configured and used by the system, along with connection health. This is read-only by design. By publishing the draft version, this is completely discarded and overwritten. Users can manually re-enqueue media files on a connection which supports spying. Re-enqueueing the files means a process where the system re-spies existing files on a storage device.

Motion v4.7



Device Bin: This panel displays a draft version of the published repository. The user works on this version only, without corrupting the published version. When the changes are confirmed, “publish” the draft is so it becomes the published version, and the system starts to use it. This is not a local copy, but it is saved on the server and is the same for all users.

Parameters: This is a Contextual property grid displaying setting details for the currently selected item.

About Configuring Resources The Device Bin/Parameter panes of the Repository module are where devices are configured and then made available to the workflow engine as publishable. It means that devices can be added or parameters changed off-line whilst the workflow engine is still operating. For example, this allows the administer to take one device out of a group such as Transcoder A, and reconfigure it, perhaps as part of an upgrade of that transcoder capability and additions to the Motion plugin which supports that transcoder. Likewise, workflows can be edited while the workflow engine is still running, again allowing those workflows that remain published to run and thus the operation as a whole is impacted less.

Key elements of the device repository are:

Communication status of the configured devices

Provide default values for protocols

Group all device related settings

Turn devices into resources by defining limits and financial data

Motion v4.7



About Upgrading Actions When upgrading a system with multiple complex workflows already created, it is labor intensive to find and replace and reconfigure all the activities changed since the previous version.

Motion 4.7 improves the process by implementing the following methods in workflow designer to notify an Engineer of which activities must be replaced.

An Icon is added in the workflow list and a tooltip is added on the icon explaining what it means.

A Warning icon is added on the activities to upgrade in the workflow designer.

In this implementation, the engineer/operator must manually replace the activities to upgrade.

On workflow definition save, if the alerts are active, the system checks them and then hides them if all of the activities were updated.

Operations This section outlines procedures for managing devices and Device Server connections for use with Motion 4. The user can do the following things:

Add and edit Device Managers, Devices, Connections

Set up access properties (address, credentials, etc.)

Set up spying, and triggers

Motion v4.7



The following terms are used in this section:

Location: logical folder which can contain Device Managers, Loadbalanced Device Groups and Devices

Device Manager: a computer where the Device Manager service runs

Device: logical folder which can contain one or more connections

Loadbalanced Device: same as Device, but works differently, as it is load balancing the associated connections based on system load. Typically can manage transcoders and the like, but not storage-type connections.

Connection: an endpoint on a computer which has an address. Actually it is a type of a ‘device’. Types of endpoints are determined by the installed Device Controllers. One Device Controller means one Connection. There are a growing number of Connections available like: CIFS, FTP, Nexio, SGL, Avid, Amberfin, Vantage, etc.

Import or Export Repository Settings Repository settings can be exported after setup or a previously defined set imported for use.

Import Resources To facilitate setup an operator can choose to import a previously defined repository setup.

1. Click Import Draft Repository icon.

2. From the Open window navigate to the file location.

3. Select the file or files to import and then click OK.

Export a Draft Repository A draft of the existing repository can be exported to a file location. This allows backup security for the repository settings and also allows the settings to be imported for use by another instance of Motion4.

1. Click Export Draft Repository icon.

2. From the Save As window, navigate to the desired file location.

3. Click Save.

Declare a Device Location Use this procedure to declare a location (physical sites).

1. Navigate to the Resources tab of the client. The “Device Bin” area is the working area. It is empty after a fresh install.

• A default location is already present. It can be renamed if needed:

Motion v4.7



To rename the location node: In the Device Bin, select the location node to rename. In the Parameter panel, change the name. Click the Save button.

2. Add a new Location: On the Device Bin pane left click and from the context menu select Add New Location.

Before declaring any device, create a “Location” that gives an indication about the geographical location of a device. This is only useful when the customer has several remote facilities. For this example create a “Main” location.

3. Click the “Resources” action menu and select “New Location”.

4. A “New Location” is created. Change its name in the Parameters area.

Declaring a Device Use this procedure to configure a device or devices that will be used in workflows.

1. From the Device Bin tab select Resources > Devices >Add > Storage >, then Select a device type.

2. Select a new device: in the Parameters panel change the following as required:

Motion v4.7



• Name: This is the name of the device seen in the workflow editor or Motion Monitor(e.g. My First Device)

• Parallel limits: Define how many job (long or short) the resource is able/allowed to perform in parallel

• Controlled by: Define which Device Manager machine is able to connect to this device. Available Device Managers are shown with a checkbox for selection.

3. Define which protocols are supported by your device. Select one of the device protocols and

change its parameters. Each protocol has a different set of parameters that will be described in a separate document. For details see Appendix B: Device Protocol Parameters.

Note: HTML docs are available for each plugin. The example graphic shows only the CIFS Connection being added to the device (My First Device > Add >CIFS Connection).

Motion v4.7



4. Configure the device protocol as required. Each protocol has a different set of parameters

that are described in Appendix B: Device Protocol Parameters.

• For Device Controller Help: Use the help button present on the endpoint parameters to open the help on a particular Device Controller. The help opens a web page loaded from the client folder in the default web browser. An index page regroups all the non-resource activities and Device Controller in a table of content. All the pages can navigate to the table of content.

5. When finished click the Save icon on the toolbar to save a draft of these settings. Once

saved, the red star will disappear.

Declaring a Device Manager Use the following procedure to declare a Device Manager and associate a device with it.

1. Specify the Name of the computer (host name) where the Device Manager resides. (Do not use IP Address.)

Device Manager(s) must be manually added. At least one Device Manager must be defined. Multiple Device Manager can be added. It can also be deployed on multiple nodes.

Motion v4.7



The Device Manager is a service in charge of actually connecting to the device. The DeviceManager runs most of the time on the Motion4 server, so the Hostname should be the name or address of the Motion4 server.

2. Click the “Save” button in the toolbar:

Making an Association Use the following procedure to associate a device with a Device Manager.

1. Select your device and select (check) the Device Manager check box:

• The following options limit the number of jobs sent to the device (jobs that are of-limit

are kept in resource manager queue).

Parallel Long term operations: Long operations, such as CIFS Copy, that generate high levels of traffic.

Parallel Short term operations: Short operations, such as 'CIFS Check it' that generate low levels of traffic (i.e. immediate actions).

If unchecked, then unlimited.

2. Save again. The device is ready, but still in the Bin. It is not visible yet by the workflow.

Creating Load Balanced Groups A load balanced group is a pool of resources of the same type.

The load is balanced to each resource of the group accordingly to the limits defined in the resource repository.

The group also handles device disconnection/failure to offload this device jobs to the remaining devices in the group.

Create a load balanced group the same way you created your devices. For details see Declaring a Device.

1. From the Device Bin tab select Resources > LoadBalanced Device Groups >Add> Device Group > New LoadBalanced Device Group.

Motion v4.7



2. On the parameters tab specify the name for the “New Loadbalanced Devicegroup”.

3. Right click on New LoadBalanced Device Group dropdown options icon ( ) and choose Add>. Available options are:

• Quality Check > Generic Quality Check Device • Transcoder > Generic Transcoder Device • Video Server > Generic Video Server Device

• Custom

4. In the Parameters panel change the following as required:

• Name: This is the name of the device group seen in the workflow editor or Motion Monitor

• Parallel limits: Define how many job (long or short) the resource is able/allowed to perform in parallel

• Controlled by: Define which Device Manager machine is able to connect to this device group.

Motion v4.7



5. Manually add each device type to this loadbalanced group. Right click on the Device Group

dropdown options icon ( ) and chose Add>…

Motion v4.7



6. Configure the device protocol as required. Each protocol has a different set of parameters that are described in Appendix B: Device Protocol Parameters.

7. When finished click the Save icon on the toolbar to save a draft of these settings.

Save a Draft of Parameter settings After setting parameters for devices a draft of the settings can be saved by clicking the Save icon

( ) on the toolbar.

Publishing the Device bin Once device and parameter settings have been finalized the settings can be published for use by

clicking the Publish icon ( ) on the toolbar. The published devices will then appear in the Published pane.

To push the changes made in the Bin to production, they must be published.

1. Click the “Publish” button in the toolbar: . The published area, which was previously empty, is now populated with the content of the Device Bin.

The green dot next to the device name indicates that the communication has been established successfully.

2. Navigate to the “Storage Explorer” tab. Your device can be seen in the left list:

3. Double click on the CIFS Connection to see the detected files:

Motion v4.7



Motion v4.7

Operations Reference Building Workflows


Building Workflows

Using the Workflow Builder Workflow Builder is the instrument used to build the workflows that integrate staff, devices, and applications together.

IMPORTANT: This is a for purchase option. For more information contact your Imagine Communications Sales Representative.

If this functionality has not been purchased, customers are locked out of the Workflow Designer. A lock screen blocks access to the workflow designer until the user inputs the required password. When the functionality has been purchased, this password is provided at the time of the installation. The user must re-enter this password when the client is restarted, or once a day, whichever comes first.

User Requirements Using the Workflow Builder feature of Motion 4 requires .Net Framework and Visual Basic Programming knowledge.

Key components Key components can be considered as:

Building of Workflows

Staff Management and Task Creation

Publishing of Workflows

How the Workflows Appear to a User.

Motion v4.7



About Designing Workflows The process for creating Motion 4 workflows has been simplified by using standardized components that are dragged/dropped and linked to create a workflow. Components are configured using Visual Basic elements.

For information on Visual Basic elements see Appendix A: NET Framework and Visual Basic.

Activities Workflows are defined by a tree of Activities. Some Activities are used to control the flow of program, like Sequence, If, and While; some Activities perform specific actions, like Assign; some could communicate with external systems, etc.

An Activity defines its own metadata and execution logic. From WF Runtime’s point of view, an Activity is just a piece of data associated with self-defined behavior. A WF is just a description of such a tree of data. So WF programing is purely declarative and data driven.

Handling Out-of-Date Definitions

Motion 4.6 implements a user notification that an activity in their workflow has an out-of-date definition. All actions will throw an error by default if the parameters given to them come from a different DISCO version than the current one. It is logged to Diagnostic Logging and shows up as the message on the failed action when viewed in the Process Explorer.

This behavior can be overridden by implementing the CanHandleVersion function for particular actions. If the action returns true from the CanHandleVersion call, it is up to the individual action itself to deal with de-serializing the old parameters gracefully.

Motion v4.7



Properties vs. Arguments There are several options available for passing data into an activity. In addition to using InArgument, activities can also be developed that receive data using either standard CLR Properties or public ActivityAction properties.

Note: As of Motion 4.6 all the enum resource activity InArguments are transitioned over to displaying as a combobox instead of a text field.

Note: The OutArguments have not been changed. They remain a text field.

CLR Properties:

When passing data into an activity, CLR properties are the option that has the most restrictions. The value of a parameter passed into a CLR property must be known when the solution is compiled. This value will be the same for every instance of the workflow. In this way, a value passed into a CLR property is similar to a constant defined in code; this value can’t change for the life of the activity, and can’t be changed for different instances of the activity.

Fundamentally, some properties are for input and other for output. Most input and all output can be used with variables.

Arguments:

These are in/ out parameters of the workflow that can be provided by other workflows or third party applications. Arguments should be used when data is only evaluated once during the lifetime of the activity; that is, its value will not change during the lifetime of the activity, but the value can be different for different instances of the activity. Condition is an example of a value that gets evaluated once; therefore it is defined as an argument. Text is another example of a method that should be defined as an argument, since it is only evaluated once during the activity’s execution, but it can be different for different instances of the activity.

ActivityAction:

When data needs to be evaluated multiple times during the lifetime of an activity’s execution, an ActivityAction should be used. For example, the Condition property is evaluated for each iteration of the While loop. If an InArgument were used for this purpose, the loop would never exit, since the argument would not be re-evaluated for each iteration and would always return the same result.

Imagine Communications Types (Previously Harris Broadcast Types) Harris.IMotion4.CommonContracts.JobStateEnum enumeration:

Represents the state of a resource activity • Possible values:

JobStateEnum.Done JobStateEnum.Failed JobStateEnum.Aborted

Harris.IMotion4.CommonContracts.InsightJobStateEnum enumeration:

Motion v4.7



Represents the state of an Insight integration activity • Possible values:

InsightJobStateEnum.Done

InsightJobStateEnum.Failed

Harris.IMotion4.CommonContract.MediaBase.MetadataDescription

• Allows accessing the SOM in the metadata returned from the GetFiles activity. • The following properties are part of the MetadataDescription class.

VF_FrameRate VF_VideoEncoding

VF_NumberOfFrames VF_VideoBitRate VF_NumberOfAudioTracks VF_AudioBitRate VF_AudioEncoding

VF_Width VF_Height VF_Duration VF_DurationTC: Timecode

SGL_Status VF_StartOfMessage: Timecode VF_EndOfMessage: Timecode Guid FileId

Metadata Note

Harris.IMotion4.CommonContracts.MediaBase.MediaFile class:

Represents a media file in Motion database • Properties:

Guid Id Guid EndpointId string Path string Name string Extension

long Size

DateTime Created DateTime Modified bool IsClosed string TapeBarcode int? TapeIndex

MediaFileContentDescription ContentDescription

FileAccessibilityTypeEnum Accessibility

PublishedEndpoint EndpointInfo

string Description string FullName string FullPath

Harris.Dam.TimeCode class:

Represents a timecode

Motion v4.7



• Creating a new instance: New Timecode(int hour, int minute, int second, int frame, TimecodeKind kind) New TimeCode (int hour, int minute, int second, int frame, int frameFraction,

TimecodeKind kind) TimeCode.FromBcd(int bcdValue, TimecodeKind kind)

TimeCode.Parse(string value) Etc..

Harris.Dam.TimeCodeKind enumeration:

Represents the kind of a timecode • Possible values:

Unspecified Smpte25 Smpte30

Smpte30d Smpte24 Smpte50

Smpte60 Smpte60d Other

Harris.IMotion4.Helpers.CustomActivities.Insight. DeleteOptionEnum enumeration:

Represents the different options available for the deletion of essence in ‘Delete Essence or Content’ activity • Possible values:

DeleteOptionEnum.DeleteEssenceIfLastFileAndNoReference DeleteOptionEnum.DeleteEssenceIfLastFile DeleteOptionEnum.NoDelete

Help Tools When working with Workflow Designer there are several help tools available to assist the operator.

Variable picker dialog The Variable picker dialog shows the type of the edited property and displays the type of the complex types. The Variable picker dialog uses a multi-line text box. A splitter allows for resizing. The dialog window is also resizable.

Motion v4.7



All the variables are shown in the tree structure:

Displays the type of the variable (argument, etc.) between brackets next to the variable name

Variables (arguments, etc.) can be expanded to expose the sub properties.

Contextual help is displayed when selecting a variable.

• Dragging a variable (argument, etc.) or a sub property of this variable and dropping it in the text box inserts the variable name or code to access it (sub property or environment variable) in the text box value.

• Clicking a variable (argument, etc.) display the help of the selected variable or sub property

Activity Help For Activities: Use the help button near the Property editor panel to open a web page loaded from the client folder in the default web browser. An index page regroups all the non-resource activities and Device Controller in a table of content. All the pages can navigate to the table of content.

Motion v4.7



Available Activities The Activities tab lists activities that can be defined for a workflow.

Workflow Activities Core building blocks for a workflow.

Motion v4.7



FlowDecision: Uses a condition and defines actions to take if the condition is true or false.

FlowSwitch: Contains an Expression that returns a value when evaluated. The activity also contains a set of Cases, which specifies a unique mapping from possible results of this evaluation to a set of workflow path. The pathhttp://msdn.microsoft.com/en-us/library/system.activities.statements.flownode%28v=vs.110%29.aspx executed is the one whose value matches the value of the evaluated Expression. A Default case can (optionally) be provided for the case in which no match is obtained

If: Equivalent to FlowDecision, but for Sequence workflows

Switch: Equivalent of FlowSwitch, but for sequence workflows

Parallel: Sequence activity that runs a set of child activities at the same time

DoWhile: A sequence looping activity that executes contained activities at least once, until a condition is no longer true.

While: A sequence looping activity that executes a contained activity while a condition evaluates to true

ForEach: A sequence activity that executes an activity action once for each value provided in the collection

ParallelForEach: A sequence activity that executes an activity action once for each value provided in the collection. All the executed activities are run at the same time compared to the ForEach activity that execute them one by one.

ExecuteSubWorkflow: initiate the execution of another workflow. Useful to leverage a utility workflow that can be used by several other workflows.

Delay: Simple activity just waiting for a certain delay.

http://msdn.microsoft.com/en-us/library/ee390738%28v=vs.110%29.aspx


http://msdn.microsoft.com/en-us/library/system.activities.statements.flownode%28v=vs.110%29.aspx

http://msdn.microsoft.com/en-us/library/system.activities.statements.flownode%28v=vs.110%29.aspx



Motion v4.7



TerminateWorkflow: Raises an error flag in the workflow that stops the workflow if not caught.

SendEmail: Sends an email

• To attach documents into an email add a new List<string> Attachments parameter on the sendmail activity.

It expects a file’s full path. e.g.: new list(of string) from {"C:\Windows\Prefetch\AgGlFaultHistory.db","C:\Windows\Branding\ShellBrd\shellbrd.dll"}

The Attachments parameter type is IEnumerable<string>

Write To File: Use this activity to write (create, overwrite, or append) the value of a string variable to a file.

Activity parameters: • Destination file name (InArgument<String>: full path to the file) • File content (InArgument<String>: content to write to the file)

• Write mode (Create, Overwrite or Append) -> create fails if the file already exists, Overwrite and Append just create the file if it doesn't exists.

Advanced Advanced building block for workflow design. These are targeted to advanced users.

Insert Workflow Instance History: Adds a line to the history tab in the ProcessExplorer

Assign: Writes a value into a variable

AddToCollection: Adds a value to a collection (list)

ClearCollection: Clears/empties a collection

ExistsInCollection: Checks if a value is in the collection

RemoveFromCollection: Removes a value from the collection

Motion v4.7



TryCatch: Sequence activity that catches error flags (exception) set by child activities. It has two additional section:

• Catch: section executed if an exception is caught (can be filtered by exception type)

• Finally: section executed an exception being caught or not

FlowChart: Inserts a FlowChart layout activity (that can contain flow activities) in a sequence workflow

Sequence: Inserts an activity that can contain several children activities. This is useful because most sequence activities can have only one child. This embed several children activities in one.

Human Activities Activities that will be manually performed by an operator.

Resource Activities These are device activities that will use resources. Resource activities are grouped into subfolders based on the title of the Device Controller that they belong to. (For example: All Amberfin activities are listed in an Amberfin subfolder.) Like almost all the other information about these activities, these groups (and the names of the groups) are determined at run-time based on the Device Controllers that the server finds.

The "title" property of the device controller's disco is displayed as the name of the group. To change the name of any of these groups, requires changing the title tag on the Device Controller.

As of v4.7 all Resource Activity Arguments default to NULL instead of the default when left empty in the UI.

IMPORTANT: This change may break older activities with non-required arguments that were previously relying on the "bad" behavior.

Motion v4.7



Antivirus Antivirus: The Anti-virus Device Controller uses the ICAP protocol over synchronous TCP-

client.

• Requests: JSON schema of the AntiVirus FileAnalysis requests fileForAnalysis: Full path to the file for analysis

• Upon successful connection the Device Controller verifies: available server resources

available AV license supported methods required for DC operating If any condition is broken an appropriate DCOutput object is generated.

• Responses: JSON schema of the AntiVirus FileAnalysis responses

clean: True if the file is clean otherwise false. threats: Description of found threats delimited with a comma.

Amberfin Amberfin EDL Transcode:

Motion v4.7



• Requests templateName: Transcoding template name conversionProfile: Conversion profile name

sourcePath: Folder of source media files sourceFileExtension: Extension for source media files destinationPath: Destination media file path destinationFilename: Destination media filename edl: EDL in Motion 3 format

jobPriority: Job Priority • Responses

resultFilePath: Result file path Motion has the ability to retrieve the outfilename after a transcode for Amberfin.

Amberfin HealthCheck: • Requests

• Responses isReachable: true if the device is reachable

Amberfin NativeTranscode:

• Requests transcodeJob: Amberfin native transcode xml


resultFilePath: Result file path Motion has the ability to retrieve the outfilename after a transcode for Amberfin.

Amberfin ReplaceAudioTrack: For Video files that contain multiple audio tracks, this property ("track to replace" (index)) allows telling the activity which track to replace. If the track index given for the replacement doesn't exist, the audio track is appended. Example: A Video file contains 4 audio tracks. "Replacing" track 5 or track "99" adds a fifth track to the video file. • Requests

templateName: Transcoding template name conversionProfile: (String)Conversion profile sourceFileDescription: Description of source video file that we spy obtained from

the GetFiles activity (example: FileDescription.Metadata.Metadata) o FileDescription:

Path: Relative path BasePath: Endpoint base path FullPath FullName

Motion v4.7



Guid Id Name Extension Size CreatedOn: DateTime ModifiedOn: DateTime? IsClosed IsDeleted MetadataDescription: Metadata

VF_FrameRate VF_VideoEncoding VF_NumberOfFrames VF_VideoBitRate VF_NumberOfAudioTracks VF_AudioBitRate VF_AudioEncoding VF_Width VF_Height VF_Duration VF_DurationTC: Timecode SGL_Status VF_StartOfMessage: Timecode VF_EndOfMessage: Timecode Guid FileId Metadata Note

public Guid EndpointId public string Description

o Return string

Name Path Extension Size Created on Modified on Is Closed

audioTracksFileDescriptions: (List<String>) One or several audio tracks with a specific naming convention that contains the target audio track index

audio track number matching pattern (regular expression) (String)

pathToOutputDirectory: Path to output/destination directory outputFileName: Output/destination file name jobPriority: Job Priority

• Action:

Motion v4.7



Using the regular expression (3), extract the audio track index from the provided audio filenames (2)

Get the number of audio tracks from the video file metadata (1) Generate the Transcode Parameters XML for Amberfin with this data.

• Responses

resultFilePath: Result file path API Limitation: The current version of the Amberfin API does not support variable number of channels within audio tracks. If the user wishes to replace an audio track, the number of channels in the source and destination audio tracks must be the same. For example, if the target video file contains 7 mono (single channel) audio tracks and the user wises to replace the second audio track, they must specify an input file that contains a single channel mono audio track. The user cannot replace the target mono track with a stereo (two channel) audio track. It is up to the user to ensure the number of channels in the audio tracks of the source and destination files are equal.

Amberfin ReplaceStereoAudio:

• Requests templateName: Transcoding template name conversionProfile: Conversion profile sourceVideoFilePath: Source video file path replacementAudioFilePath: Replacement audio file path

outputVideoFilePath: Output video file path jobPriority: Job Priority

• Responses resultFilePath: Result file path

Amberfin SimpleTranscode: • Requests

templateName: Transcoding template name conversionProfile: Conversion profile name sourcePath: Source media file path sourceFilename: Source media filename

destinationPath: Destination media file path destinationFilename: Destination media filename sourceInTimecode: Defines the frame (the in-point) of the video specified in the

source media to be included as the first frame in this segment. If this value set to null, the first frame of the video specified in the source media will be the first frame included in the segment

sourceOutTimecode: Defines the frame (the out-point) of the video specified in the source media to be the last frame in this segment. If this value set to null, the last

Motion v4.7



frame of the video specified in the source media will be the last frame included in the segment

targetTimecode: The element restripes the timecode of the output to start at the specified location

logoEnabled: Enable logo generation logoPath: Location of the file containing the logo

positionX: Specifies where the logo should be placed horizontally from left corner positionY: Specifies where the logo should be placed vertically from the top width: Specifies width of logo should be scaled in pixels height: Specifies height of logo should be scaled in pixels opacity: How opaque to make the overlayed logo, from 100% being completely

opaque, to 0% being completely transparent

prekeyed: Whether the input logo has been pre-keyed alphaPresent: Whether the input logo has an alpha channel, which should be used

to mix it with the video


resultFilePath: Result file path

Motion has the ability to retrieve the outfilename after a transcode for Amberfin.

Digimetrics Aurora Digimetrics Aurora Analyze: This action retrieves the full path to the report.PDF generated

by Digimetrics Aurora (the light version) in order to send it via email. Now the Digimetrics Aurora DC returns the full path of the report.pdf file after executing an analyze action.

• Requests path: Source media file path

templateName: Template for media QC analysis Create Report Package: Optionally create report zip file. (Default = True)

• Responses reportPackagePath: Report package path reportPdfPath: Report PDF path

passed: QC process passed using the specified template

Digimetrics Aurora HealthCheck Action:

• Requests: • Responses:

isReachable: true if the device is reachable

Motion v4.7



Avid Avid CheckIn: This action registers files into ISIS

• Requests pathToFile: Path to file to check-in destinationInInterplay: Destination Path where to check-in versionComment: version comment

• Responses

Avid Delete:

• Requests path: Path to the asset in Avid Interplay name: Name of the media asset in Avid Interplay

• Responses

Avid HealthCheck:

• Requests • Responses


Avid Move:

• Requests sourcePath: Path to the asset in Avid Interplay

sourceName: Name of the media asset in Avid Interplay destinationFolder: Folder in Avid Interplay to move the asset to

• Responses

Avid SendToPlayback:

• Requests sourcePath: Path to the asset in Avid Interplay

sourceName: Name of the media asset in Avid Interplay transferEngineHostName: Host name of the transfer engine we want to use for

transfer

destinationPlaybackDevice: Name of the playback device we want to send the media asset to

overWrite: Set to true means it is OK to overwrite an asset with the same name at destination

• Responses

Avid Spy: • Requests

• Responses

Motion v4.7



spyResult: The JSON string that contains the spy result

CIFS CIFS CheckDir:

• Request

path: CIFS path (e.g. \dir\subdir). • Response

exists: True if the directory exists otherwise false.

CIFS CheckId:

• Request path: CIFS source path (e.g. \dir\subdir).

fileName: CIFS source filename (e.g. filename.mpg). • Response

exists: true if ID was found

CIFS Copy:

• Request sourcePath: CIFS source path (e.g. \dir\subdir).

sourceFileName: CIFS source filename (e.g. filename.mpg). targetPath: CIFS target path name (e.g. \dir\subdir). targetFileName: CIFS target filename (e.g. filename.mpg). enableOverwriteExisting: Overwrite existing file.

preserveOriginalTimeStamps: Preserve original timestamps (creation time, last access time, last write time) or update them.

withTemporaryFileAndRename: Using a temporary file buffer (a temp file will be created and renamed after copying the file).

• Response

CIFS CopyDir:

• Request sourcePath: CIFS source path (e.g. \dir\subdir). targetPath: CIFS target path (e.g. \dir\subdir).

enableOverwriteExisting: Overwrite existing file. preserveOriginalTimeStamps: Preserve original timestamps (creation time, last

access time, last write time) or update them.

withTemporaryFileAndRename: Copy using a temporary file buffer (a temp file will be created and renamed after copying the file).

• Response

CIFS CreateDir:

Motion v4.7



• Request path: CIFS path (e.g. \dir\subdir). directoryName: CIFS directory name.

• Response success: True if the directory has been created otherwise false.

CIFS Delete:

• Request path: CIFS source path (e.g. \dir\subdir). fileName: CIFS source filename (e.g. filename.mpg).

• Response

CIFS Delete Dir:

• Request path: CIFS path (e.g. \dir\subdir).

• Response

CIFS Generate CCI Based Thumbnails / CIFS Generate Time Based Thumbnails: These actions provide the ability to generate thumbnails based on scene change detection or on fixed intervals. They are able to generate thumbnails (jpeg files) from a video file on a CIFS share (i.e. a browse copy). One action for each option:

Generate thumbnails at the beginning of the file and on each “n” consecutive second (n – configurable value/setting) until the end of the file

Generate a thumbnail at the beginning of the file and on each scene change detected. Scene change detection works like in the current CCI file generation and a when the CCI value exceeds a configurable value/setting a thumbnail is generated. Additional settings are required by CCI extraction (sample rate and threshold)

CCIProcessor: If the CCIProcessor.exe always exports with a "." as the decimal separator, then use the InvariantCulture formatter. Note: Never try to massage numbers or dates into "local" or "good" formats. Always let the framework handle the localization conversions for you.

For 'CIFS Generate CCI Based Thumbnails' activity there are two different arguments with different input parameters: o CCI extraction (CCIProcessor) uses the CCI extraction threshold with a default

value 0.3.

o CCI thumbnail generation threshold uses the 'CCI sample rate' parameter. • CIFS Generate CCI Based Thumbnails Action

Request o sampleRate: Sample Rate

o CCIthreshold: CCI threshold (default value: 0.3) o CCIExtractionThreshold: CCI extraction threshold o path: CIFS file path (e.g. \dir\subdir).

Motion v4.7



o fileName: CIFS file filename (e.g. filename.mpg). o Create marker list file: Generate .txt file about thumbnails.

Response

o markerArray: Contains all the markers items: Marker base values

• CIFS Generate Time Based Thumbnails Action Request

o interval: Interval (in sec) of generating thumbnails.

o path: CIFS file path (e.g. \dir\subdir). o fileName: CIFS file filename (e.g. filename.mpg). o Create marker list file: Generate .txt file about thumbnails.

Response

o markerArray: Contains all the markers items: Marker base values

Thumbnails are created by default in a folder beside the video file having the folder name equal with the file name (including extension) plus a “.thumbnails” extension (e.g. for the “abc.mp4” file the folder name should be “abc.mp4.thumbnails”). Thumbnail file names are equal with the video file name (including extension) plus a part composed by the frame count the thumbnail was taken with 6 digits and the “.jpg” extension. (Example: For the “abc.mp4” file the first thumbnail taken from the first frame of the file is “abc.mp4.000000.jpg” and the one taken at the first second, considering 25fps would be “abc.mp4.000024.jpg”.)

The activities return a list of markers corresponding to the thumbnail. This list can be passed to the Import Markers activity to directly attach the thumbnails to a content or essence.

Optional for the activities: using a check box: create a .txt file • In addition to the jpeg files created in the “thumbnails” folder, a simple textfile is

created as well containing the list of the thumbnails and the timecodes from where the thumbnails were grabbed. The file name is identical to the folder name, but with the “.txt” extension. (Example: For the “abc.mp4” file the file name would be “abc.mp4.thumbnails.txt”.)

• The file contains one line for each thumbnail file. In the first column the line contains the timecode from where the thumbnail was grabbed (if no start timecode is available in the file, then the timecode is considered as starting with “00:00:00:00”)>. The second column shows the filename without path.

CIFS GetBasicFileInfo:

• Request path: CIFS source path (e.g. \dir\subdir). fileName: CIFS source filename (e.g. filename.mpg).

• Response

Motion v4.7



result: Provides the file description. o name: Filename without extension o extension: Filename extension

o size: Size of file in in bytes o duration: Duration of media in frames o creationTimeUTC: UTC time of file creation o lastWriteTimeUTC: UTC time of last modification

CIFS Get Extended Information

• Request

path: CIFS source path (e.g. \dir\subdir). fileName: CIFS source filename (e.g. filename.mpg).

• Response streams: Information of the streams in media file

o items: Information of a stream in a media file

index: Index of the stream in the containing media file codec_type: Type (audio or video) of the codec of the stream codec_name: Name of the codec of the stream codec_long_name: Long name of the codec of the stream bitrate_in_kbps: Bitrate of the stream in kbps duration_in_ms: Duration of the stream in millisecs frame_rate: Frame rate of the video stream number_of_frames: Number of frames in the video stream timecode: Start timecode of the video stream width: Width of the frames in the video stream height: Height of the frames in the video stream display_aspect_ratio: Display aspect ratio of the of the frames in the video stream scanning_type: Scanning type of the video stream sample_format: Sample format of the audio stream sample_rate: Sample rate of the audio stream channels: Channel number of the audio stream

o format: Format information of the media file

number_of_streams: Number of streams in the media file format_name: Name of the format of the media file format_long_name: Long name of the format of the media file filename: Name of the media file file_size_in_bytes: Size of the media file in bytes bitrate_in_kbps: Bitrate in kbps duration_in_ms: Duration of the media in millisecs metadata: Metadata of the media file

CIFS health check

Motion v4.7



• Request • Response


CIFS Move • Request

sourcePath: CIFS source path (e.g. \dir\subdir). sourceFileName: CIFS source filename (e.g. filename.mpg). targetPath: CIFS target path (e.g. \dir\subdir). targetFileName: CIFS target filename (e.g. filename.mpg).

enableOverwriteExisting: Overwrite existing file. • Response

CIFS MoveDir

• Request sourcePath: CIFS source path (e.g. \dir\subdir). targetPath: CIFS target path (e.g. \dir\subdir).

enableOverwriteExisting: Overwrite existing file. • Response

CIFS Parse ADC List File: This activity can parse a LST file (on local file system or on a CIFS share) and returns a collection of "ADC events". The activity takes a CIFS endpoint and a filepath, and returns a list of ADC Events. The "ADC event" is a data type that allows users to access individual fields to apply filters (workflow condition) or retrieve data.

• Request FileName: Path to file to be parsed. TimecodeKind: Possible values are 24, 25, 30, 30d, 50, 60, 60d

• Response

events: The list of ADCEvents o ADCEvent:

Type: ADC API event type Timecode OnAir: on air time ID: identifier Title: title Timecode SOM: start of message IsSOMValid: if False, SOM is not provided Timecode DUR: duration SegmentNumber: segment number DateToAir: scheduled date for the event to air.

o items: Result: True if the operation succeeded, false otherwise.

Motion v4.7



CIFS Rename

• Request path: CIFS path (e.g. \dir\subdir). oldName: Old name. newName: New name.

• Response

CIFS RenameDir

• Request path: CIFS path (e.g. \dir\subdir). oldName: Old name. newName: New name.

• Response

CIFS Spy

• Requests isRecursive: Determines if the spy should be recursive. extensions: Determines the file extensions to spy.

o items:

(Option) CIFS Spy that allows the user to specify masks for directories to ignore during the spy. This option is a string:

o which is empty by default which doesn't change current spy behavior o contains a coma separated list of masks o filter isn't case sensitive and supports wildcards. (e.g. Inputting "*Install" will

match "Motion Install", but not "Aurora Installs".) o when a folder name matches one of the mask, and the recursive spy is also

turned on, the spy action will ignore the folder

o option name: Exclude folders matching naming convention e.g. “*.thumbnails” as a comma separated list.

• Response spyResult: The JSON string that contains the spy result

Diva Archive Motion 4.6 and higher allow the DIVA Device Controller to switch between the 1.0 and 2.1 APIs depending on what the user inputs as the endpoint address.

Diva Archive Action • Requests:

objectName: Name of the object to be queried objectCategory: Category assigned to the Object when it was archived

Motion v4.7



source: Name of the Source (e.g. video server, browsing server). This name must be known by the DIVArchive configuration description.

mediaName: mediaName designates either a Group of Tapes or an Array of Disks declared in the configuration where the Instance has to be created. When this parameter is a null string, the default Group of Tapes called 'DEFAULT' is used.

filesPathRoot: Root folder for the files specified by the filenamesList parameter filenamesList: File path names relative to the directory specified by the

filesPathRoot parameter. When filesPathRoot is null, path names must be absolute names.

items: o qualityOfService: Basic Quality of Service (QOS - qualityOfService) values for

both Archive and Restore requests

priorityLevel: Level of priority for this Request. The priorityLevel can be in the range [0...100] or the value

comments: Optional information describing the Object (can be a null string). • Responses: JSON schema of the Diva Archive responses

Diva CheckId Action

• Requests: objectName: Name of the object to be queried

objectCategory: Category assigned to the Object when it was archived (* or empty value searches on all.)

Group: Check a file presence in a specific group of a category. (* or empty value searches on all.)

An operator can run a DIVA Check ID command and provide a specific tape group. The input has the description:"Restrict the check to a specific tape group".

• Responses: JSON schema of the Diva CheckId responses exists: true if ID was found

Diva Delete Action

• Requests

objectName: The name of the object to be deleted (InArgument<String>: name of the object to delete)

objectCategory: The category of the object to be deleted (InArgument<String>: category containing the object to delete)

priority: The priority of the delete job

(Integer or enum: priority for the diva job created by the action, default is Normal) • Responses

ObjectExisted: True if the object existed, false otherwise (OutArgument<Boolean>: indicate if the object existed and was deleted, or if it didn't exist)

Motion v4.7



getExtendedInfo: Get File List for an Object

• Requests path: Path to object (category) fileName: FileName of object (objectname)

• Responses: JSON schema of the GetExtendedInfo responses

Extended Properties

• fileList: List of files contained in object items:

o getObjectStatus: Diva GetObjectStatus Action: Gets the status of the object (offline/online, returns a list of comma seperated tape IDs)

• Requests objectName: The name of the object to be queried.

objectCategory: The category of the object to be queried. Wildcards ("*") allowed. • Responses: JSON schema of the Diva GetObjectStatus responses

online: True if an object instance exists on an inserted tape, false otherwise tapeIDs: A comma seperated list of tape VSNs that the object is currently stored on

Diva HealthCheck Action

• Requests: JSON schema of the Diva HealthCheck requests

• Responses: isReachable: true if the device is reachable

Diva PartialRestore Action

• Requests: objectName: Name of the object to be queried objectCategory: Category assigned to the Object when it was archived

destination: Destination (e.g. video server or browsing server) for the Object files. This name must be known by the DIVArchive configuration description.

destinationPath: Destination Path destinationFilename: Destination Filename SOM: SOM in timecode EOM: EOM in timecode

qualityOfService: Basic Quality of Service (QOS - qualityOfService) values for both Archive and Restore requests

priorityLevel: Level of priority for this Request. The priorityLevel can be in the range [0...100] or the value

format: Value of the video format (Usually want DIVA_FORMAT_AUTODETECT) Source Filename: (Optional) Specify the name of the file to restore out of the DIVA

object, instead of restoring the one with the same name as the object itself.

Motion v4.7



This defaults to the original behavior (restore the file with the same name as the object) when the Device Controller receives an empty/null string.

• Responses: JSON schema of the Diva PartialRestore responses

Diva Restore Action

• Requests: objectName: Name of the object to be queried

objectCategory: Category assigned to the Object when it was archived destination: Destination (e.g. video server or browsing server) for the Object files.

This name must be known by the DIVArchive configuration description.

filesPathRoot: Root folder for the files specified by the filenamesList parameter qualityOfService: Basic Quality of Service (QOS - qualityOfService) values for both

Archive and Restore requests priorityLevel: Level of priority for this Request. The priorityLevel can be in the range

[0...100] or the value • Responses: JSON schema of the Diva Restore responses

Diva DoSpy Action • Requests: JSON schema of the Diva DoSpy requests

• Responses: JSON schema of the Diva DoSpy responses

DIVA SpyInc Action

• Requests from: from date time e.g.: 2013-11-20 11:37:27

• Responses


FlipFactory FlipFactory HealthCheck

• Requests • Responses


FlipFactory Transcode

• Requests userName: FlipFactory username. password: FlipFactory password. factoryName: FlipFactory factory name.

sourceFilePath: FlipFactory source file path (eg c:\inbox\test.mp4). targetFileName: FlipFactory target filename without extension (it will be determined

by the factory e.g. mp4).

Motion v4.7



• Responses: JSON schema of the FlipFactory Transcode response

FIMS Transfer FIMS Transfer DC health check

• Request

• Response isReachable: true if the device is reachable

FIMS Transfer DC transfer

• Request essenceLocatorType: Essence locator type files: Files/folders to transfer

o items: destination: Destination folder

• Response: JSON schema of the transfer action response

FTP FTP CheckDir

• Requests path: FTP path name

• Responses exists: true if ID was found

FTP CheckId • Requests

path: FTP path name filename: FTP file name The CheckID action transitions the server into binary transfer mode before requesting the size of a file.


FTP CreateDir

• Requests path: Path on the FTP server name: Directory name on the FTP server to create

• Responses succeeded: true if creation succeeded

FTP CustomCommand

Motion v4.7



• Requests command: FTP Custom Command

• Responses

commandSucceeded: true if command succeeded

FTP Delete Dir

• Requests path: Path on the FTP server name: Directory name on the FTP server to delete

• Responses

succeeded: true if deleteDir succeeded

FTP Delete Id

• Requests path: FTP path name filename: FTP file name

• Responses

succeeded: true if deleteId succeeded

FTP Download

• Requests srcPath: FTP path on server srcFile: FTP file name on server dstPath: FTP path local

dstFile: FTP file name local • Responses

succeeded: true if download succeeded

FTP GetFileList

• Requests path: FTP path

• Responses files: List of files

o items: isClosed: true if the file is closed isDeleted: true if the file was deleted metadata: Extended metadata name: Filename without extension extension: Filename extension size: Size of file in in bytes duration: Duration of media in frames

Motion v4.7



creationTimeUTC: UTC time of file creation lastWriteTimeUTC: UTC time of last modification

FTP HealthCheck

• Requests: JSON schema of the FTP HealthCheck requests • Responses


FTP Device Controller does a logon in the Healthcheck action and the UI shows if the password is incorrect.

FTP Rename

• Requests fromPath: FTP rename from path fromFile: FTP rename from file toPath: FTP rename to path toFile: FTP rename to file

• Responses succeeded: true if rename succeeded

FTP Server To Server Transfer

• Requests srcPath: FTP path on source server

srcFile: FTP file name on source server dstPath: FTP path on destination server dstFile: FTP file name on destination server

• Responses succeeded: true if transfer succeeded

Communication Log Note: Source and Destination prefixes are added to the FTP server-to-server transfer communication log entries.

FTP Spy

• Requests skipEmptyFiles: True if skip empty files

• Responses spyResult: The JSON string that contains the spy result

FTP Upload • Requests

srcPath: FTP path local srcFile: FTP file name local dstPath: FTP path on server

Motion v4.7



dstFile: FTP file name on server • Responses

succeeded: true if upload succeeded

Instant Online healthCheck: Instant Online HealthCheck Action

• Requests: JSON schema of the Instant Online HealthCheck requests • Responses


renderEdl: IOL Render EDL Action • Requests

EDL: FinalCutPro XML (InArgument<String>: FCP XML)

AudioChannels: Audio channels (Int32) AudioBitsPerSample: Audio bits per sample (Int32)

OutputFileName: Filename for the generated file. Can be empty. (InArgument<String>: filename for the generated file)

• Responses GeneratedFileName: Generated file name.

(OutArgument<String>: filename for the generated file if none was provided)

About the Workflow: The EDL is produced by Insight using the “Project” function and is produced based on the low-res proxy. A Motion workflow is initiated by the Insight user to start the IOL process. The EDL is passed to Motion as parameter (it is an internal format). Motion with the right “plug-in” formats the EDL to match the target device requirements (in this case IOL). Usually the material ID is used in the final EDL, not file name (e.g. in case of IOL, the files should be in a Nexio SAN).

About IOL transcodes: The intermediate files created by the DC when scheduling IOL transcodes are created with the .xml extension instead of the .fcpxml extension.

K2 Summit K2 Summit CheckID

• Requests uri: The URI to the video file


K2 Summit Change SOM: Some workflows need to be able to change the SOM of a clip on the K2 device. This action takes the new SOM as an input property (can be a variable) and uses the API to change the SOM on the device.

Motion v4.7



• Requests sourceUri: URI to the source Clip newClipSOM: New start of message (SOM) (Type of input argument:

Harris.Dam.Timecode) • Responses: JSON schema of the K2 Summit Change SOM responses

K2 Summit Copy

• Requests srcUri: URI to the Source Clip dstUri: URI to the Destination Clip

• Responses: JSON schema of the K2 Summit Copy responses

K2 Summit Delete

• Requests

uri: The URI to the video file to be deleted • Responses: JSON schema of the K2 Summit Delete responses

K2 Summit Set AFD: Some workflows need to be able to change the AFD metadata of a clip on the K2 device. This action takes the new AFD value (string) as an input property (can be a variable) and uses the API to change the metadata on the device.

• Requests uri: The URI to the video file to be set AFD afd: The AFD to write to the clip.

• Responses: JSON schema of the K2 Summit Set AFD responses

Possible AFD code values: AFD is decimal number from 0 to 15. Possible values of AFD codes described in table below.

Active Format Description codes from SMPTE2016-1 Specification

Active Format Description AFD Code

In a 4:3 coded frame In a 16:9 coded frame

Undefined (see below) Undefined (see below) 0000 (0)

Reserved Reserved 0001 (1)

Letterbox 16:9 image, at top of the coded frame (see note 1)

Full frame 16:9 image, the same as the coded frame (see notes 1 and 2)

0010 (2)

Letterbox 14:9 image, at top of the coded frame (see note 1)

Pillarbox 14:9 image, horizontally centered in the coded frame (see notes 1 and 3)

0011 (3)

Letterbox image with an aspect ratio greater than 16:9, vertically centered in the coded frame (see note 1)

Letterbox image with an aspect ratio greater than 16:9, vertically centered in the coded frame (see note 1)

0100 (4)


Motion v4.7



Active Format Description codes from SMPTE2016-1 Specification

Active Format Description AFD Code

In a 4:3 coded frame In a 16:9 coded frame



Full frame 4:3 image, the same as the coded frame

Full frame 16:9 image, the same as the coded frame

1000 (8)

Full frame 4:3 image, the same as the coded frame (see note 4)

Pillarbox 4:3 image, horizontally centered in the coded frame

1001 (9)

Letterbox 16:9 image, vertically centered in the coded frame with all image areas protected (see note 5)

Full frame 16:9 image, with all image areas protected (see note 5)

1010 (10)

Letterbox 14:9 image, vertically centered in the coded frame

Pillarbox 14:9 image, horizontally centered in the coded frame

1011 (11)


Full frame 4:3 image, with alternative 14:9 center (see note 6)

Pillarbox 4:3 image, with alternative 14:9 center (see note 6)

1101 (13)

Letterbox 16:9 image, with alternative 14:9 center (see note 6)


1110 (14)

Letterbox 16:9 image, with alternative 4:3 center (see note 6)


1111 (15)

• Notes: If Bar Data is not present, AFD ‘0000’ indicates that exact information is not available and the active image should be assumed to be the same as the coded frame. AFD ‘0000,’ when accompanied by Bar Data, signals that the active image’s aspect ratio is narrower than 16:9, but is not 4:3 or 14:9. As the exact aspect ratio cannot be conveyed by AFD alone, wherever possible AFD ‘0000’ should be accompanied by Bar Data to define the exact vertical or horizontal extent of the active image. AFD code ‘0100’ signals that the active image aspect ratio is wider than 16:9. As the exact aspect ratio cannot be conveyed by AFD alone, wherever possible AFD ‘0100’ should be accompanied by Bar Data to define the exact vertical extent of the active image. Bar Data is not supported by the K2 media server as these formats are not commonly used today in broadcast. In determining AFD codes to originate, readers are cautioned that emission systems

in some areas of the world may not support some or all of AFD codes ‘0001’ through ‘0111.’

Motion v4.7



In a 16:9 coded frame, AFD code ‘0010’ represents the same image display as AFD code ‘1000.’ AFD code ‘1000’ is the preferred coding for full-frame 16:9 images. AFD code ‘0010’ is not used in North America.

In a 16:9 coded frame, AFD code ‘0011’ represents the same image display as AFD code ‘1011.’ AFD code ‘1011’ is the preferred coding for a horizontally centered 14:9 pillarbox image. AFD code ‘0011’ is not used in North America.

In a 4:3 coded frame, AFD code ‘1001’ represents the same image display as AFD code ‘1000.’ AFD code ‘1000’ is the preferred coding for full-frame 4:3 images.

AFD code ‘1010’ is intended for use with images that may not fill the frame vertically but where all areas of the image should be displayed (i.e., an image where cropping is not permitted) and which therefore can only be adequately displayed in letterbox format.

The “alternative center” image refers to an area of essential picture information. The areas outside this area (shown gray in the illustrations) may optionally be cropped without significant loss to the viewer.

Aspect ratio information for the coded frame is not part of the AFD code and it is necessary to code this aspect ratio information separately. The AFD and aspect ratio codes may be transported together as part of a larger data structure.

K2 Summit GetRemainingSize

• Requests channelName: Channel Name e.g. 'C1' volumeName: Volume Name e.g. 'C:'

• Responses totalStorage: Total Storage in Bytes remainingStorage: Remaining Storage in Bytes

K2Summit HealthCheck

• Requests: JSON schema of the K2Summit HealthCheck requests • Responses


K2 Summit Rename

• Requests oldUri: URI to the OLD Clip newClipName: NEW Clip Name

• Responses: JSON schema of the K2 Summit Rename responses

K2Summit Spy

• Requests: JSON schema of the K2Summit Spy requests • Responses


K2 Summit Subclip

Motion v4.7



• Requests sourceClipName: Source Clip Name sourceClipPath: Source Clip Path

destinationClipName: Destination Clip Name destinationClipPath: Destination Clip Path destinationClipSOM: Destination Clip Start Of Material(SOM) destinationClipEOM: Destination Clip End Of Material(EOM)

• Responses: JSON schema of the K2 Summit Subclip responses

mCapture mCapture HealthCheck Action

• Requests: JSON schema of the mCapture HealthCheck requests • Responses:


mCapture SubClip Action

• Requests: SourceFilePath: File on which sub-clip operation is being performed.

(InArgument<String>: full path to the file to process) DestinationFilePath: File resulting from the sub-clip operation.

(InArgument<String>: full path to the result file)

StartTimecode: Start time of the sub-clip. Subclip action will create the result clip by extracting content from the source file from SOM to end of Duration.

(InArgument<TimeCode>) Duration: Duration of the sub-clip.

(InArgument<Duration>)

• Responses: JSON schema of the mCapture SubClip responses

Nexio Nexio CheckId

• Requests id: Extended ID of the file


Nexio ConsolidateId: This action purges the specified Id from all its video and audio material that is not included in any of the subclips


Motion v4.7



• Responses: JSON schema of the Nexio ConsolidateId responses

Nexio Subclip

• Requests subclipId: The extended ID of the subclip that is going to be created parentId: The extended ID of the clip that the subclip will be created from

markIn: The new subclip will start from the in timecode of the parent markOut: The new subclip will end at the out timecode of the parent

• Responses: JSON schema of the Nexio Subclip responses

Nexio Delete: This action deletes the clip with the given Id from the endpoint


• Responses: JSON schema of the Nexio Delete responses

Nexio GetExtendedInfo


• Responses streams: Information of the streams in media file

o items: Information of a stream in a media file include: index: Index of the stream in the containing media file codec_type: Type (audio or video) of the codec of the stream codec_name: Name of the codec of the stream codec_long_name: Long name of the codec of the stream bitrate_in_kbps: Bitrate of the stream in kbps duration_in_ms: Duration of the stream in millisecs frame_rate: Frame rate of the video stream number_of_frames: Number of frames in the video stream timecode: Start timecode of the video stream width: Width of the frames in the video stream height: Height of the frames in the video stream display_aspect_ratio: Display aspect ratio of the of the frames in the video stream scanning_type: Scanning type of the video stream sample_format: Sample format of the audio stream sample_rate: Sample rate of the audio stream channels: Channel number of the audio stream

format: Format information of the media file o number_of_streams: Number of streams in the media file o format_name: Name of the format of the media file o format_long_name: Long name of the format of the media file o filename: Name of the media file

Motion v4.7



o file_size_in_bytes: Size of the media file in bytes o bitrate_in_kbps: Bitrate in kbps o duration_in_ms: Duration of the media in millisecs

o metadata: Metadata of the media file

Nexio GetExtendedInfoItem

• Requests extendedId: Extended ID of the file key: Key of the extended field or metadata to read

• Responses

value: Value of the extended field or metadata item

Nexio HealthCheck

• Requests: JSON schema of the Nexio HealthCheck requests • Responses


Nexio Rename

• Requests oldExtendedId: Extended ID of the file to rename

newExtendedId: New extended ID of the file • Responses: JSON schema of the Nexio Rename responses

Nexio SetExtendedInfoItem

• Requests extendedId: Extended ID of the file

Machine Name: The video server name and channel where the media was recorded umid: Unique identifier username: UNICODE-stored field indicating the individual logged in to the system at

record time department: UNICODE-stored field indicating the department of the individual

logged in at record time. Only supported in MediaBase PRO systems extendedDescription: UNICODE-stored 120-character user entry text field for storing

details about media. Max size is 240 bytes extendedAgency: UNICODE-stored 15-character user entry text field for storing

detail about media. Max size is 30 bytes userField1: UNICODE-stored 25-character user entry field. Max size is 50 bytes

userField2: UNICODE-stored 25-character user entry field. Max size is 50 bytes userField3: UNICODE-stored 25-character user entry field. Max size is 50 bytes userField4: UNICODE-stored 25-character user entry field. Max size is 50 bytes startTC: Start time code

Motion v4.7



Type: Set the "Type" metadata attribute. The maximum length of this field is 5 ASCII characters.

oldDescription: Text description field oldAgency: Text description field deleteProtected: Value is true if media should be delete protected, false if it should

not be delete protected

videoARC: ARC applied to the clip when it is loaded for playout in a channel configured for the clip's aspect ratio

videoARCForce: Force SD clips to given aspect ratio or override any AFD data present

audioTracksInfo: Set information about audio tracks extracted extended fields. Track token is mandatory, other tokens are optional and separated by semicolons. Token list: compressed, count, formatCode, format, tag. Example: Track=1;tag=123

• Responses: JSON schema of the Nexio SetExtendedInfoItem responses

Nexio Spy

• Requests SkipEmptyFiles: True if empty files have to be skipped SkipAudioFiles: True if audio files have to be skipped

SkipUMIDLessFiles: True if UMID-less files have to be skipped • Responses


Nexio TrimSegment: This activity supports trimming of videos on Nexio Servers equivalent to the operations on Nexio in M3. The activity takes in an extended id, a start timecode, and a stop timecode.

The user inputs an actual Harris.Dam.Timecode for the start and end points of the segment.

All instances of timecodes in the Nexio DC are changed form from string format timecodes to actual Harris.Dam.Timecodes.

The activity trims the video clip specified by the extended id, using the start and stop timecodes provided.

The activity trims everything except what the user specifies, effectively creating an in-place subclip. The TrimSegment activity is frame-accurate (and will actually correct some cases of bad user input). Also, the trimming works multiple times.

• Requests

ExtendedId: The Extended ID of the clip to be trimmed StartTimeCode: Timecode to start trim EndTimeCode: Timecode to end trim

• Responses: JSON schema of the Nexio TrimSegment responses

Motion v4.7



SelenioFlex File SelenioFlex File HealthCheck

• Requests: JSON schema of the SelenioFlex File HealthCheck requests • Responses


SelenioFlex File Transcode

• Requests

splitOptions: Split Options o NONE o AUTOMATIC o ALWAYS

o NEVER adjustAspectRatio: Adjust Aspect Ratio Options

o NONE o ADJUST_WIDTH o ADJUST_HEIGHT

o GROW_ONLY o SHRINK_ONLY o LETTERBOX_OR_PILLARBOX o CROP

groupName: Group (Should be fetched from Transcoder) sourceFileUNC: Full Path to the Source file name (UNC) projectFromServer: Project from Server (Should be fetched from Transcoder) destinationPath: Destination path

• Responses transcodeSuccess: True if transcode job finished successfully, false otherwise resultFilePaths: The list of files produced by the transcode operation

o items: Motion has the ability to retrieve the outfilename after a transcode for Selenio Flex. It takes advantage of a Selenio Flex field called "outputFiles" on a "task" object that can be queried for transcode progress.

ca.digitalrapids.mediamanager.common.model.ws

Class TranscodeTask outputFiles List<MediaFile> outputFiles The output file(s) of the transcode task

Motion v4.7



SGL SGL Archive

• Requests volumeGroup: The set of tapes or disk to be used for the archive operation fullFileName: The full path of the file including the server it resides on and the file

name guid: A unique identifier (Clip name, Guid) which must be unique throughout the

entire archive(Guid)

priority: Prior to FlashNet version 6.4.01: a value from 1 to 10, 1 being highest. The default is 5. From FlashNet version 6.4.01 this range is extended from 0 (zero) to 100. A value of zero allows FlashNet to prioritise your job itself. The default is 5.

verifyFile: Specifies if the archive should perform a bitwise verification of the archived data with the original data. This process is performed after the archive has finished writing

deleteFile: Specifies if the files being archived should be deleted after the archive has finished. This is not supported by some video servers

fileSize: The size, in bytes, of the file. Specifying this parameter helps FlashNet optimize the storage of your data

• Responses: JSON schema of the SGL Archive responses

SGL CheckID

• Requests guid: A wildcard specification of the Guid string. The % character can be used to

form a search string which will return a list of pattern matches containing the storage details of each Guid. If the user only provides the endpoint, a warning dialog is displayed detailing missing information.

group: A wildcard specification of the media pool to which the Guids were originally archived. The % character can be used to specify more than one media pool e.g. `Group%' will return all Guids archived (or subsequently copied) to volumes in Group1, Group2, Group3 etc.

volume: A wildcard specification of the volume on which the Guids reside. The % character can be used to specify more than one volume e.g. `Tape%' will return all Guids currently on Tape1, Tape2, Tape3 etc.

• Responses

exists: true if ID was found

SGL Delete

• Requests guid: Clip name to delete

• Responses: JSON schema of the SGL Delete responses

Motion v4.7



SGL GetFileStatus

• Requests guid: Clip name (Guid) of the file to look for

• Responses resultCount: Number of entries returned

status: The current status of this instance of the Guid; one of: 'DELETED', 'ONLINE' or 'OFFLINE'

filesArray: Contains all the available information about the matching Guids o items: Information about media on SGL Flashnet

SGL HealthCheck

• Requests: JSON schema of the SGL HealthCheck requests • Responses


SGL Migrate

• Requests sourceVolume: The name of the medium with the archive containing the assets to

migrate

sourceArchiveNumber: The archive number containing the assets to migrate destVolume: The name of the target medium

moveOrCopyAssets: A flag to govern whether the assets are moved or copied to the target medium

• Responses: JSON schema of the SGL Migrate responses

SGL Partial Restore

• Requests guid: Clip name (Guid) of the file to be restored destinationPath: NOTE: if file exists the operation will fail (WARNING: NO

OVERWRITE!) destinationFileName: NOTE: if file exists the operation will fail (WARNING: NO

OVERWRITE!) startOffset: Start Offset Frame

endOffset: Stop Offset Frame priority: Prior to FlashNet version 6.4.01: a value from 1 to 10, 1 being highest. The

default is 5. From FlashNet version 6.4.01 this range is extended from 0 (zero) to 100. A value of zero allows FlashNet to prioritise your job itself. The default is 4.

• Responses: JSON schema of the SGL Partial Restore responses

SGL Restore

• Requests

Motion v4.7



guid: Clip name (Guid) of the file to be restored destinationPath: NOTE: if file exists the operation will fail (WARNING: NO

OVERWRITE!) destinationFileName: NOTE: if file exists the operation will fail (WARNING: NO

OVERWRITE!) priority: Prior to FlashNet version 6.4.01: a value from 1 to 10, 1 being highest. The

default is 5. From FlashNet version 6.4.01 this range is extended from 0 (zero) to 100. A value of zero allows FlashNet to prioritise your job itself. The default is 4.

• Responses: JSON schema of the SGL Restore responses

SGL Spy • Requests

idMask: To filter based on ID groupMask: To filter based on Group volumeMask: To filter based on volume (tape ID)

• Responses


SGL SpyInc

• Requests idMask: To filter based on ID groupMask: To filter based on Group volumeMask: To filter based on volume (tape ID)

from: from date time e.g.: 2013-11-20 11:37:27 • Responses


Vantage Vantage HealthCheck Action

• Requests: JSON schema of the Vantage HealthCheck requests • Responses


Vantage Start Workflow

• Requests workflowName: Vantage workflow name.

sourceFilePath: Vantage source file path (eg c:\inbox\test.mp4). parameters: Vantage parameters. Job Title: When the user specifies a job title, the DC starts the workflow with that

job title.

Motion v4.7



• Responses labels: Vantage metadata labels variables: Vantage workflow variables

(optional) Dictionary<String, String> and that contains for all the vantage workflow variables, the name and the value. The Result returning the label is kept, but remains optional as some specific use cases might need it.

Failed Actions: At the end of the Vantage workflow, whatever the status is, a query is performed for the failed actions to get the: action name, description, and error message. This OutArgument is populated with a list of "VantageFailedAction" (ActionName, Description, ErrorMessage). This list is populated with all the failed actions regardless of the return status of the activity.

Integration Activities Activities provided to interact with external applications.

Insight – Generate ID: Generates one or more ID labels based on a given Insight ID class.

Generate UMID: Generates an SMPTE Unique Material Identifier label

Regular Expression: Runs the specified (Pattern) regular expression against the input string. Returns the resulting array. Types: Split - Splits the input string into an array of substrings at the positions defined by the regular expression. Match - Returns the groups matched by the regular expression.

ADC Material Checker: Workflow designers need to verify that a file is not scheduled for playout before deciding to delete it from the playout server. The common use case is a

Motion v4.7



purge workflow when files are automatically deleted if they match certain criteria. In these scenarios it is mandatory to check that the file is not in selected transmission lists before proceeding to deletion.

This activity checks if a file is scheduled for playout. • Related ADC Service Enhancement: 89504: Allow Motion to be able to check for In use

ID.doc This change provides a way for Motion to find out if clips are on a playlist. It checks

1 Material ID against several ADC lists. A method is added to the List Service API which goes through the whole copy of the

list and looks for the specific Ids. This is a time consuming operation, not a database request, so frequent calls might affect the List Service performance which is more time critical than the database operations.

It is recommended to call the newly implemented method ‘CheckMaterialIds’ not more often than 0.5 seconds.

The current List Service clients will still work with the List Service despite the added method, but it will not be available until they update their WCF references.

Insight - Add attachment: Allows attaching documents (PDF, Word, etc.) to Insight content or essence. For "Insight - Add attachment"…

• The Title doesn't is not a required field. If the title is empty, the system parses a file name from the file path.

When parsing the title, the extension is removed The title is inserted into the database, it does not show in the Invenio client. Motion now requestsIinvenio for its languages and inserts the title as an entry in all

the languages. • The following options were implemented: 'From Disk' and 'Add Url'.

The add attachment activity now has a drop down input which allows the user to select between adding the file as a reference (Add URL as attachment), or adding the File Data (Add attachment from disk).

When the File Data, the data is also uploaded with the attachment. Both options work for Content and Essence. Save File to DB is now default.

Insight - Update content dates: Each date is optional. For content preparation workflows, date values are updated in a Motion activity. Ideally, this is a single activity where anyone or multiple dates can be set on a Content object within Insight: ProductionDate, FirstAirDate, ExpirationDate, PurgeDate, and/or NextTxDate.

• "Insight - Update content dates" activity: Each date is optional. For content preparation workflows, date values are updated in a Motion activity. With this implementation, this is a single activity where one date can be set on a Content object within Insight: ProductionDate, FirstAirDate, ExpirationDate, PurgeDate, and/or NextTxDate.

Motion v4.7



Insight- Create or Update Essence: Creates or updates an Insight Essence if used in a

triggered workflow.

Insight- Create or Update Content: Creates or updates an Insight Content if used in a triggered workflow

Insight- Update Related Content: Updates the duration of Insight Content segments referencing a given essence

Insight- Content Check ID: Checks if an Insight Content exists based on the provided House Id

Insight- Essence Check ID: Checks if an Insight Essence exists based on the provided House Id

Insight- Create Synchronizer Event: Creates a new insert/update/delete event in Insight Synchronizer Service queue if used in a triggered workflow

Insight- Associate Contents: Creates an Insight Content if used in a triggered workflow and associate it with another Insight Content (Asssociation can be version/sub/related)

Insight- Delete Content or Essence: Deletes Insgiht Essence and Content if used in a triggered workflow (delete trigger)

Insight - STL Parser/ Insight -PAC Parser Activities: The STL parser activity and PAC parser activity are used for importing subtitles into Nexio Insight. The activity parses the subtitle file and returns a list of markers. This list is passed to the "Insight - Import Marker" activity. This activity supports several file formats (auto detect or selectable from a drop down).

The STL Parser automatically supports the EBU STL, Bugginmedia STL, PSB STL, and Spell STL file formats. Portuguese (and most other) characters are also supported.

Insight- Marker Importer: The Marker importer activity is used for importing markers into Nexio Insight. Now when parsing a file or a XML containing markers (content and/or essence), this information is converted into a list of markers for this activity. This activity can then create all these markers at once.

TextFileParserActivity: The Parse Text file activity is enhanced to read a CSV file on a CIFS share and returns a list of lines (a line is a list of cell). This allows processing the result in a ForEach activity (for each line) and then accessing the cells by index (currentLine(3)). • Activity Properties

Activity input properties: o File path: full UNC file path of the CSV file

Motion v4.7



o Username: (optional) CIFS credential o Password: (optional) CIFS credential

Activity output property:

o Result: List Of (Array of string) (something enumerable at least) • File Formats: The range of this activity is extended to various file formats. File format is

selected from a dropdown list:

CSV char separated field: a dedicated property allow the user to specify the separator. It

should support special chars like tab (\t for example) Advanced: a dedicated property allow the user to specify a regular expression

containing named groups, these groups are the fields returned The result is a list of rows. Row fields can be accessible by index.

The first Group object in the Match GroupCollection (at index 0) isn’t included in the CSVResult, because it represents the entire match.

If the regex pattern has named groups, the CSVResult columns use the name of the groups.

Example: Input: Regex: "(?<FileName>[^,]+),(?<FileSize>[^,]+),(?<FileVersion>[^,]+),(?<AssemblyVersion>[^,]+),(?<ProductVersion>[^,]+)" CSV:

Harris.AutoDAM.UI.Common.dll,139776,1.0.0.116,1.0.0.105,1.0.0.116 Harris.AutoDAM.UI.Controls.dll,354816,1.0.0.116,1.0.0.105,1.0.0.116 Result:

FileName FileSize FileVersion AssemblyVersion ProductVersion

Harris.AutoDAM.UI.Common.dll

139776 1.0.0.116 1.0.0.105 1.0.0.116

Harris.AutoDAM.UI.Controls.dll

354816 1.0.0.116 1.0.0.105 1.0.0.116

Insight - Get custom property value / Insight - Set custom property value: Nexio Insight content can have custom properties. This allows some customer specific metadata to be stored. For example, a customer wants to store the Quality Check result in a content property, but as this is not part of the built-in properties, by configuration, a custom one is added for them.

These workflow activities are about reading/writing the custom properties value. They allow workflow designers to access (read and update) the QC status of a Nexio Insight content from the workflow and can be used for any metadata (QC, attribute, etc.).

Motion v4.7



Get Files: Queries the motion database for files based on an assortment of filtering parameters. The GetFiles activity will return all files that match the specified criteria, regardless of whether or not they are closed.

• Motion 4.6 added a filter to the GetFiles activity so it can, optionally, return only the "closed" files. Values for this filter:

All Closed only (return only the “closed” files) Closed with Metadata extracted only

XML Parser: Nexio Motion 4.4 added support for allowing workflow designers to get data out of XML documents (variable or file) and use these data in a workflow. The activity has the following input parameters: • XML document: optional, variable containing the XML document. Not used if the XML

document is in a file. • XML filename: optional, full UNC path to the XML path. Not used if the document comes

in a variable. • XSLT document: XML transformation instruction to convert the XML document into

something the activity can understand. These data can have one level of nesting: for example a list of segments, each of them having their own data.

The activity returns a collection easily usable for each activity: Collection of Dictionary<String, String>

For example, each item of the collection represent a segment and the dictionary is a list of Key, value pairs containing the segment data.

XML Transform: This activity is used for transforming a XML string using a XSLT (template) document. It is added as an advanced workflow activity because it can be used for more than just Nexio Insight-related tasks. Example: Nexio Insight can be used for low-res proxy based timing/segmenting, but not having Insight Capture, D-Series can be updated with timing information by dropping a proper file (i.e. a transformed timing file) to a designated folder. • Activity Properties: Create a new activity to apply transformation to an XML string using

a XSLT document.\

In Properties: o XML data (string): xml to transform (not a file name, the xml is coming from a

variable)

o XSLT data (string): xslt used (not a file name) Out Properties:

o Transformed XML (string): result of the transformation

Advanced CommandLine Execute: Runs the specified command in a shell on the server system

(effectively opens command prompt, inserts the specified string and presses enter)

Motion v4.7



• Returns the process Exit code as an OutArgument, so this code can be tested in the workflows.

• Returns ActionState (JobStateEnum) as well as an error message to indicate if the EXE was not found or whatever reason prevented the activity to start it.

• Retrieves the StdOut and StdErr streams. The data written to these streams by the app is returned in two OutArgument<string>.

• Timeout in seconds: (Default = 1) A zero (0) value means the feature is disabled. If the value is > 0, the activity terminates the process after the timeout elapsed. The activity state is then Timeout.

Parse EDL: Creates the EDL object specified by the EdlXml string

Create EDL: Creates an EDL xml string based on a list of files (FileDescriptions)

• FileDescription: Path: Relative path BasePath: Endpoint base path

FullPath FullName Guid Id Name

Extension Size CreatedOn: DateTime ModifiedOn: DateTime?

IsClosed IsDeleted MetadataDescription: Metadata

o VF_FrameRate o VF_VideoEncoding

o VF_NumberOfFrames o VF_VideoBitRate o VF_NumberOfAudioTracks o VF_AudioBitRate

o VF_AudioEncoding o VF_Width o VF_Height o VF_Duration

o VF_DurationTC: Timecode o SGL_Status

Motion v4.7



o VF_StartOfMessage: Timecode o VF_EndOfMessage: Timecode o Guid FileId

o Metadata o Note

public Guid EndpointId public string Description

• Return string

Name Path Extension Size

Created on Modified on Is Closed

Create Final Cut XMEML: Create Final Cut Pro XML Interchange Format document based on Insight EDL. This activity converts an Invenio EDL to a Final Cut Pro XML. • Input parameters:

AddAudioPanEffect (if true, pan effect is added)

AudioTrackCount (if 0, no audio track will be created) Display Name Endpoint: (Required) Argument and constant with the IsParameter checkbox to be

consistent with the resource activities. Activity search for this endpoint in the DB for each ID and get the FileDescription internally. The activity's endpoint selection can use CIFS and Nexio endpoints.

Invenio Edl: enter a VB Expression IsEndpoint Parameter: checkbox Result: enter a VB Expression

When the basepath and path are null, the workflow activity returns: file://File Where the File is in the proper case(not all lower case)

Insight – Execute Macro: Executes an Insight Macro

MSSQL Database Request / ODBC Database Request

• The result of the “ForEach” activity is changed to the same type used by the SQL activity. (I.e. Use the same SQlResult type as the SQL activity.)

• The SQLResult type can retrieve the columns by name. A user can access the column of a SQLResult by name instead of by Index. So if the Select order is changed, the output doesn't change.

Motion v4.7



Operations The Workflow Controller is used to create, edit, publish, and execute IMotion4 workflows.

View Workflows Use the following procedure to view the workflow list.

Click to toggle the Show Workflows icon to show all workflows or only published workflows. • Show all workflows. (In the following example since the test Workflow has not been

published, it is displayed.)

• Show only published workflows. (In the following example Demo Workflow is shown

because it is published.)

Motion v4.7



Create a Workflow Use the following procedure to create a new workflow.

1. To create a workflow,

• From the toolbar click on the “New workflow” button

• Right click on Default and from the context menu select “New Workflow”.

2. In the Create New Workflow dialog…

• Enter the name of the workflow • Set the priority. This may be low to high (P1 - highest to P10 - lowest) • Select the root activity. Flowchart or Sequence. • Click “Create”. A new workflow with the selected properties is created.

Delete or Rename a Workflow Use the following procedure to delete or rename a workflow.

1. Toggle to show all available workflows.

2. Select/highlight the desired workflow.

3. To Delete a workflow:

• From the toolbar click on the “Delete” button

• Right click on desired workflow and from the context menu select “Delete”.

Motion v4.7



4. To Rename a workflow:

• Right click on desired workflow and from the context menu select Rename. Enter the new name.

Create a Workflow Group Use the following procedure to create a new workflow.

1. To create a workflow group:

• From the toolbar click on the “New Group” button • Right click on Default and from the context menu select “New Group”.

2. In the Create New Workflow Group dialog:

Motion v4.7



• Enter the name of the workflow group. • Click “Create”. A new workflow group is created.

3. Drag workflows in the list into the Workflow Group folder.

Workflow Designer has the ability to:

- Drag and drop a folder to another folder in the workflow tree.

- Drag and drop a workflow group into another workflow group.

Delete or Rename a Workflow Group Use the following procedure to delete or rename a workflow group.

1. Toggle to show all available workflows and workflow groups.

2. Select/highlight the desired workflow group.

3. To Delete a workflow group:

• From the toolbar click on the “Delete” button • Right click on desired workflow group and from the context menu select “Delete”.

• A “Delete Workflow Group’ confirmation dialog appears.

Click Delete to accept the action or Cancel to abort the operation After confirmation, all folder content (workflows and sub-folders) is deleted.

4. To Rename a workflow group:

• Right click on desired workflow group and from the context menu select Rename. Enter the new name

Motion v4.7



Edit a Workflow After the workflow is created, the designer is displayed and the user can edit the workflow. Or a designer can choose to modify an existing workflow. Perform activities in a specific sequence.

1. Drag and drop required activities from the toolbox to the designer. (e.g. Delay)

• (Option) Find an Activity: If you have an idea of the name of the activity, use ‘Find activity…’ to search among

available activities.

Note: The activity search box is automatically cleared after the user ‘drag and drops’ an activity (from the search result) to the workflow.

Specify the search parameter and then click the search icon ( ).

2. Connect with Arrows. (Select the icon. The arrow drag points are highlighted. Select a drag

point and drag the arrow in the required direction to connect.)

Motion v4.7



3. Perform edits as required. On the right panel of the designer, the user can edit several

workflow properties:

4. Activity Properties: Edit the properties of the selected activity

Motion v4.7



• In the workflow click on the icon of the Activity • Select the ‘Activity’ Property tab, and then…

Enter the name for the Activity

Enter the value for the Activity (e.g. 00:00:10)

5. Variables tab: Variables can be used to pass data between activities

• Select a variable and specify variables and VB expression:

• To add a Variable click the add icon ( ).

• To delete a Variable click the delete icon ( ).

6. Arguments tab: Arguments are the input and/or output of the workflow

• Use the dropdown to select values:

• To add an Argument click the add icon ( ).

• To add a Triggered Workflow Argument click the add icon ( ).

Motion v4.7



• To delete an Argument click the delete icon ( ).

7. Imports tab: Imported namespaces allow referencing a type without its full name. Currently assigned namespaces are listed.

• Use the dropdown to select new namespaces:

Motion v4.7



• To add a namespace click the Add button.

8. Click the Save icon ( ) on the toolbar to save the workflow.

Note: A warning message is displayed on attempting to close the Workflow Designer client before saving workflow changes.

Note: On workflow definition save, if the alerts are active, the system checks them and then hides them if all of the activities were updated. If there is an issue, a warning is displayed.

Note: Bad namespaces are detected on saving a workflow. To help identify the source a log message is added at the warning level in the Motion 4 Client module. It appears if any bad imports are detected after a workflow export.

Motion v4.7



To enter a VB Expression or other variable expression The following procedure broadly outlines the process for specifying VB Expressions for Activity parameters. This procedure uses Environment Variable as an example.

1. On the workflow image select an activity. The variable is displayed in the right pane.

2. (Option) To add Environment variables.

• From the screen header bar Click the Settings icon located in the upper right corner.

• On the System Settings & Environment Variables dialog select the Environment Variables tab. This is used to edit environment variables only.

• Click Add

3. Select a parameter and click the ‘…’ button.

4. The ‘Enter value for Expression’ dialog is displayed.

Motion v4.7



• The following folders are listed:

Activities: Output properties of previous activities. Arguments: Input/output parameters of workflow. Variables: Variable declared w/in workflow, but not accessible to outside.

Environment variables: Global variables for use across all workflows. These are read only, not writable.

A folder with a ‘+’ indicates assigned variables. The folder can be expanded and the variables displayed.

5. Specify the environment variables then click OK.

6. Click OK (or Cancel).

Import/Export Environment Variables Motion 4.6 and higher have the ability to import/export environment variables to an xml file from the Environment Variables tab.

1. On the workflow image select an activity. The variable is displayed in the right pane.

Motion v4.7



2. Select the gear button on the top right of the standalone application.

3. The System Settings & Environment variables popup dialog is displayed

4. To Import a predefined set of environment variables

Import button: Click to import an XML file of previously defined and saved environment variables. Browse to the location of the desired file, select the target file, and then click OK to import.

5. To Export environment variables

Export button: Click to export the current environment variables to an XML file. Browse to the desired save location, rename the file (as required), and then click OK to export the file. XML Format:

<EnvironmentVariables>

<Variable Name="EnvVar1" Value="1" />

Motion v4.7



<Variable Name="EnvVar2" Value="a" /> <Variable Name="EnvVar3" Value="" /> <Variable Name="EnvVar6" Value="" />

</EnvironmentVariables>

About Setting Priorities on Workflows The priority means nothing from a workflow stand point as long as it doesn’t share resources with another workflow. It is the role of the Resource Manager to manage these priorities.

The priority assigned to a workflow or a workflow instance is a data passed to the Resource Manager.

Every instance created from this workflow definition will have this default priority.

But the user can later change manually from Motion Monitor, the priority of a selected workflow instance.

When the priority of a workflow instance (from ProcessExplorer) is changed, the priority is propagated to the jobs that are already queued in the Resource Manager. This permits users to change a workflow’s priority when it becomes urgent.

Finding Workflows If the desired workflows are not found, try the following:

1. Make all workflows (published and unpublished) visible

2. Clear the filter box.

3. This should make all workflows visible. If the workflow still cannot be seen, try entering its

name to the filter box.

Motion v4.7



Provide priority to the API when starting an Amberfin transcode Workflow designers can assign a priority to a transcode job. Amberfin Transcode activities (Resource Activities: Amberfin EDLTranscode, Amberfin NativeTranscode, and Amberfin SimpleTranscode) are enhanced to have an additional Job Priority property. This priority is passed to the enhanced API.

For example , the Job Priority parameter is shown for Amberfin EDLTranscode setup.

The following description is taken from the Amberfin feature document: ControlJobPriorityGuide.pdf

setJobPriority(string jobID, int priority)

The jobId argument is a valid job UUID as returned from the transcode() or repurpose() ICRControl methods.

The priority argument is an integer value from 2311 to 231. Any value > 2000 will be treated as IMMEDIATE which may invoke special job handling behavior in future versions of iCR (e.g. automatic cancellation of a low priority running job to allow processing of the IMMEDIATE job). It is not recommended to use values > 2000 at this time.

The following table map illustrates how priority values are mapped to enumeration values within iCR:

Priority Enumeration

Less than or equal to -1000 LOW

-1001 to 0 MEDIUM

1 to 1000 HIGH

1001 to 2000 URGENT

Greater than 2000 IMMEDIATE

Motion v4.7



Staff Management and Task Creation With Workflow Designer the user can create Human Tasks. When a workflow reaches this point the workflow stops. In the Task Assignment window the user can check the available tasks. First the user assigns the task to him/herself. Then after finishing the task, the user updates the status and the workflow continues.

To create a Human Task Activity Use the following procedure to create a Human Task.

1. In the designer from the left side activities toolbox drag & drop a Human Task activity to the designer area.

2. Select the human task.

3. Enter the required properties on the right side Activity properties panel:

• Due Date, Name, and Status List. • Assignee List: (e.g. Insight Groups) • Description: Name of Insight>Security>Groups>”Task” • Due date: Specify system Date. (#dd/mm/yyyy#) • Input for Decision: Dictionary (of Tkey, Tvalve)

• Specify other parameters a required. (For details see To enter a VB Expression or other variable expression.)

For example, status items can be extended while designing the Human Task activity. Here is an example what should one insert into the ‘StatusList’ property:

o New System.Collections.Generic.List(Of String) From {"Status1", " Status2", " Status3"}

o These items will appear in the ‘Update Status’ dropdown, and the workflow logic can decide what should happen after a task has been updated.

Motion v4.7



Using a Device in a Workflow Use the following procedure to specify using a device in a workflow.

1. Navigate to the “Workflow” tab and open the workflow.

2. In the “Activities” list find the “CIFS Copy” activity and drop it below the delay activity, and link it:

3. In the “Activity properties” area, select your device for both Source and Target properties:

4. Select the _SourceFileName property and click the ellipse button on the right to open the

Variable selection box:

5. Select the “MediaId” argument, and then click OK.

Motion v4.7



6. Fill in _SourcePath and _TargetPath with double quotes:

7. Fill in the _TargetFileName property with the string: MediaId + “-“

8. Save the new workflow and test it by passing the name of an existing file (in your device

folder).

• After 30 seconds, the file is copied and the new filename will have a dash appended to the extension.

• After few seconds the new file is listed in the Storage Explorer.

Set a Workflow to Start Automatically Most of the time you want to automate task as much as possible. Use the following procedures to set your workflow to start automatically when a new file is detected.

Prepare your workflow 1. In the Workflow tab, first create a copy of your existing workflow:

Motion v4.7



2. Name the new copy “My first automatic workflow”.

3. To automatically start a workflow when a file is detected it must have some special

parameters. Add these parameters in the Arguments area.

4. Two parameters are created:

• ChangeLog: that will carry the file event type (Created, Closed, Updated or Closed) • MediaFile: that will carry the file information (Path, Name, Extension, Size, etc.)

5. Delete the Delay activity and replace it with the Assign activity:

Motion v4.7



6. To assign a new value to a variable write the filename and extension carried by the

“MediaFile” variable to the previous “MediaId” variable. By doing so we don’t have to change the “CIFS Copy” activity that already uses the “MediaId” variable.

• In the “To” property (in the activity box or in the “Activity properties” area) write: MediaId.

• In the “Value” property, write: MediaFile.Name + “.” + MediaFile.Extension

7. Save your workflow

Publish and Execute a Workflow When a workflow is selected, the user can choose actions from the top menu or from the right click context menu.

• Publish can only be executed if the workflow is saved to the server. • Execute with real-time tracking.

Publish a Workflow If a workflow is created or modified, it is not ready for use by everybody. It can be tested from designer, but it must be published for everybody to use it. If this workflow is a sub-workflow or a

Motion v4.7



workflow for trigger in the resource repository, then apply the changes on each sub-workflow or trigger.

Until your workflow is published, you can only run it from the designer.

To make your workflow available to other parts of the system, it must be published. This is equivalent to telling the system: “I’m confident my workflow will work because I tested it. I want to put it in production”.

Click the “Publish” button in the toolbar:

Important: Every time a workflow is changed the new version must be published. Until this is done, the previously published version will continue to be used by other parts of the system.

Use the following procedure to publish a workflow.



3. To Publish a workflow:

• From the toolbar click on the “Publish” icon .

• Right click on desired workflow and from the context menu select “Publish”.

4. This makes the workflow available for use.

Execute a Workflow Use the following procedure to execute a published workflow.

Circular Reference Note: The operator is warned when circular references are created using the Execute Workflow activity. (e.g. : Workflow A calling workflow B / Workflow B calling workflow

Motion v4.7



A). While this may be useful in some very specific cases, the user now receives notification at the time of publishing the second workflow if a cross reference has been created.



3. To Execute a workflow:

• From the toolbar click on the “Execute” icon . • Right click on desired workflow and from the context menu select “Execute”.

4. To execute a workflow, click the “Execute” button on the top menu.

5. Set properties as required in the Execute Workflow dialog:

• The user can override the default priority of the workflow, set the number of instances to start, and set the preferred execution mode:

Execute the workflow immediately with the overridden priority. If the workflow is published, a schedule can be created: the workflow will be

executed at the scheduled time with the default priority. The following screen shots illustrate the variety of parameters that can be available depending on the workflows construction:

Motion v4.7



6. After these properties are set, fill the values of the workflow arguments (if any) and click

“Execute” to start the workflow.

7. Tracking the Workflow: A workflow started from the workflow designer is always tracked. The Workflow Tracker window is resizable.

Motion v4.7



How Workflows Appear to a User A number of workflows can be initiated such as archiving, transcode, exporting to a non-linear editing system, or retrieving from archive from within the Insight system, the Storage Explorer from Motion4 client, or other systems that subscribe to Motion’s workflows

Workflows can be defined by the administrator using Motion and the Insight Config tool, and after a workflow has been defined, it can be initiated from the folder system, search tools, document forms, Baseband and Clip Editor. For more details of how these workflows are accessed refer to the Insight User Guide.

Pre-Configure Workflow Macros Before initiating a workflow, workflow macros must be pre-configured using Content Handler and Insight.

Create, Modify and Delete an Action After configuring one or more macros, actions can be created, modified and deleted in Insight.

The Action Details Dialog The Action Details dialog provides Status, Input, and Output tabs for displaying an action's details. This allows an operator to easily see the Ins and Outs of actions, but also get the job ID to search in Magellan DL; the Job ID is used as a suffix for the action logs. The UI allows copying the individual displayed data to the clip board (job ID, filename in the input, etc.)

Motion v4.7



Status tab: This tab displays the Action Display name, Activity Name (FTP transfer, etc.), Job ID, Action ID, current message and progress (same as in the list). Datetimes are displayed in regional format.

Input tab: This tab displays the action inputs and endpoints (location\device name\endpoint

alias). The user can check the endpoint parameters in the Resource Manager.

The following examples show CheckID with one endpoint (left) and CheckID with multiple endpoints (right).

Output tab: When the action is done, this tab displays the outputs

Motion v4.7



Create an Action Nexio® Insight allows users to create new actions using the Action Config tool. After an action has been created, it can be initiated from various locations in Nexio Insight immediately.

Use the following procedure to create a new action.

1. Start Nexio Insight and log in as an administrator.

2. In the menu, select System Customization > Action Config. The Action Config tool opens in the workspace.

3. In the Operations group click on CreateAction, enter a name for the new action. This can be any name, but it is recommended to choose a descriptive name.

4. Select which workflow should be used for the new action in WorkflowConfig.

5. Associate the workflow parameters to….

• “Insight Object” means the workflow’s argument is mapped to one of the properties of the selected Insight document (Content, Essence…)

• “Constant” fills the argument with a predefined value • “Prompt” shows a custom form that gives the possibility to enter the value of the

argument when the workflow is being initiated.

• In case of “Not used” the Argument is ignored • Selecting “ID Generator” creates an automatic Parameter for the selected Argument by

using an IDClass.

6. Click on Save Actions.

Action Processing: During operation, users can determine if an action is already processing (sent to the device), or still queued in the ResourceManager queue, by reviewing the icon in the Action list. In Action list, the icon and test for the action reflects if the action is still in the queue and not yet in the device.

Modify an Action Nexio Insight allows users to modify actions as necessary using the Action Config tool. Actions can be modified by selecting a different workflow from the Workflows dropdown list and/or changing action parameters in the Arguments section.

Motion v4.7



Use the following procedure to modify an existing action.

1. In the menu, select System Customization > Action Config. The Action Config tool opens in the workspace.

2. Click Own Actions/Inherited Actions (readonly)/ Group related (only for admins) in the Context panel to display the corresponding actions that have been pre-configured.

3. In the Action List click to highlight an action to modify.

4. Modify the workflow and/or parameter information as necessary.

5. Click Save Actions to save your modifications.

Delete an Action Nexio Insight allows users to delete actions using the Action Config tool if they are no longer needed. Use the following procedure to delete an existing action.

1. In the menu, select System Customization > Action Config. The Action Config tool opens in the workspace

2. Click Own Actions / Group related(only for admins)in the Context panel to display the corresponding actions that have been pre-configured.

3. Click to highlight an action to delete.

4. Click the Delete button. The action is removed from the list of available actions.

Configure Action Parameters Configuring action parameters is specific to each action and the associated Motion4 workflow. The available action parameters are determined by the associated Motion4 workflow and the information that is required to perform an action.

For example, when configuring an action to send a media to archive, the Media ID property might be the only information required to carry out the workflow. Using the Nexio Insight Action Config tool, administrators can determine how this Media ID is defined. For instance, it may be the Content House ID or the Essence House ID value or the User may be prompted to enter the information. Ultimately, these parameters are defined specific to each customer workflow.

When a workflow is selected for an action, the workflow parameters are automatically displayed in the arguments field.

Motion v4.7

Operations Reference Scheduling and Triggering Workflows


Scheduling and Triggering Workflows

Schedule Workflow Operations The Schedules module allows users to schedule workflows for one time run or on a daily basis. From the menu bar a user can add, edit and delete schedule items.

Schedule a Workflow Use the following procedure to schedule a Workflow.

1. Select the Schedules tab

2. From the toolbar select the Add New Schedule icon ( ).

3. From the dropdown select a workflow from the list of available workflows.

4. On the Execute Workflow dialog specify the following parameters:

• Priority: If required change the default priority. (P1 – P10) • Workflow name: Specify the workflow name.

• Specify the schedule start date. Click the down arrow to specify from a calendar view. Or use the scroll arrows to increment or decrement date by day.

• Specify Frequency: Once or Daily. • MediaId: Specify the Media ID.

Motion v4.7



5. When finished click Schedule. Workflow appears on the schedule pane.

Update a Scheduled Workflow Use the following procedure to update a scheduled a Workflow

1. Select the Schedules tab.

2. Selected a currently scheduled workflow on the schedule pane.

3. From the toolbar select the Update Schedule icon ( ). The Update Schedule dialog is displayed.

4. On the Update Schedule Workflow dialog modify the following parameters are required:

• Workflow name: Specify the workflow name.

Motion v4.7



• Schedule start date: Click the down arrow to specify from a calendar view. Or use the scroll arrows to increment or decrement date by day.

• Frequency: From the dropdown select Once or Daily. • MediaId: Specify the Media ID.

5. When finished click OK. The workflow schedule is updated.

To Delete a Scheduled Workflow Use the following procedure to delete a scheduled workflow that is no longer needed.

1. Select the Schedules tab

2. Selected a currently scheduled workflow on the schedule pane.

3. From the toolbar select the Delete Schedule icon ( ).

4. A Confirm delete dialog is displayed.

5. Click Yes to delete the schedule.

Workflow Trigger Operations The role of Motion is to automate as many tasks as possible. To do so, workflows can be automatically started. Several events can trigger a workflow execution:

A file event: This is when a file is created, updated or deleted on a storage.

A storage capacity event: This is when the storage remaining capacity drops below a configured level.

A schedule: This is usually for maintenance purpose. The workflow can be set to run on a regular basis (every Sunday at midnight for example).

A human intervention: This is auctioned either through task driven assignments or through a human decision based around using a function such as search, project creation, etc.

Note: For information on configuring a workflow to run automatically see: Set a Workflow to Start Automatically.

Motion v4.7



Configure a Trigger 1. Navigate to the “Resources” tab. And select your device’s “CIFS Connection”. In the

Parameters area, Triggers group, select (check) the trigger(s) to use. In the example graphic “Close” is selected.

• Create trigger starts a workflow as soon as a new file is detected

• Update trigger starts a workflow when a file starts to be modified • Close trigger starts a workflow only when the created or modified file is closed (nothing

is written to the file anymore)

• Delete trigger starts a workflow when a file is deleted • Override job priority: Optionally, a job priority override can be set for each trigger type.

This option becomes enabled when its associated trigger type is selected.

2. Select the workflow to start for the selected trigger. In the example graphic a workflow is

selected for Close trigger.

If your workflow isn’t listed in the dropdown list:

• Try refreshing the resource tab by clicking the refresh button:

WARNING: All unsaved changes will be lost, so save your bin before performing this action.

• Maybe you forgot to add the mandatory arguments

• Maybe you forgot to publish your workflow

3. Leave the two parameters empty.

4. Save your bin and publish it.

Motion v4.7



Test the trigger Add a new file to the device’s folder. After few seconds, it will appear in Storage Explorer.

Notice that the column for the selected trigger, (e.g. “Is Closed”), is set to “No”.

After few seconds, this column turns to “Yes”.

You can then go to “Process Explorer” and see the new workflow instance started by your trigger.

Motion v4.7

Operations Reference Motion4 Monitoring


Motion4 Monitoring

About Monitoring The Motion Monitor allows an operator to monitor tasks, devices, files status, and the status of a particular workflow or set of workflows. It gives an overview of all the staff, applications, and devices that form part of the infrastructure set which deliver the workflows and processing capability of tasks and workflows.

The Process and Storage Explorer graphical components are present in both in Motion4 standalone client and Insight Client. They allow an operator to monitor tasks, devices, files status, and the status of a particular workflow or set of workflows.

The ability to monitor appears at a macro level for system administrators or those in the role of MCR operator, where their ability to look at all workflows and devices to which they have security rights.

Note: An individual user can monitor workflows they have requested through the Insight UI.

Global Monitoring When integrated with Insight, the UI allows administrators and operational staff to monitor all workflows and devices across the organization based on their security privileges. In the following image Process Explorer is launched.

Motion Plugins in Nexio Insight The Storage Explorer, Process Explorer, and the Tasks module can be referenced in Nexio Insight. They are shown differently for admin and ordinary users. The following screen shot illustrates how Motion4 plugins appear in Nexio Insight:

Motion v4.7



Transfer Monitor

Motion v4.7



Task Manager

Reports

<This functionality is targeted for a future release. The information presented here is for reference only.>

Motion v4.7



Workflow Monitoring In the Process Explorer UI there is a list of workflow types (definitions); the user can select one or more types to monitor. List of instances is then filtered based on the user’s selection. For each workflow instance a user can see the priority, status of workflow, progress of current activity on device, who started this workflow, and when it was started.

Motion v4.7



Monitoring Device Status In the Published part of Resource Repository a user can view the health-check statuses of all devices. Colored pictograms provide visual feedback of the state of each device in system.

A green pictogram indicates the device is operating normally.

A red pictogram indicates the device is malfunctioning, then the device is marked with,

Monitoring Device Storage Status and Files on Devices In Storage Explorer UI is a list of spied storages, for each device a media base is built with the list of all files on storages. For each media file an extensive set of metadata is extracted and presented to the user.

Also the volume of storage use by device can be displayed.

Motion v4.7



Process Explorer Operations The Process Explorer page is used to monitor workflow instances (aka processes) in the system. This page provides a snapshot about the system and is automatically refreshed every few seconds. The explorer shows workflow instances which are in running, done, failed, etc. state as a live feed, so it gives an idea what is happening right now. It is also serves as a history. The user can watch the log, errors and progress of different jobs which are being executed on devices.

Process Explorer is composed of 3 parts:

The left pane lists available workflows. The operator can select to display all or one particular process and display their requests in the center pane.

The center pane displays all requests for all or a selected process. By default, instances are ordered by ‘created date’.

The right pane displays details of the checked requests (action progression, history, Event Details). These are read-only information, but the Priority can be changed. Note: Changing priority will not affect activities which are running or already done.

Motion v4.7



Diagnostic Logging Default Settings With Motion 4.7 and higher the following are default settings for Process Explorer Diagnostic Logging:

Max storage: 4GB

file rolling size: 1GB

default verbosity: all but info and debug

This also means that no other verbosity settings are overwritten.

Using Process Explorer Depending on the status of a selected request, the operator has the capability to pause, resume and abort a request.

Multiple item selection is available by holding SHIFT or CTRL keys while clicking on items.

Find Workflows

1. Specify a workflow in the “Find workflow” field and then click the search icon.

2. Check All workflows to display all workflows, or from the list of found workflows select the individual workflow(s) to display.

Filter workflows There are some filtering options to help finding the appropriate process (like only published, done, failed, aborted, running, etc.) It is also possible to:

Select only one or several processes to monitor, or filter for date.

Search by MediaId in Process Explorer.

This has been addressed by adding new icons: Restart ( ) a process

Edit Parameter and Restart ( ) a process.

Motion v4.7



Sort workflows by date It is possible to sort the display of workflows by date Modified date/time.

On the Modified column click the arrow to toggle the sort of workflows.

Change a Workflow’s Priority When the priority of a workflow instance (from ProcessExplorer) is changed, the priority is propagated to the jobs that are already queued in the Resource Manager. This permits users to change a workflow’s priority when it becomes urgent.

Right click Context menu

1. Select a workflow.

2. Right click and from the context menu select Change Priority.

3. From the expanded options select the desired priority level.

Restart a Workflow In Motion 4.6 and higher the restart button in the ProcessExplorer offers a dropdown for restarting a workflow version.


1. Select a workflow request.

Motion v4.7



2. Right click and from the context menu select Restart.

Restart Button Operation

Clicking on the Restart button starts the ‘default’ action.

Clicking on the drop down button provides the following options:

• Default: Restart the workflow using the latest published version (if the argument list didn't change, otherwise fallback to second case)

• Restart the workflow using the latest published version, but allow the user to review and edit the parameters before starting a new instance.

Edit Parameter and Restart a process.

Clicking on the Edit Parameter and Restart button restarts the modified action.

When restarting a workflow, editing the parameters, the execute dialog is pre-filled with the previous parameters.

Workflow Actions

Published Workflows: The latest published version of a workflow is used when restarting an instance from a published version.

Editing Workflows: The latest version of the workflow being edited is used when restarting an instance from an editing version. (i.e. not published).

Review requests 1. From the left pane select an available workflow (or multiple workflows).

2. Requests associated with the workflow process(es) are displayed their in the center pane.

Pause a request 1. Select/highlight a running request

2. From the ribbon bar select « Pause ». All requests are paused for the selected process.



2. Right click and from the context menu select Oause.

Resume a request 1. Select/highlight a paused request.

2. From the ribbon bar select « Resume ». All requests are for the paused process are resumed.



Motion v4.7



2. Right click and from the context menu select Resume.

Abort a request 1. Select/highlight a request

2. From the ribbon bar select « Abort ». All requests are for the process are aborted.



2. Right click and from the context menu select Abort.

Review request details 1. Select/highlight a request

2. The right pane displays details of the checked requests:

• Actions tab view displays the action progression • History tab view displays past actions for the selected request • Event Details tab view displays specifics on the event selected in the Actions or History

tab.

Storage Explorer Operations Storage Explorer is responsible for monitoring spied MediaFiles on storage devices. Devices and their connections which support spying are displayed in this module and are available for checking their content. It is also possible to execute a very simple search for media name.

Incremental spy feature: Nexio Motion 4.4 added incremental spy action support for devices, such as archive that have an API allowing partial retrieval of the inventory. Based on the date of the last item in the Database, the Device Controller asks only for "what's new since...". The incremental spy action is performed as required, while a full spy action is scheduled every night.

Devices, their MediaFile contents, and their metadata are shown in a read-only manner. A user can browse a huge number of MediaFiles, or can search for them (search functionality is limited). Also the Actions (set up in ActionConfig) can be managed and executed from here.

Storage Explorer is a read-only viewer, which does not allow modifying files, folders, nor file properties. It supports huge number of files; there is no exact limit of the maximum. The file list is refreshed automatically by default every 2 seconds, giving nearly live information.

It is present in both in Motion4 standalone client and Insight Client, and allows an operator to monitor storage devices and file status.

This window is composed of 4 parts:

Motion v4.7



The left pane shows the configured servers and their capacities. For each server, the remaining capacity, total capacity and status are displayed. The operator can click on desired server to display all media information in the center part.

The center pane displays media information for the selected server/path in the left part. The title of this window displays the name and eventually the path of the selected server. The operator can select a media and drag and drop this media in another device/Path destination or execute a local action right clicking on this media.

The right panes displays metadata for the selected File and Content if HS media file is installed.

Using Storage Explorer 1. Select the Storage Explorer tab.

2. Open a Connection from the left pane by double-clicking on a storage. The contents are displayed in the center pane.

3. (Option) Click the Search icon. The Search Results are displayed.

4. Select a MediaFile in the center pane. The details are displayed in the right panels (File Details and Content Properties). This information is generated by the Extended Metadata Extractor during spy process.

• Some files can be extracted (mostly video files), but others will contain only basic file information, such as name, created time, extension, etc.

• Files before and under extraction also show basic information. • Extended metadata is available only after the file is closed.

Motion v4.7



Filter for properties It is also possible to filter for certain properties such as name, extension, created date, modified date, size. By default the file sort order in Storage Explorer is by Name in Ascending order.

Execute an Action This module gives access to the Action Config Management. Users can execute Actions (set up in ActionConfig) on one or more MediaFiles by selecting them.

For details on using the Action Config Management console see section System Management > Action Configuration.

Task Assignment Operations On the Task Assignment page a user can observe and manage the human tasks created by the ‘Human Task’ action found in the ‘Human Activities’ group in the workflow toolbox.

This module shows the human tasks and the user’s that can manage them. In the Task Assignment UI a user can track list of tasks that he can assign to himself and a list of tasks already assigned to him. Using this UI the user can assign tasks to himself, un-assign tasks he can’t accomplish, or finish tasks.

Example if User view:

Example of Admin View: Note the available filter options.

Motion v4.7



Using Task Assignment Typically a task is assigned to a group of users. The first user action is to assign the task.

1. User reviews available tasks. The following filters are available for admin users; a limited set is available to normal users:

• Assignable to me

• Assigned to me • Assigned or assignable to anyone

2. User assigns a task to himself/herself and then notifies other members of the group that he/she will do this task.

• The user can un-assign tasks he/she cannot accomplish.

3. The Info panel describes the task to perform.

4. Once the task has been completed, the user returns to this panel, selects the task, updates the status (fills in the comment, the execution time and the final status of the task), and then saves it by selecting ‘Finish Task’.

5. This status is then tested in the workflow to decide what to do next.

Motion v4.7

Operations Reference System Management


System Management

System Settings Settings module is used to perform a system backup or to restore a system.

To Launch System Settings 1. Select the gear button on the top right of the standalone application.

2. The System Settings & Environment variables popup dialog is displayed.

3. Select the About tab to view the product name copyright, client and server versions.

4. Select Environment Variables tab to view currently set variables.

5. Select the System Settings tab. There are only two functionalities available to access:

• System Backup • System Restore

Motion v4.7



6. Select ‘Backup System’ or ‘Restore System’.

• Navigate to the Restore/Backup file and click Open. • A confirmation dialog is displayed. Select ‘Yes’ to continue or ‘No’ to abort the action.

• The progress dialog is displayed showing the progress and messages, and with the ability

to abort the current process.

By initiating a process, the process will get an Id and by polling this process using the Id the user gets the real time progress.

Both Backup and Restore process happens on the server, the client only uploads or downloads the file, which is created or used. That is why there is a different state for upload/download.

Action Configuration Actions are basically shortcuts to workflows, which can be executed on certain MediaFiles. These Actions can be saved on the server to make it accessible to all users.

Motion v4.7



Actions have a name, some associated connections (on which they can be executed), and an associated workflow. The user can map certain information to input arguments of the associated workflow. These mappings are completed by the client when executing the action and the actual MediaFile properties are substituted.

For Example: "Endpoint” allows a user to pass the Endpoint of the file that is selected to the workflow. The data is of type AddressBase to be passed directly as a variable to the resource activities.

The available mappings can be seen the following screenshot:

These Actions are not the same Actions available in Nexio Insight Client. Nexio Insight Actions are saved in Nexio Insight server, not Motion4 server.

Open the Action Config Management console

1. From the toolbar select the Action Configuration icon.

2. Select Action Configuration from the dropdown

Motion v4.7



Create a new action

1. On the Action Config Management dialog click the ‘create new action’ icon. . The dialog is populated with default settings.

2. In the Name field specify the name of the Action

3. Click the add icon in the center pane to associate a Storage Device with the action. From the dropdown choose select a specific device or “Select all” for all devices, and then click Add.

Motion v4.7



4. Option: To delete an associated Storage device, select a device in the center pane and then

click the minus icon .

5. LaunchWorkflow: Click the dropdown to choose from a list of available workflows.

6. Workflow parameters. When a workflow is selected parameters specified for that workflow

are listed. These parameters can be modified as required.

7. Select the dropdown list for the workflow parameter and choose a parameter/endpoint.

8. The final action will reflect all defined settings.

Motion v4.7



Make a copy of the Action Use an existing action as a template to speed up the creation of new Actions.

1. Click the copy icon.

2. This copy can then be renamed and new devices associated and workflows specified.

Create an AddressBase from the endpoint alias In addition to the current ability to create an AddressBase object by providing a Guid, Motion 4.6 and higher includes a static method for creating an AddressBase object from an Endpoint Alias.

New EndpointAddress with {.EndpointAlias = "xxx" }

The endpointalias property is case insensitive

Where, xxx = A unique alias name.

The following graphic illustrates the location of the EndPointAddress parameter.

Example 1: {.EndpointAlias = " xyz" } Depending on its designation…

• xyz will give back just the first endpoint which name is xyz, and which will be the first depending on theSQL server collation.

Or

Motion v4.7



• xyz can be everything that the user gives on the resource repository

Example 2: {.EndpointAlias = "shared" } will get a list of published endpoints.

Motion v4.7

Operations Reference Appendix A: NET Framework and Visual Basic Reference


Appendix A: NET Framework and Visual Basic Reference

Background The following information is provided as a general reference to NET Framework and Visual Basic. It assumes the reader has fundamental experience with these application/programming language.

What is the .NET Framework? The .NET Framework is a managed execution environment that provides a variety of services to its running applications. It consists of two major components:

the common language runtime (CLR)

.NET Framework Class Library

All managed languages in the .NET Framework, such as Visual Basic and C#, provide full support for object-oriented programming including encapsulation, inheritance, and polymorphism.

What is object-oriented programming? It is a programming paradigm that represents concepts as "objects" that have data fields (attributes that describe the object) and associated procedures known as methods. Objects, which are usually instances of classes, are used to interact with one another to design applications and computer programs.

Classes and objects The terms class and object are sometimes used interchangeably, but in fact, classes describe the type of objects, while objects are usable instances of classes. So, the act of creating an object is called instantiation. Using the blueprint analogy, a class is a blueprint, and an object is a building made from that blueprint.

Types in the .NET Framework Value types: Variables that are based on value types directly contain values. Assigning one

value type variable to another copies the contained value.

Motion v4.7



• Structures • Enumerations

Reference types: A reference type has a pointer which points to the memory location where

the actual data stored. • Classes

• (Interfaces) • (Delegates)

Classes and structures Classes and structures are both container types, meaning they hold other types as members. A container type is useful for gathering a set of data items, such as customer information, that is closely related but cannot be held in a single elementary type. A class or structure can contain data members to hold these items and code members to manipulate them. The members can then be referred to individually, or the container can be treated as a single entity.

Motion v4.7



. NET Framework Class Library (FCL) The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime.

Types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access.

The FCL is organized into Namespaces.

Namespace Software projects consist of several pieces of code such as classes, structures, etc., known as the components. The number of these components can be very large. These components can be grouped into categories. This logical grouping construct is known as a Namespace. In a Namespace the groups of components are somehow related to each other. Namespaces are similar in concept to a folder in a computer file system. Like folders, namespaces enable classes to have a unique name or we can say that it is a logical naming scheme for grouping related types.

Commonly used namespaces in Workflow Editor

FCL reference: http://msdn.microsoft.com/en-us/library/gg145045(v=vs.100).aspx

Structures

Numeric types

Integral types

VB Alias Type Range Size Type Char

SByte System.Sbyte -128 to 127 Signed 8-bit integer -

http://msdn.microsoft.com/en-us/library/gg145045(v=vs.100).aspx

Motion v4.7




Byte System.Byte 0 to 255 Unsigned 8-bit integer -

Short System.Int16 -32,768 to 32,767 Signed 16-bit integer S

UShort System.UInt16 0 to 65,535 Unsigned 16-bit integer US

Integer System.Int32 -2,147,483,648 to 2,147,483,647 Signed 32-bit integer I

UInteger System.UInt32 0 to 4,294,967,295 Unsigned 32-bit integer UI

Long System.Int64 -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807 Signed 64-bit integer L

ULong System.UInt64 0 to 18,446,744,073,709,551,615 Unsigned 64-bit integer UL

Char System.Char U+0000 to U+ffff Unicode 16-bit character C

Floating-point types

VB Alias Type Approximate range Precision Type Char

Single System.Single -3.4 × 1038 to +3.4 × 1038 7 digits F

Double System.Double ±5.0 × 10−324 to ±1.7 × 10308 15-16 digits R

Decimal

VB Alias Type Approximate range Precision Type Char

Decimal System.Decimal (-7.9 x 1028 to 7.9 x 1028) / (100 to 28) 28-29 significant digits D

Boolean: Represents a truth value, typically the result of a relational or logical operation. The literal is of type System.Boolean. The default value of the Boolean type is equivalent to the literal False.


Boolean System.Boolean True or False 1 byte -

Date: Represents a date and/or a time and maps to System.DateTime. The default value of the Date type is equivalent to the literal # 01/01/0001 12:00:00AM #.

Char: Represents a single Unicode character and maps to System.Char. The default value of the Char type is the “null character”.

Enumerations An enumeration (enum) is a special form of value type, which supplies alternate names for the values of an underlying primitive type. An enumeration type has a name, an underlying type,

Motion v4.7



and a set of fields. The underlying type must be one of the built-in signed or unsigned integer types (such as Byte, Int32, or UInt64). The fields are static literal fields, each of which represents a constant.

Literals A literal is a textual representation of a particular value of a type. Literal types include boolean, integer, floating point, string, character, and date. Literals can be treated as instances of their corresponding types.

Boolean literals: True and False are literals of the Boolean type that map to the true and false state, respectively.

Integer literals can be decimal (base 10), hexadecimal (base 16), or octal (base 8). A decimal integer literal is a string of decimal digits (0-9). The type of a literal is determined by its value or by the following type character. If no type character is specified, values in the range of the Integer type are typed as Integer (System.Int32); values outside the range for Integer are typed as Long (System.Int64).

A floating-point literal is an integer literal followed by an optional decimal point (the ASCII period character) and mantissa, and an optional base 10 exponent. By default, a floating-point literal is of type Double. If the Single, Double, or Decimal type character is specified, the literal is of that type.

A string literal is a sequence of zero or more Unicode characters beginning and ending with a double-quote character. Within a string, a sequence of two double-quote characters is an escape sequence representing a double quote in the string. A string constant is of the String type.

A date literal represents a particular moment in time expressed as a value of the DateTime type. The literal may specify both a date and a time, just a date, or just a time. If the date value is omitted, then January 1 of the year 1 in the Gregorian calendar is assumed. If the time value is omitted, then 12:00:00 AM is assumed. To avoid problems with interpreting the year value in a date value, the year value cannot be two digits. When expressing a date in the first century AD/CE, leading zeros must be specified. A time value may be specified either using a 24-hour value or a 12-hour value; time values that omit an AM or PM are assumed to be 24-hour values. If a time value omits the minutes, the literal 0 is used by default. If a time value omits the seconds, the literal 0 is used by default. If both minutes and second are omitted, then AM or PM must be specified. The compiler treats literals enclosed within number signs (# #) as DateTime.

A character literal represents a single Unicode character of the Char type. Two double-quote characters is an escape sequence representing the double-quote character.

Visual Basic Operators Full list of available operators in Visual Basic: http://msdn.microsoft.com/en-us/library/asfcc119(v=vs.100).aspx

http://msdn.microsoft.com/en-us/library/asfcc119(v=vs.100).aspx

http://msdn.microsoft.com/en-us/library/asfcc119(v=vs.100).aspx

Motion v4.7



Assignment Operators = Operator:

Assigns a value to a variable or property.

• variableorproperty = value

variableorproperty: Any writable variable or any property. value: Any literal, constant, or expression.

Remarks: The element on the left side of the equal sign (=) can be a simple scalar variable, a property, or an element of an array. The variable or property cannot be ReadOnly. The = operator assigns the value on its right to the variable or property on its left.

Arithmetic operators

+ Operator (unary and binary) : Adds two numbers or returns the positive value of a numeric expression. Can also be used to concatenate two string expressions.

• expression1 + expression2 or + expression1

expression1: Required. Any numeric or string expression. expression2: Required unless the + operator is calculating a negative value. Any

numeric or string expression.

Result:

• If expression1 and expression2 are both numeric, the result is their arithmetic sum. • If expression1 is absent, the + operator is the unary identity operator for the unchanged

value of an expression. In this sense, the operation consists of retaining the sign of expression2, so the result is negative if expression1 is negative.

• If expression1 and expression2 are both strings, the result is the concatenation of their values.

- Operator (unary and binary) : Returns the difference between two numeric expressions or the negative value of a numeric expression.

• expression1 - expression2 or - expression1 expression1: Required. Any numeric or string expression. expression2: Required unless the - operator is calculating a negative value. Any

numeric expression.

Result: The result is the difference between expression1 and expression2, or the negated value of expression1.

Motion v4.7



* Operator: Multiplies two numbers.

• number1 * number2 number1: Required. Any numeric expression. number2: Required. Any numeric expression.

Result: The result is the product of number1 and number2.

^ Operator: Raises a number to the power of another number.

• number1 ^ number2 number1: Required. Any numeric expression. number2: Required. Any numeric expression.

Result: Double. Operands of any different type are converted to Double.

/ Operator: Divides two numbers and returns a floating-point result.

• number1 / number2 number1: Required. Any numeric expression. number2 : Required. Any numeric expression.

Result: The result is the full quotient of number1 divided by number2, including any remainder.

\ Operator: Divides two numbers and returns an integer result.

• number1 \ number2 number1: Required. Any numeric expression. number2: Required. Any numeric expression.

Result: The result is the integer quotient of number1 divided by number2, which discards any remainder and retains only the integer portion.

Mod Operator: Divides two numbers and returns only the remainder.

• number1 Mod number2

number1: Required. Any numeric expression. number2 : Required. Any numeric expression.

Result: The result is the full quotient of number1 divided by number2, including any remainder.

Motion v4.7



Comparison Operators The following are the comparison operators defined in Visual Basic:

< (Less than)

<= (Less than or equal to)

> (Greater than)

>= (Greater than or equal to)

= (Equal to) (= Operator is also used as an assignment operator.)

<> (Not equal to)

result = expression1 comparisonoperator expression2

result: Required. A Boolean value representing the result of the comparison.

expression1, expression2: Required. Any expression.

comparisonoperator: Required. Any relational comparison operator.

Like Operator: Compares a string against a pattern.

• result = string Like pattern result: Required. Any Boolean variable. The result is a Boolean value indicating

whether or not the string satisfies the pattern. If both string and pattern are empty strings, the result is True.

string: Required. Any String expression. Pattern: Required. Any String expression conforming to the pattern-matching

conventions.

Characters in pattern Matches in string

? Any single character

* Zero or more characters

# Any single digit (0–9)

[ charlist ] Any single character in charlist

[! charlist ] Any single character not in charlist

Logical Operators

And Operator: Performs a logical conjunction on two Boolean expressions.

Motion v4.7



• result = expression1 And expression2 result: Required. Any Boolean expression. Result is the logical conjunction of two

Boolean values. expression1: Required. Any Boolean expression. expression2: Required. Any Boolean expression.

• For Boolean comparison, result is True if and only if both expression1 and expression2 evaluate to True:

If expression1 is And expression2 is The value of result is

True True True

True False False

False True False

False False False

Or Operator: Performs a logical disjunction on two Boolean expressions

• result = expression1 Or expression2 result: Required. Any Boolean expression. result is the inclusive logical disjunction of

two Boolean values.

expression1: Required. Any Boolean expression. expression2: Required. Any Boolean expression.

• For Boolean comparison, result is True if and only if both expression1 and expression2 evaluate to True:

If expression1 is And expression2 is The value of result is

True True True

True False True

False True True

False False False

Not Operator: Performs logical negation on a Boolean expression

• result = Not expression

Motion v4.7



result: Required. Any Boolean expression. expression: Required. Any Boolean expression.

If expression is The value of result is

True False

False True

Classes A class is a data structure that may contain data members (constants, variables, and events), function members (methods, properties, indexers, operators, and constructors), and nested types. Classes are reference types.

Objects, Properties, Methods Objects, properties, methods, (and events) are the basic units of object-oriented programming. An object is representing an instance of a class. Properties, methods, (and events) are the building blocks of objects, and constitute their members.

Objects An object represents an instance of a class.

In Visual Basic, you must instantiate an object before you can apply one of the object's methods or change the value of one of its properties. Instantiation is the process by which an instance of a class is created and assigned to an object variable:

Dim person1 As Person = New Person()

The above example, the variable person1 is assigned to refer to a new instance of the class Person.

Properties A property is an attribute of an object that defines one of the object's characteristics, such as size, color, or screen location, or an aspect of its behavior, such as whether it is enabled or visible.

To change the characteristics of an object, you change the values of its corresponding properties.

To set the value of a property, affix the reference to an object with a period, the property name, an equal sign (=), and the new property value:

Motion v4.7



person1.FirstName = "John“

You can retrieve information about an object by returning the value of one of its properties.

Accessing properties:

• Read/write • Read-only • Write-only

Methods A method is an action that an object can perform.

Examples

• myStopwatch.Start() • Console.WriteLine(“Hello World”)

Contructors Constructors are class methods that are executed when an object of a given type is created, and usually initialize the data members of the new object:

Dim person1 As Person = New Person("John", "Doe")

The String class Represents a sequence of Unicode characters and maps to System.String. The default value of the String type is a null reference.

The maximum size of a String object in memory is 2 GB, or about 1 billion characters.

Instantiating a String Object The most commonly used way by assigning a string literal to a String variable.

Dim string1 As String = "This string created by assignment."

Arrays vs. Collections Arrays are most useful for creating and working with a fixed number of strongly typed objects. Collections provide a more flexible way to work with groups of objects. Unlike arrays, the group of objects that you work with can grow and shrink dynamically as the needs of the application change.

Motion v4.7



If you need to change the size of an array, VB creates a new array and releases the previous array for disposal. This takes execution time. Therefore, if the number of items you are working with changes frequently, or you cannot predict the maximum number of items you need, you might obtain better performance using a collection.

A collection, which does not have to create a new object or copy existing elements, can handle resizing in less execution time.

Arrays An array is a set of values that are logically related to each other, such as the number of students in each grade in a grammar school. By using an array, you can refer to these related values by the same name, and you can use a number that’s called an index or subscript to tell the values apart. The individual values are called the elements of the array, and they’re contiguous from index 0 through the highest index value.

An array can have one dimension or more than one.

You can refer to the array as a whole when you want to refer to all the values it holds, or you can refer to its individual elements one at a time.

Example:

Dim numbers(2) As Integer

numbers(0) = 10

Collections Closely related data can be handled more efficiently when grouped together into a collection. Instead of writing separate code to handle each individual object, you can use the same code to process all the elements of a collection. Some Collections classes have sorting capabilities, and most are indexed. Memory management is handled automatically, and the capacity of a collection is expanded as required.

Generic collection classes make it easy to create strongly typed collections.

Generics A generic type is a single programming element that adapts to perform the same functionality for a variety of data types. When you define a generic class or procedure, you do not have to define a separate version for each data type for which you might want to perform that functionality.

An analogy is a screwdriver set with removable heads. You inspect the screw you need to turn and select the correct head for that screw (slotted, crossed, or starred). Once you insert the correct head in the screwdriver handle, you perform the exact same function with the screwdriver, namely turning the screw.

When you define a generic type, you parameterize it with one or more data types. This allows the using code to tailor the data types to its requirements. Your code can declare several different programming elements from the generic element, each one acting on a different set of

Motion v4.7



data types. But the declared elements all perform the identical logic, no matter what data types they are using.

List(Of T) collection Lists are similar to arrays but are stored very differently. Each element in a list also includes a pointer to the previous and next elements, making it a doubly linked list. It is very fast to add or delete items because doing so only involves changing a few pointers. However, searching a list can be expensive since all searches need to start at one of the list's ends.

Declaration and initialization:

• Dim myStringList As List(Of String) = New List(Of String)

Adding a new item to the end of the list:

• myStringList.Add("item1")

Doing everything in one expression: • Dim myStringList As List(Of String) = New List(Of String) From {"item1", "item2"}

Dictionary(Of TKey, TValue) collection Represents a collection of keys and values.

Provides a mapping from a set of keys to a set of values. Each addition to the dictionary consists of a value and its associated key. Retrieving a value by using its key is very fast, because the Dictionary(Of TKey, TValue) class is implemented as a hash table.

Every key in a Dictionary(Of TKey, TValue) must be unique.

The capacity of a Dictionary is the number of elements the Dictionary can hold. As elements are added to a Dictionary, the capacity is automatically increased.

The For Each statement requires the type of each element in the collection. Since the Dictionary is a collection of keys and values, the element type is not the type of the key or the type of the value. Instead, the element type is a KeyValuePair(Of TKey, TValue) of the key type and the value type.

Creating a new dictionary of strings, with string keys:

• Dim openWith As New Dictionary(Of String, String)

Adding elements:

• openWith.Add("txt", "notepad.exe") • openWith.Add("bmp", "paint.exe")

Doing everything in one expression:

• Dim openWith As New Dictionary(Of String, String) From {{"txt", "notepad.exe"}, {"bmp", "paint.exe"}}

Motion v4.7



Static classes and class members Static classes and class members are used to create data and functions that can be accessed without creating an instance of the class. Static class members can be used to separate data and behavior that is independent of any object identity: the data and functions do not change regardless of what happens to the object. Static classes can be used when there is no data or behavior in the class that depends on object identity.

Some static classes from FCL:

• System.Path, System.Math, System.Console

Motion v4.7

Operations Reference Appendix B: Device Protocol Parameters


Appendix B: Device Protocol Parameters

Use Notes

Default Settings & Tool Tips Device Controller defaults are consistent between the UI and code, and the min and max are validated where applicable (a tooltip indicates the range).

Handling Out-of-Date Definitions Motion 4.6 implements a user notification that an activity in their workflow has an out-of-date definition. All actions will throw an error by default if the parameters given to them come from a different DISCO version than the current one. It is logged to Diagnostic Logging and shows up as the message on the failed action when viewed in the Process Explorer.

This behavior can be overridden by implementing the CanHandleVersion function for particular actions. If the action returns true from the CanHandleVersion call, it is up to the individual action itself to deal with de-serializing the old parameters gracefully.

Motion v4.7



AmberFin Connection

Protocol Name: Folder/workflow name (e.g. AmberFin Connection).

Service Uri*: API Service URL of Amberfin server.

• (Option) Provide a comma separated list of URIs (no number limit) IP or hostname for the endpoint. This allows the Amberfin Device Controller to try all the IPs to find one that it can connect to.

Timeout in seconds: Request time out. Minimum: 5 seconds / Maximum: 600 seconds (10minutes)

Parallel long-term operation limit: Maximum number of parallel resource intensive operations on endpoint.

Parallel short-term operation limit: Maximum number of resource inexpensive operations on endpoint.

Health Check Schedule Interval: Use the slide to set Time interval for checking device availability. (Default: 60s) • Custom Interval checkbox: Specify a custom checking interval (hh:mm:ss).

Motion v4.7



Antivirus Connection Then Anti-virus Device Controller uses the ICAP protocol over synchronous TCP-client.

Upon successful connection the Device Controller verifies:

• available server resources • available AV license • supported methods required for DC operating

If any condition is broken an appropriate DCOutput object is generated.

Return information:

• If the input json file created targets a non-viral file, the Device Controller returns True (i.e. file is clean)

• If the input json file created targets a viral file, the Device Controller returns False (i.e. file is not clean) and found violations delimited by a comma

Protocol AntiVirus endpoint definition

Name: Workflow name. (e.g. AntiVirus Connection)

Address: Address of the AntiVirus server.

Port: Port number of the AntiVirus server.

Parallel long-term operation limit: (Check box to enable this parameter.) Maximum number of parallel resource intensive operations on endpoint.

Parallel short-term operation limit: (Check box to enable this parameter.) Maximum number of resource inexpensive operations on endpoint.

Motion v4.7



Health Check Schedule Interval: Use the slide to set Time interval for checking device availability. (Default: 60s)

• Custom Interval checkbox: Specify a custom checking interval (hh:mm:ss).

Motion v4.7



Digimetrics Aurora Connection

Name: Aurora workflow name. (e.g. Digimetrics Aurora Connection)

Service Uri*: API Service URL of Aurora server.

Username: Login identifier.

Password: Login password.

Report folder: Path of Aurora report folder.





Motion v4.7



Avid Connection

Motion v4.7



Protocol Name: Folder/workflow name (e.g. Avid Connection).

Address*: Avid interplay address.

Username: Avid interplay username

Password: Avid interplay password.

Workgroup: Avid interplay workgroup name.

Path: Relative path within the workgroup.




Spying Enable Spying: Check to monitor this endpoint for file changes.

Spy Start Time: Specify the spy start time ‘Immediately’ or ‘Specific Time’. When Specific time is selected the option “Spy Schedule Interval in Seconds” is enabled for specifying time.

Spy Schedule Interval: Use the slide to set Time interval for starting spy retrieving file changes. (Default: 60s) • Custom Interval checkbox: Specify a custom checking interval (hh:mm:ss).

Storage Warning Threshold Percent: Minimum level of free space required in megabytes on endpoint storage. If free space goes under this level warning will be initiated (currently warning initiation is not implemented).

Associate with Insight Storage: If synchronized with Insight then files discovered on this storage will be synchronized to Insight associated to selected storage.

Triggers For association with Workflows.

Create: Selected workflow will be executed when new file is created on storage.

• Override job priority: Optionally, a job priority override can be set for each trigger type. This option becomes enabled when its associated trigger type is selected.

Close: Selected workflow will be executed when a file is closed on storage.


Motion v4.7



Update: Selected workflow will be executed when a file is updated on storage.


Delete: Selected workflow will be executed when a file is deleted on storage.


Protocol-specific spy parameters TBD

Baton QC The Interra Systems Baton quality check Device Controller device uses a personal Zenium engine just for Motion (deployed with Motion), license server, a very simple blueprint, and the Zenium Baton plug-in to provide Baton QC support. The simple Web API can submit and monitor jobs in Zenium and then retrieve the job results.

The device controller generates a package (zip file) from the original report files.

Note: Always reusing the same Zenium instance ID without disposing of it allows it to stay loaded and so saves resources.

Deployment The Baton DC is deployed with Motion.

The Zenium Server and the Zenium Repo Server that the DC uses must be deployed separately from Motion. Motion doesn't necessarily have to be on the same machine as the device manager (all the URLs are configurable), but the default behavior assumes that it is.

For details on Zenium reference the Zenium Designer Users Guide and SelenioFlex File User Guide.

Motion v4.7



Protocol Name: Baton workflow name. (e.g. Baton Connection)

Host Name: Baton Host name.

Port: Port number of the Baton device. (Default: 8080)

Username: Baton login username

Password: Baton login password. The password is encrypted on entry.



Health Check Schedule Interval in Seconds: Time interval for checking device availability in seconds. (Default: 60)

Motion v4.7



CIFS Connection

Motion v4.7



Protocol Name: Folder/workflow name (e.g. CIFS Connection).

Address*: Address of CIFS device (e.g. \\share\). \\host\shared_folder (An IP address can work here) (e.g. \\localhost\c$\test)

Domain: Domain of CIFS device.

Username: Username of CIFS device.

Password: Password of CIFS device.




Spying Enable Spying: If set this endpoint will be monitored for file changes.





Exclude extensions from Metadata Extraction: If blank, process for metadata extraction is tried for all the files. If entries specified (e.g. .mov, .doc, etc.), the matching files are excluded from the metadata extraction process.

Metadata Extraction Priority: Use the slider to specify, for each declared endpoint, the metadata extract jobs priority from 1 to 10 (as for the workflows). Job scheduler uses this new parameter from the endpoint.

IMPORTANT: Default value is 10 (lowest). Change this value carefully as a normal (5) or higher (1 to 4) priority will have a direct impact on your workflow jobs when the system is processing a lot of metadata extraction jobs.

Motion v4.7




Create: Selected workflow will be executed when new file is created on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Close: Selected workflow will be executed when a file is closed on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Update: Selected workflow will be executed when a file is updated on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Delete: Selected workflow will be executed when a file is deleted on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Protocol-specific spy parameters Is recursive: Determines if the spy should be recursive.

Extensions to spy: Determines the file extensions to spy.

Motion v4.7



Digital Rapids Connection This DC supports the API before name space changes.

If a customer upgrades the device, workflows needs to be changed.

Protocol Name: Digital Rapids workflow name.

Service Uri*: API Service URL of Digital Rapids server.

Service Timeout: API Service Timeout Value in milliseconds. (Default: 5000)





Motion v4.7



DIVA Connection

Motion v4.7



Protocol Name: DIVA workflow name. (e.g. DIVA Connection).

Service Uri*: API Service URL of the DIVA server.

• Motion 4.6 and higher allow the DIVA Device Controller to switch between the 1.0 and 2.1 APIs depending on what the user inputs as the endpoint address.

Service Timeout: API Service Timeout Value in minutes. (Default: 30)





Spying Enable Spying: If set, this endpoint will be monitored for file changes.


Spy Schedule Interval: Use the slide to set Time interval for starting spy retrieving file changes. (Default: 60s)




Exclude extensions from Metadata Extraction: If blank, than all/everything are spied. If entries specified (e.g. .mov, .doc, etc.) then only these are spied. Diva Note: In Storage Explorer, when reviewing the metadata of a file in the Diva (an object in Diva language), the operator can see the list of files in this object and a list of tapes holding the object.

Metadata Extraction Priority: Use the slider to specify, for each declared endpoint, the metadata extract jobs priority from 1 to 10 (as for the workflows). Job scheduler uses this new parameter from the endpoint. IMPORTANT: Default value is 10 (lowest). Change this value carefully as a normal (5) or higher (1 to 4) priority will have a direct impact on your workflow jobs when the system is processing a lot of metadata extraction jobs.

Motion v4.7




Create: Selected workflow will be executed when new file is created on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Close: Selected workflow will be executed when a file is closed on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Update: Selected workflow will be executed when a file is updated on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Delete: Selected workflow will be executed when a file is deleted on storage. • Override job priority: Optionally, a job priority override can be set for each trigger type.


Protocol-specific spy parameters Category Mask (use * as wildcard): To filter based on Category (i.e. endpoint specific).

Note: Using the default Category Mask "*", Spy returns everything from all the categories.

Motion v4.7



FIMS Transfer Connection

Protocol Name: FIMS Transfer workflow name.

Address*: Address of FIMS transfer service (e.g. http://fims-device-location).

Username: Username of FIMS transfer service.

Password: Password of FIMS transfer service.





Motion v4.7



Flip Factory Endpoint Connection

Protocol Name: Flip Factory Endpoint workflow name.

Service Uri*: API Service URL of FlipFactory server.





Motion v4.7



FTP Connection

Motion v4.7



Protocol Name: FTP workflow name.

FTP Server: FTP Server Address.

FTP Server Port: FTP Server Port Number. (Default: 21)

Username: Login identifier.

Password: Login password.

Root Path: This parameter specifies what folder to start spying from on the FTP device and defaults to "/".













Motion v4.7








Protocol-specific spy parameters Skip Empty Files: Enable (Yes)/Disable (No) skip any files.

Motion v4.7



Instant Online Connection The Instant Online device controller is used to send a FinalCutPro project to IOL. When the FCP XML is generated previously in the workflow, the activity accepts it as an input property.

Protocol endpointSchema: Instant Online server endpoint definition

Name: Workflow name. (e.g. Instant Online Connection)

Instant Online Server: Host name or IP Address of the Instant Online server.

Note: The Port is hardcoded as 3002.

User Name: Instant Online Login identifier. (Motion by default)

Password: Instant Online Login password. (Motion by default)





Motion v4.7



K2 Summit Connection

Motion v4.7



Protocol Name: K2 Summit workflow name.

Domain Name: K2 Summit Domain name.

Host Name: K2 Summit Host name.

Username: K2 Summit User name.

Password: K2 Summit Password.

K2 Summit timeout: K2 Summit communication timeout. (Default: 100)














Motion v4.7







Protocol-specific spy parameters TBD

Motion v4.7



mCapture Connection

Protocol endpointSchema: mCapture server endpoint definition

Name: Workflow name. (e.g. mCapture Connection)

Address: Address of the mCapture device.

Port: Port number of the mCapture device.





Motion v4.7



Nexio Connection

Protocol Name: Nexio workflow name.

Address*: Address of Nexio device.

Port: Port number of the Nexio device API. (Default: 557)





Motion v4.7








Exclude extensions from Metadata Extraction: If blank, than all/everything are spied. If entries specified (e.g. .mov, .doc, etc.) then only these are spied.

Metadata Extraction Priority: Use the slider to specify, for each declared endpoint, the metadata extract jobs priority from 1 to 10 (as for the workflows). Job scheduler uses this new parameter from the endpoint. IMPORTANT: Default value is 10 (lowest). Change this value carefully as a normal (5) or higher (1 to 4) priority will have a direct impact on your workflow jobs when the system is processing a lot of metadata extraction jobs.










Motion v4.7



Protocol-specific spy parameters Skip Empty Files: True if empty files have to be skipped.

Skip Audio Files: True if audio files have to be skipped.

Skip UMID Less Files: True if UMID-less files have to be skipped.

Protocol-specific get extended metadata parameters From the listings of “Protocol-specific get extended info parameters”, select (check) the extended metadata that Nexio Spy is to retrieve.

Check boxes include:

Extract Record Date Time

Extract Machine Name

Extract Source 8 byte Id Handle

Extract UMID

Extract GUID

Extract User Name

Extract Department

Extract Link

Extract Description

Extract Agency

Extract User Field 1




Extract External Controller UID

Extract Video ARC

Extract Modified Timestamp

Extract Video QA Status

Extract Video ARC Added Bits

Extract Vertical Size

Extract Scan Type

Extract Frame Rate

Extract Audio Tracks

Extract Audio Tracks Info

Extract Aspect Ratio

Motion v4.7



Selenio Flex Connection

Protocol Name: Selenio Flex workflow name.

Service Uri*: API Service URL of Selenio Flex server.

Service Timeout: API Service Timeout Value in milliseconds. (Default: 5000)




Motion v4.7



SGL Connection

Motion v4.7



Protocol Name: SGL workflow name.

SGL Server: SGL Server IP Address.

SGL Server Port: SGL Server Port Number. (Default: 8199)

SGL Server timeout: SGL Server communication timeout. (Default: 100)

Parallel long-term operation limit: Maximum number of parallel resource intensive operations on endpoint. (Default: )

Parallel short-term operation limit: Maximum number of resource inexpensive operations on endpoint. (Default: )





Spy Schedule Interval: Use the slide to set Time interval for starting spy retrieving file changes. (Default: 60s)


Incremental Spy Start Time: Specify the incremental spy start time ‘Immediately’ or ‘Specific Time’. When Specific time is selected the option “Incremental Spy Schedule Interval in Seconds” is enabled for specifying time.

Incremental Spy Schedule Interval in Seconds: Use the slide to set Time interval for starting spy retrieving file changes. (Default: 60s) • Custom Interval checkbox: Specify a custom checking interval (hh:mm:ss).



Triggers Create: Selected workflow will be executed when new file is created on storage.



Motion v4.7








Protocol-specific spy parameters ID Mask (use * as wildcard): To filter based on ID.

Group (use * as wildcard): To filter based on Group.

Volume (use * as wildcard): To filter based on volume (tape ID).

Motion v4.7



Vantage Endpoint Connection

Protocol Name: Vantage workflow name.

Service Uri*: API Service URL of Vantage server




Passing Variables Workflow designers need to be able to:

pass variables from the Motion4 workflow to the vantage workflow.

retrieve values from the vantage workflow when it's completed. The best way to achieve this is to return the list of "labels".

The following parameters are added to:

VantageStartWorkflowRequest: Dictionary<string, string> parameters

Response value in VantageStartWorkflowResponse: string[] labels

• get back the progress • get the final status and results

Motion v4.7

Operations Reference Appendix C


Appendix C

Device Endpoint URI Examples This matrix provides a list of example endpoint URIs needed to give Motion, and other information.

Note: This matrix is current to the date of this product release.

Device Controller Endpoint example

AmberFin http://zf-amberfin:8080/icr/ICRControl

Digimetrix Aurora http://wtl-AuroraTest:1001/ApiService

Avid

Diva http://137.237.135.21:9763/services/DIVArchiveWS_SOAP_2.1.DIVArchiveWSHttpSoap12Endpoint/

SelenioFlex File http://vm-SelenioFlex:44000/TranscodeMgrWS

Motion v4.7 - Imagine Communications

Documents