1. Click Workflows in the left menu, then click Workflows to display a list of existing workflows.
2. Select a workflow, and click the Edit icon () in the Action column to edit the workflow. The Edit Workflow panel displays at the right, where a workflow can be renamed, enabled or disabled, made visible, set to run with a right-click, or set as Admin Only. You can also set a priority for this workflow based.
   
3. A workflow's "Subject Qualifier Expression" can be modified. A Subject Qualifier further refines the attributes on an asset that must be true for the workflow to be displayed to an end user. Subject Qualifiers are written in Spring Expression Language (SPeL) 
   
   Important: Subject Qualifier Expression text field is only available if subjectDOClassName is not empty in the workflow. 
4. Use the Priority field to set the importance of a workflow so that the most important work is done first. The scheduled workflow with the highest priority value is executed first. This field allows you to guarantee service level commitments, prioritize the most important or profitable work, and deprioritize non-critical work.
   • Select a static priority of No Priority (value 1), Low (value 2), Medium (value 3), High (value 4), or Critical (value 5).
   • Select Custom to enter your own number or to create a dynamic priority by entering an expression that evaluates to a number, which becomes the priority value. Use Java Spring Expressions to dynamically calculate the priority of a workflow. For more information, see Spring Expression Language (SpEL) documentation.
     Important: The expression and data object(s) that are available to evaluate in a custom priority are limited to those which can be evaluated before they are processed by a runtime (priorities are handled by the scheduler). A basic rule of thumb is to only attempt to evaluate an expression that includes data that is available in the user space and not the backend of Reach Engine. For example, the date/time, username, or role can be evaluated for priority. The amount of executing workflows or the results of an asset query would not be evaluated for priority.
   • Existing workflows have a default value of No Priority, which is the lowest priority.
   • The Workflow Status page displays a priority column, which indicates the priority value of each scheduled or executing workflow. If a workflow has a custom priority value, this value is also displayed. Users can sort workflows by priority so that they understand when a particular workflow will execute and which work is most important.
   • The priority of a workflow can be specified in the XML header. If the Keep these Display Preferences option is turned on, when the workflow is reimported, the values selected in the UI are not overwritten by any values in the API.
5. If Keep these Display Preferences is turned on, when a workflow is reimported, the values are not overwritten with the API values. If turned off, when a workflow is reimported, the values are overwritten. 
6. Select the Context Data tab to view, add, and edit workflow parameters without editing the XML or exporting/importing the workflow manually.
   • The Name and Data Type fields are ready only.
   • Select More to access toggles for accept multiple values, required fields, and hidden or to modify the label and description.
   • Context data definitions are displayed in the order of user input. To reorder, drag and drop by selecting the header.
     
     
   • You can quickly change parameters as your business needs evolve. Context data definitions provide you with workflow variables that can be used to accept external input to your workflow, maintain and communicate data between steps and sub-flows, store the result of a workflow, and have a default value based on the fields of Assets or other Reach Engine DataObjects.
   • Important: Default system workflows cannot be edited but their context data definitions and their values are shown as ready only. Picklist datadefs that are populated by a data object query cannot be edited. Duplicate a system workflow to edit the datadefs for a unique use case or export the XML and edit in the IDE of your choice.
7. Click Save.

Import a workflow using the Upload icon ( ) at the top right of the Workflows screen. As an admin, when you import a workflow, you have the option to override its flags:

• Enabled
• Visible
• Admin Only
• Right-click

To ensure an import is always correctly flagged in the Access (Admin) UI, any reset will revert on workflow re-import and flags will remain the way they were set by the Admin, regardless of what's in the workflow.

Workflow Step Queues

To view the global workflow steps that are configured and the activities within them in Spartan, navigate to /alpha/#/workflow-step-queues. 

Workflow Groups

Administrators can create groups to manage workflows.

Display and Search Workflow Groups

1. Click Workflows in the left menu, then click Workflow Groups to display a list of existing workflow groups.
2. Select a group. You can:

• Click the Edit icon ( ) in the Action column to edit workflow groups.
• Click the Add icon ( ) at the top left to add new workflow groups.
• Click the Delete icon ( ) in the Action column to remove a workflow group. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple workflow groups.

To search for workflow groups, click in the Search box and enter your search term.

To promote or demote workflow groups, click the Reorder icon ( ) to open the Order Workflow Groups panel. Drag and drop workflow groups to the desired position in the list of groups and click Save.

