Set here the following parameters to define how the action will be performed.
Settings
Web service URL: The URL on which the Aurora web services are available (i.e. where test plans and tasks status are managed) must be specified in the following format: http://AuroraServer:port/APIService.
For instance: http://AuroraQC:1001/APIService
User: Username for accessing the web service.
Password: Password for authenticating the username in the web service.
Test plan: The Aurora test plan is to be used to verify the media file. For instance: Quality Test
NB: The test plan must be entered exactly as set in the Aurora server (Template Editor).
NB: Plans are created on the configuration page (e.g. http://auroraqc/Aurora/login.aspx).
Save in the asset's EDL: Indicate the number of the EDL (default is 8) in which Aurora results (i.e. detected segments issues) will be written.
If Quality Check reports errors: Specify the behaviour in case an error is detected:
Exit with ERROR status (default) - Exit the action with the "Error" status
Proceed through the OK exit - Exit the action with "OK" status, allowing the T-workflow to continue although the negative result of the QC.
Save result file on DB: If this option is enabled, any virtual documents or reports uploaded to the workflow action would be saved into the database when saving the workflow action.
Use api version 5.1.311.0: If this option is enabled, it will enable the compatibility with Digimetrics api version 5.1.311.0
Note: Parameters support integrating Etere T-workflow and Aurora are based on the Etere.WF.Aurora.exe executable.
File access permissions
Aurora's logged user must have enough file access permissions to access the source network storage device. Otherwise, the action will end in error (318767105: File not found or not accessible). Permissions are configured during the Aurora setup; they can be manually added from the "Windows Services" module.
Although permissions are given during Aurora's setup process, they can be manually configured by setting the "Aurora Controller" and "Aurora Verifier" windows services accordingly. For further details, please refer to the manual of Digimetrics Aurora.
Depending on the success of the operation, the action will return one of the following results:
OK - The web service was connected, the file was found, and the verification was positive.
ERROR - The web server was not connected, the file was not found, or the verification was negative.
In case Digimetrics Aurora determines that a file verification is negative, a message will be included in the asset's T-workflow log (Error: Result parsed file: This stream has "n" errors and "n" warnings).