Metadata Forms in a Workflow

When a default metadata form is specified for a workflow, the form is rendered for user input. To specify a default metadata form in a workflow, use the following XML.

<contextDataDef name="singleMetadataForm" dataType="MetadataForm" 

label="Metadata Form" userInput="true" defaultDataExpression="{'metadataFormId': 200}"/>

Create a Workflow Group

1. Click Workflows in the left menu, then click Workflow Groups to display a list of existing workflow groups.
2. Click the Add icon ( ) at the top left to open the Add Workflow Group panel.
3. Enter a workflow group name.
4. Click the Workflows field and choose a workflow from the drop-down list. Repeat to add multiple workflows. 
   
5. Click Save. The new workflow group displays in the list.

You can re-sort the groups in the list by dragging and dropping them into the order you want.

Workflow Groups display in the Actions ( ) menu for related assets.

Watch Folders

Reach Engine watch folders are used to trigger workflows against files placed in the folder. Watch folders include a default set of properties, but can also contain custom properties that are unique to the Reach Engine workflow executed against the watch folder. 

Click Workflows in the left menu, then click Watch Folders to display a list of existing watch folders.

Important: When watch folders are added or modified, they are updated immediately and Reach Engine does not need to be restarted.

From this page, you can:

• Click the Edit icon ( ) in the Action column to edit a watch folder.
• Click the Delete icon ( ) in the Action column to remove a watch folder.
• Toggle the Enabled slider to turn on/off a watch folder.
• Select a column name to reorder the list.
• Enter a search term in the Search box to filter the watch folders.

Create a watch folder

1. Click the Add icon ( ) at the top left.
2. Enter a watch folder name.
3. Enter the watch folder path.
4. Select which workflow to run.
5. In File Data Def, select which data definition to assign to an incoming file. Data Defs are variables that are used in Workflows. Use the Data Def inputs to define the value of a data def to populate on any execution of a Watch Folder / Schedule. 
6. For Polling Interval, select how often the watch folder (in seconds) should be checked for new files. After finding a new file in the folder, Reach Engine checks the size of the file and waits until it remains the same size for the number of seconds set as the polling interval. After checking the file twice and verifying the size is unchanged, the workflow is then initiated.
7. If your watch folder as subfolders, turn on Process Folders to also process subfolders within the specified path.
8. To have the system wait until it can validate that no other systems or users are accessing or modifying a file to decrease the likelihood that a file will be processed prematurely, turn on Require a File Lock. This option is used in conjunction with Polling Interval.
9. To delete a file from the watch folder after successfully executing the workflow, turn on Delete on Success. 
10. You can add context data using name/value pairs in Data Def 1. Select + Data Def to add additional pairs.
11. Select Add. Newly added watch folders are enabled by default.

Schedules

You may want certain workflows to run at a scheduled interval. To display the list of recurring workflow schedules, click Workflows in the left menu, then click Schedules.

Note: With the release of the Workflow Schedules feature, Reach Engine will automatically migrate any existing scheduled workflows (CRONS). All intervals will be created as Custom. Once imported, Local Properties entries for CRON configurations will be ignored and Reach Engine will not need to be restarted to add new schedules or modify existing ones.

Create a workflow schedule

1. Click the Add icon ( ) at the top left to add new workflow schedule.
2. Enter the schedule name.
3. Select the workflow to run.
4. Select an Interval Time. To use a CRON expression, select Custom then enter the CRON expression.
5. Select Add. Schedules are not enabled by default. 

Modify existing workflow schedules

1. Select a schedule. The right curtain displays schedule information.
2. Modify the schedule as needed. 
3. To disable a schedule, toggle the Enable Schedule slider.

Note: If you delete a schedule, this action cannot be undone.

Metadata

Metadata levels can be used to build a metadata schema:

• "Facets" can be used to group pick-list metadata fields and make those fields available to specific user role(s).
• "Fields" are the lowest level of a hierarchy. For example, every drop-down in the football search is an individual picklist (season, team, player). Fields can be combined to create a hierarchy that defines the order in which the fields can be searched or added to an asset as metadata.
• "Forms" create a structure of fields when users ingest content into Reach Engine.
• "Groups" contain metadata fields that can be used to organize fields for visual representation, as well as for regulating visibility of fields.
• "Hierarchies" allows you to order fields in a dependent order for tagging and searching content.
• "Categories" are applied to metadata groups. They are primarily used for organizational purposes and permissions restrictions.

Fields and hierarchies can be combined to create forms and/or groups.

Metadata Facets

Facets help users search and filter data within Reach Engine to more quickly get to the asset(s) they want. Admins can create facets for metadata pick-list fields and then assign that facet to a role(s). When a user logs into Reach Engine, the user is presented with the metadata fields for the facets that their role(s) have visibility to see.

Display and Search Facets

1. Click Metadata in the left menu, then click Facets to display a list of existing facets.
2. Select a facet. You can:

• Click the Edit icon ( ) in the Action column to edit facets.
• Click the Add icon ( ) at the top left to add new facets.
• Click the Delete icon ( ) in the Action column to remove a facet. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple facets.

Facets are sorted alphabetically by display name.

Create a Facet

1. Click Metadata in the left menu, then click Facets.
2. Click the Add icon ( ) at the top left to open the Create Facet panel.
3. Enter a Facet Name.
4. Choose the Roles for which the Facet is applicable. You can choose more than one role.
5. Choose the Fields for which the Facet is applicable. You can choose multiple pick-list fields.
6. Drag-and-drop the fields to define the order of the visible properties.
   
   Note: Properties within a Facet that are greyed out are not visible to all selected roles because of the role permissions.
7. Click Add. The new Facet displays in the list.

Metadata Fields

Fields are the lowest level of a hierarchy. To view the existing metadata fields, select Metadata from the left menu then Fields. 

• If a field is archived, the Boost and Boost Priority fields are disabled. Archived fields are not shown to users in the user interface but assets with values set on that field are not removed.
• If a Boost is not active, the Boost Priority field is disabled.

Create a metadata field

1. Click the Add icon ( ) at the top left.
2. Enter the field name.
3. Select the field data type. See Picklist fields below for information specific to picklists.
   
4. Turn on the Boost toggle if the field is searchable.   
5. Specify the Boost Priority. This value indicates how much to weight the field for its relevance when doing a basic search in Reach Engine. 
6. Select Add.

Picklist fields

From the list of fields, you can edit a picklist field in single asset view by selecting the picklist name link in the Name column. This option makes editing a large picklist easier.

When Picklist is selected as the field type, enter the possible values in the Value section.

1. Click the Add Item button.
2. Enter a name.
3. You can enter a Custom ID. If this field is left blank, a unique ID is created. The ID cannot be modified once set.
4. Click Confirm.

Other picklist actions:

• Use the Search field to filter long picklists so you can find what you need. 
• Click the pencil icon to edit an existing picklist item. 
• Click the X to remove an item from a picklist. Removing the item only removes it from the picklist. Existing instances of this value remain on assets.
• You can import values from a CSV file for a picklist field by selecting the import () icon from the picklist field row from the main field screen. You can also select the import icon from the action buttons at the top of single asset view. If you are editing an existing field, choose whether to replace existing values or append values to the existing list. The toggle to edit picklist values after import is selected by default when importing to a picklist field.
• You can export picklist items to a CSV by selecting the export () icon from the picklist field row from the main field screen. You can also select the export icon from the action buttons at the top of single asset view. The file will contain the name and ID of each picklist item.

Categories

Categories are applied to collections, videos, clips, audio assets, images, projects, other assets and metadata groups. They are primarily used for organizational purposes and permissions restrictions.

Note: A user's Role must have association to all categories listed on an asset to view that asset.

Common examples of categories include:

• Business Process Uses: Ready for review, accepted, rejected, ready for editing, raw materials, completed projects.
• Departmental Uses: Post-production, public relations, producers, client.
• Multi-Company Uses: Accelerated Entertainment, Levels Beyond, External Company.

Display and Search Categories

1. Click Metadata in the left menu, then click Categories to display a list of existing categories.
2. Select a category. You can:

• Click the Edit icon ( ) in the Action column to edit categories.
• Click the Add icon ( ) at the top left to add new categories.
• Click the Delete icon ( ) in the Action column to remove a category. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple categories.

Categories are sorted alphabetically by display name.

To search for categories, click in the Search box and enter your search term. The search looks at the Display Name, Description, and ID fields.

Create a Category

1. Click Metadata in the left menu, then click Categories.
2. Click the Add icon ( ) at the top left to open the Create Category panel.
   
3. Enter a display name and description for the new category.
4. Choose the roles associated to the category.
5. Click Add. The category displays in the list.

Metadata Forms

Display and Search Metadata Forms

1. Click Metadata in the left menu, then click Forms to display a list of existing metadata forms.
2. Select a form. You can:

• Click the Edit icon ( ) in the Action column to edit metadata forms.
• Click the Add icon ( ) at the top left to add new metadata forms.
• Click the Delete icon ( ) in the Action column to remove a metadata form. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple metadata forms.

To search for metadata forms, click in the Search box and enter your search term. For example, there are four forms: Test, Another Test, Test This, and Form. If the text "test" is typed in the box, the first three forms with the word "test" in their names display. If "this" is typed in the box, only the form "Test This" would display.

Create a Metadata Form

1. Click Metadata in the left menu, then click Forms to display a list of existing metadata forms.
2. Click the Add icon ( ) at the top left to open the Create Form panel.
3. Enter a Name for the new Metadata Form.
4. Choose the Categories for the form. You may choose multiple categories. Anytime a metadata form is used for a Reach Engine ingest, the assets will be tagged with the category assigned from the metadata form. Additional categories can also be assigned based on a user's role from the Prelude and Premiere panels.
5. Choose the Roles for the form. You may choose multiple roles.
6. Choose the Fields you want to associate with the Metadata form. You can choose multiple fields.
   
7. Drag-and-drop the fields to define the order of the visible properties.
8. Move the slider beside a Metadata Field to make it a required field when the Metadata form is displayed.
9. Click Add. The new form displays in the list.

Metadata Groups

Display and Search Metadata Groups

Metadata groups contain metadata fields. Metadata groups are used to organize fields for visual representation inside Reach Engine, as well as for regulating visibility of fields. Through the use of categories and roles, administrators determine metadata groups visible to and editable by users.

1. Click Metadata in the left menu, then click Groups to display a list of existing metadata groups.
2. Select a group. You can:

• Click the Edit icon ( ) in the Action column to edit metadata groups.
• Click the Add icon ( ) at the top left to add new metadata groups.
• Click the Delete icon ( ) in the Action column to remove a metadata group. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple metadata groups.

To search for metadata groups, click in the Search box and enter your search term.

Create a Metadata Group

1. Click Metadata in the left menu, then click Groups.
2. Click the Add icon ( ) at the top left to open the Create Group panel.
   
3. Enter a name. The name you enter becomes the group's header throughout Reach Engine's applications.
4. Select category/categories to associate the group to the category in the user interface.
5. Click Add.

Metadata Mappings

Metadata mappings provide templates that Access users can use to map EXIF fields to metadata fields in Reach Engine. To view the metadata mappings available in Reach Engine, click Metadata in the left menu, then click Mappings. Currently, this information is read only and cannot be modified through Spartan. 

Create and Manage Users

Administrators can create Reach Engine Access and Collaborate users who can be assigned roles that define the types of actions they can perform.
Note: Reach Engine can be configured to map roles to users based on OAuth groups. Please contact your Levels Beyond representative for details.

Reach Engine Users

Display and Search Reach Engine Users

1. Click Users in the left menu, then click Reach Engine Users.
2. Select a user. You can:

• Click the Edit icon ( ) in the Action column to edit users.
• Click the Add icon ( ) at the top left to add new users.
• Click the Archive icon ( ) at the top left to archive a user. You can multi-select (CTRL+Click or Command+Click) and click the Archive icon at the top left to archive multiple users.
• Click the Key icon ( ) to reset a user's password.

Note: This option is only available if your organization does not use Okta, Ping, LDAP, or SAML for identity management and single-sign on (SSO) security. In organizations that use the preceding tools, the Reach Engine password is linked with the SSO and must be reset at an organization level.

To disable a user, but not archive the user, select a user, click the Edit icon to display the Edit User panel, and then deselect the Enabled slider.

To display archived users in the list of users, move the Archived slider, at the top right above the list of users, to the right.

To search for users, click in the Search box and enter your search term.

Create a Reach Engine User

1. Click Users in the left menu, then click Reach Engine Users.
2. Click the Add icon ( ) at the top left to open the Create User panel.
   
3. Enter a unique User Name.
4. Enter the user's first and last name.
5. Enter a unique Email Address.
6. Assign one or more roles to the user in the Role field. Roles assigned to the user determine the assets the user can view, as well as Reach Engine features that are accessible to the user. Note: A user's role must have association to all categories listed on an asset to view that asset.
7. Move the Admin slider to the right to give the user administrative access to Reach Engine.
8. Click Add. The new user displays in the list.

The new user receives an email welcome to Reach Engine. The email contains the user's User ID and a system-generated default password and prompts the user to change the password when they first log into Reach Engine.

Note: Access uses BCrypt encryption to store passwords.

Collaborate Users

Display and Search Collaborate Users

1. Click Users in the left menu, then click Collaborate Users.
2. Select a user. You can:

• Click the Edit icon ( ) in the Action column to edit users.
• Click the Add icon ( ) at the top left to add new users.
• Click the Delete icon ( ) in the Action column to remove a user. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple users.

Create a Collaborate User

1. Click Users in the left menu, then click Collaborate Users.
2. Click the Add icon ( ) at the top left to open the Create Collaborate User panel.
   
3. Enter the user's first and last name.
4. Enter a unique Email Address.
5. Click Add. The new user displays in the list.

The new user receives an email welcome to Collaborate. The email contains the user's User ID and a system-generated default password and prompts the user to change the password when they first log into Reach Engine.

Categories

Categories are applied to collections, videos, clips, audio assets, images, projects, other assets and metadata groups. They are primarily used for organizational purposes and permissions restrictions.
Note: A user's Role must have association to all categories listed on an asset to view that asset.
Common examples of categories include:

• Business Process Uses: Ready for review, accepted, rejected, ready for editing, raw materials, completed projects.
• Departmental Uses: Post-production, public relations, producers, client.
• Multi-Company Uses: Accelerated Entertainment, Levels Beyond, External Company.

Display and Search Categories

1. Click Users in the left menu, then click Categories to display a list of existing categories.
2. Select a category. You can:

• Click the Edit icon ( ) in the Action column to edit categories.
• Click the Add icon ( ) at the top left to add new categories.
• Click the Delete icon ( ) in the Action column to remove a category. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple categories.

Categories are sorted alphabetically by display name.
To search for categories, click in the Search box and enter your search term. The search looks at the Display Name, Description, and ID fields.

Create a Category

1. Click Users in the left menu, then click Categories.
2. Click the Add icon ( ) at the top left to open the Create Category panel.
   
3. Enter a display name and description for the new category.
4. Choose the roles associated to the category.
5. Click Add. The category displays in the list.

Roles

Administrators can create roles, set Reach Engine access, and manage the permissions assigned to a group of users. For example, an editor may be assigned create, modify, view and delete permissions; a reviewer may be assigned only modify and view permissions; and a producer may be assigned only create, modify and view permissions.
Each role can be associated with one or more categories. Roles can also be associated with one or more metadata groups.
Note: When modifying Roles, a Modify Asset Categories checkbox allows Administrators to control which Roles can modify asset categories.

Display and Search Roles

1. Click Users in the left menu, then click Roles.
2. Select a role. You can:

• Click the Edit icon ( ) in the Action column to edit roles.
• Click the Add icon ( ) at the top left to add new roles.
• Click the Delete icon ( ) in the Action column to remove a role. You can multi-select (CTRL+Click or Command+Click) and click the Delete icon at the top left to delete multiple roles.

To search for roles, click in the Search box and enter your search term.

Create a Role

1. Click Users in the left menu, then click Roles.
2. Click the Add icon ( ) at the top left to open the Add Role panel.
   
3. Enter a name for the role.
4. Choose metadata groups and permissions.
5. Choose the category permissions:
   
   • Choose View Uncategorized Assets to give non-admin users access to view assets that do not have categories. The following scenarios occur if a user's role does not have "View Uncategorized Assets" set:
     • When a clip is created, the clip inherits the parent video's categories. 
     • When a new collection is created, setting a category is mandatory.
     • When a new project is imported, setting a category is mandatory. 
   • Choose Edit Asset Categories to allow users in the role to modify asset categories.
6. Choose the Role(s) for which the categories are visible.
7. Choose the default categories applied when a clip is created. The list of default clip categories can only be populated from the list of defined categories on the role. If a default clip category has not been created on the role, then the default Reach Engine operation of parent asset category inheritance still occurs. Categories on parent asset are pre-populated in the metadata panel on the right for both timeline and video clips. For users that have multiple roles, default categories are set on all roles and all default categories are applied to the timeline and video clips. For users that have multiple roles, but only one role has default categories and the others do not, parent asset category inheritance still occurs.
8. Choose the asset permissions.
   
   • Choose Edit Assets to allow users in the role to edit asset details, including:
     • Asset name.
     • Asset metadata.
     • Clip mark in/out points.
     • This option does not include editing asset categories.
   • Choose Delete Assets to allow the user in the role to delete assets.
   • Choose Create Collections to allow users in the role to create collections.
   • Choose Add/Remove from Collections to allow users in the role to add and remove from the contents in a collection.
9. Choose the download & export permissions.
   
   • Choose Download Proxy to allow the user to download proxies. If a user has multiple roles, the user can download proxies if at least one role permits it.
   • Choose Download Source & Mezzanine to allow the user to download high-resolution source files. This option is useful if the user wants to work on the files when not connected to a network. This option is not for Clips or Collections.
10. Choose the Collaborate tasks & permissions.
    
    • Choose Share Assets Externally if the role can download assets (Shared tasks) in Collaborate.
    • Choose Request Assets Externally to define if the role can create tasks in Collaborate to request assets (Request tasks).
11. Choose the workflows started by these roles to allow a role to view additional workflows.

Notes:

• Users that are assigned one or more roles will have access to all workflows run by any users assigned to those role(s) on the workflow status screen, not just their own workflows.
• Archived roles do not display in the list.

By default, the roles are allows to Take Action on Workflows Started by the Above Roles. Move the slider to change this option.

1. Choose Use RQL to refine permissions to allow the user to use RQL search queries. Note that a role with RQL permission that grants access to content:
   
   • Allows users with that role to see thumbnails of those assets.
   • Allows users with that role to see metadata if their Role also grants view metadata access and/or edit metadata if their Role also grants edit metadata access.
2. Enter the RQL Permissions.
3. Click Add. The new role displays in the list.

Notes:

• When a user has multiple roles, the user can perform an action if at least one role permits it.
• The Roles panel allows an administrator to define read-only (view) permissions for specific metadata groups within the Role.
• Users assigned multiple roles should have optimistic viewing/editing permissions:
• If one user's Role has view and another Role does not, the user can view.
• If one user's Role has edit and another Role has view, the user can edit.
• A metadata group cannot be both view and edit at the same time.
• If a user has access to an Asset and that Asset has a metadata group, then if one of the user's Roles has either view or edit access, the user can see the metadata group's fields.
• If Edit is selected for a metadata group, it is assumed that the user has view as well.

Storage

With release 2.7, you can define file systems, directories, libraries, and path mappings for storage. In the past, storage was defined using a .properties file, which required customers to contact Levels Beyond to make changes and to restart the system in order for the changes to take effect. With release 2.7, storage options can be added and changed by your organization's administrator and changes take effect immediately with no down time. 

The storage structure is hierarchical. A file system is the top level of your storage. An example of a storage structure might be:

• File system: AWS
• Directory: levelsbeyond:reachengine/proxies/
• Library: s3proxies

File Systems

A file system is the top level of your storage. To create or edit file systems:

1. Click Storage in the left menu, then click File Systems.
2. Add support for KMS Encrypted Buckets by setting the kms.arn parameter.
3. To edit an existing file system, click the Edit icon ( ) in the Action column. Make the necessary changes and click Save.

AWS S3 Transfer Acceleration

With release 2.14, AWS S3 transfer acceleration is supported. S3 transfer acceleration must be enabled in the AWS Console first. Multiple file systems can be created and applied to the same bucket in order to apply acceleration to different use cases.

To use transfer acceleration, edit an existing file system and set useAcceleration to true at the bottom of the Edit panel.

Directories

You can configure directories for the types of storage you have defined on the File Systems page. Directories are a level below the file system storage level. User permissions are tied to directories. Currently, you can view and update existing directories.  

1. Click Storage in the left menu, then click Directories.
2. To edit an existing directory, click the Edit icon ( ) in the Action column. Make the necessary changes and click Save.
   Note: The File System picklist is populated with file systems defined on the File Systems page.

Libraries

Libraries are used for managed storage or repositories, such as the default locations for mezzanine and proxy files or other supported content types. Currently, you can view and update existing libraries.

1. Click Storage in the left menu, then click Libraries.
2. To edit an existing library, click the Edit icon ( ) in the Action column. Make the necessary changes and click Save.

Path Mappings

Path mappings provide a translator between two different storage systems. For example, if one storage uses Linux and another storage uses Windows, the path mappings translate the syntax so both storage locations can be used and understand each other. Currently, you can view and delete existing path mappings.

1. Click Storage in the left menu, then click Path Mappings.
2. To edit an existing path mapping, click the Edit icon ( ) in the Action column. Make the necessary changes and click Save.
3. To delete an existing path mapping, click the Delete icon ( ) in the Action column.

Dynamic Properties

Dynamic properties can be used for system configurations and workflow variables that need to be updated. Dynamic properties can be modified without restarting Reach Engine.

Display and Search Dynamic Properties

1. Click More in the left menu, then click Dynamic Properties.
2. Select a Dynamic Property. You can:

• Click the Edit icon ( ) in the Action column to edit the dynamic property.
• Click the Add icon ( ) at the top left to add a new dynamic property.

Create a Dynamic Property

1. Click More in the left menu, then click Dynamic Properties.
2. Click the Add icon ( ) at the top left to add a new Dynamic Property. The Create Dynamic Property panel displays.
3. Enter the key and value.
   
4. Click Add.
   

Enable Feedback Icon

Administrators can enable the Feedback () icon, which lets users provide feedback, request features, vote on feature requests, see what is in progress, and see which features were recently released. The Feedback icon is configured per installation. To configure the Feedback icon for your company, add a dynamic property with the following values:

• Key = feedbackEnabled
• Value = true

Search for a Dynamic Property

To search for a dynamic property, enter the property name in the search field. As you enter text, the list shortens to include only those items that match the entered text.

Exec Servers

Execution servers are separate from the Reach Engine server. They can be used to run processes and communicate with other servers including the Reach Engine server. Execution servers accept command line parameters to run transcoders, delivery services, etc.
For more information, please contact your Levels Beyond representative.

Display and Search Exec Servers

1. Click More in the left menu, then click Exec Servers.
2. Select an Exec Server. You can:

• Click the Edit icon ( ) in the Action column to edit an Exec Server.
• Click the Add icon ( ) at the top left to add a new Exec Server.

Create an Exec Server

1. Click More in the left menu, then click Exec Servers.
2. Click the Add icon ( ) at the top left to add a new Exec Server. The Create Exec Server panel displays.
   
3. Enter the server name, host, and port.
4. Select the server's operating system from the list.
5. To activate the server so that it can be used, move the Enabled slider to the right. If you choose not to enable the server during server creation, you can enable it later from the server list by moving the Enabled slider.
6. To allow commands to the server, check Online.
7. The Commands area is read only through the Admin tab. The information in the Commands area is populated by a TXT file that is installed when the exec server is installed. This command file specifies commands that can be run on this exec server, such as a transcoding command. For more information about commands, please contact your Reach Engine support team.
8. Click Add. An ID is automatically assigned to the exec server.

Enable/Disable Exec Server

To enable or disable an Exec Server, select the server from the list and move the Enabled slider.

Search for an Exec Server

To search for an exec server, enter the server name or host name in the search field. As you enter text, the exec server list shortens to include only those servers that match the entered text.

Live Servers & Feeds

Live servers allow you to stream and ingest live events into Reach Engine. Dynamic Clipping allows an organization to take in a live event video via an HLS stream, take clips off that live HLS stream, and post those clips onto the social media sites Facebook, Twitter, and YouTube. Most other assets from within Reach Engine can also be posted to social media sites, but each site dictates the assets it will accept. For example, YouTube does not accept documents.

Administrators must configure both the live servers and feeds as well as the linked social media accounts. When these connections are set up, users with permission can get content in front of digital viewers within minutes of real-time. Users can watch events as they unfold with full control of the playhead. They can create clips in the same fashion as library content, tagging them as they go. Clips are posted to social media via a seamless user action, resulting in expanding your audience in near real-time.

To view existing live servers, click the More menu, then click Live Servers & Feeds.

Create Live Servers & Feeds

1. From the More menu, click Live Servers & Feeds.
2. Click the + icon in the upper left (above the ID column). The right panel opens.
3. Enter a Name for the new linked account.
4. Enter the Address(URL) for the server.
5. Select the server Type.
   Note: Currently, Elemental Live is the only Type option.
6. Click Add.

Edit Live Servers & Feeds

1. From the More menu, click Live Servers & Feeds.
2. Click the Edit icon for the live server you want to edit. 
3. Edit the live server details as needed, then click Save.