LogoLogo
To the Oz WebsiteOz API ReferenceContact Us
  • General
    • Oz Liveness and Biometry Key Concepts
      • Solution Architecture
      • Liveness, Face Matching, Black List Checks
      • Passive and Active Liveness
      • Hybrid Liveness
      • Oz API Key Concepts
      • Oz API vs. Oz API Lite
      • SaaS, On-premise, On-device: What to Choose
      • Oz Licensing Options
    • Integration Quick Start Guides
      • Server-Based Liveness
        • How to Integrate Server-Based Liveness into Your Web Application
        • How to Integrate Server-Based Liveness into Your Mobile Application
        • How to Check Your Media for Liveness without Oz Front End
      • On-Device Liveness
        • How to Integrate On-Device Liveness into Your Mobile Application
      • Face Matching
        • How to Add Face Matching of Liveness Video with a Reference Photo From Your Database
        • How to Add Photo ID Capture and Face Matching to Your Web or Mobile Application
  • Guides
    • Developer Guide
      • API
        • Oz API
          • Working with Oz System: Basic Scenarios
            • Authentication
            • Uploading Media
            • Liveness
            • Biometry (Face Matching)
            • Best Shot
            • Blacklist Check
              • Blacklist (Collection) Management in Oz API
            • Quantitative Results
            • Using a Webhook to Get Results
            • Single Request
            • Instant API: Non-Persistent Mode
          • System Objects
          • User Roles
          • Types of Analyses and What They Check
          • Rules of Assigning Analyses
          • Statuses in API
          • Media Tags
          • Metadata
          • API Error Codes
          • Oz API Postman Collections
          • Changelog
        • Oz API Lite
          • API Lite Methods
          • Oz API Lite Postman Collection
          • Changelog
      • SDK
        • Oz Mobile SDK (iOS, Android, Flutter)
          • On-Device Mode
          • Android
            • Getting a License for Android SDK
              • Master License for Android
            • Adding SDK to a Project
            • Connecting SDK to API
            • Capturing Videos
            • Checking Liveness and Face Biometry
            • Customizing Android SDK
              • How to Restore the Previous Design after an Update
            • Android Localization: Adding a Custom or Updating an Existing Language Pack
            • Android SDK Methods and Properties
            • Changelog
          • iOS
            • Getting a License for iOS SDK
              • Master License for iOS
            • Adding SDK to a Client’s Mobile App
            • Connecting SDK to API
            • Capturing Videos
            • Checking Liveness and Face Biometry
            • Customizing iOS SDK Interface
              • How to Restore the Previous Design after an Update
            • iOS Localization: Adding a Custom or Updating an Existing Language Pack
            • iOS SDK Methods and Properties
            • Changelog
          • Flutter
            • How to Install and Use Oz Flutter Plugin
            • Flutter SDK Methods and Properties
            • Changelog
        • Oz Liveness Web SDK
          • Web Plugin
            • Adding the Plugin to Your Web Page
            • Launching the Plugin
              • Description of the on_complete Callback
              • Description of the on_result Callback
              • Capturing Video and Description of the on_capture_complete Callback
              • Description of the on_error Callback
            • Closing or Hiding the Plugin
            • Localization: Adding a Custom Language Pack
            • Look-and-Feel Customization
              • Customization Options for Older Versions (before 1.0.1)
            • Security Recommendations
            • Browser Compatibility
            • No-Server Licensing
          • Changelog
    • Administrator Guide
      • Deployment Architecture
      • Installation in Docker
      • Installation in Kubernetes
      • Performance and Scalability Guide
      • Publishing API Methods in the Internet: Security Recommendations
      • Monitoring
      • License Server
      • Web Adapter Configuration
        • Installation and Licensing
        • Configuration File Settings
        • Configuration Using Environment Variables
        • Server Configuration via Environment Variables
      • Oz API Configuration
    • User Guide
      • Oz Web UI
        • Requesting Analyses
        • Users and Companies
        • Blacklist
        • Statistics
        • Settings
        • Changelog
  • Other
    • Media Quality Requirements
    • Oz SDK Media Quality Checks
    • Media File Size Overview
    • Compatibility
    • FAQ
    • Tips and Tricks
      • Oz Liveness Gestures: Table of Correspondence
      • Sudo without Password
      • Android: Certificate Validation Error
    • Previous Documentation
      • Mobile SDK
        • Android
          • Interactions with the Oz API Server
          • Uploading and Analyzing Media
        • iOS
          • Uploading and Analyzing Media
      • User Guides
        • Oz Demo Kit
        • Web UI
      • Oz Modules Installation
        • Standalone Installer
        • Oz System Lite
Powered by GitBook
On this page
  • How to Create an Order for Analysis
  • Filters

Was this helpful?

Export as PDF
  1. Guides
  2. User Guide
  3. Oz Web UI

Requesting Analyses

PreviousOz Web UINextUsers and Companies

Last updated 1 year ago

Was this helpful?

How to Create an Order for Analysis

  1. Click the Create order button on the Orders tab.

2. Select media files to upload to the system or drag and drop them to the selected area.

3. After the download is complete, the analysis types become available for selection. By default, there are all possible checkboxes.

  • Document check – recognition and verification of the document fields.

Uncheck the (or not installed components) analysis types you don't need.

4. Next, select tags – the type of content for each uploaded file and at the end click the Submit analysis button.

  • Options for choosing the Document type (you can load several pages of one document at once):

    • Document with photo

    • Document without photo

  • if there is a face in the image, not a document, select the Selfie content type.

  • For videos, only Selfie is available along with qualifying tags:

    • orientation: Portrait or Landscape

Please note: if the tags are chosen incorrectly, the analysis results might be flawed.

5. Upon the analysis completion, you'll see the results for the previously selected analysis types:

  • analysis succeeded – everything went fine;

  • analysis failed – faces don't match, Liveness check failed, an error emerged during the processing, etc.;

  • operator required – this means the system requests for the additional check made by your employee.

To get the detailed result for a specific type of analysis, click on the mark near the analysis' name.

OPERATOR and CLIENT OPERATOR can change the analysis verdict. These roles have access to an additional button: Make decision.

To change the verdict, the user should select the decision from the drop-down menu and click Apply.

Once analyses are finished for a folder, this folder gets status according to the analyses' results:

  • SUCCESS– everything went fine, all analyses completed successfully;

  • OPERATOR_REQUIRED – there are no analyses with the DECLINED status, but one or more analyses have been completed with the OPERATOR_REQUIRED status;

  • DECLINED – one or more analyses have been completed with the DECLINED status.

The other two statuses that you might encounter are FAILED and INITIAL. FAILED means that one or more analyses are finished with an error. INITIAL stands for folders with no analyses applied.

A report on the study will be available in the PDF format by clicking the PDF list button (1) from the list of orders. For this option to become available, you should have a pre-configured report template for your company.

Any order can be deleted either by clicking the Trash bin button from the list of orders (2) or by clicking the Delete button from the order form.

Filters

Analysis orders can be filtered by several parameters. The scope of visibility is limited by the access rights of your user's role.

  • In the Orders tab, click the Filter button

  • you can use one or more fields for filtering:

    • Order number – enter the full alphanumeric order number or type the first few characters.

    • Date/time – the range of dates of orders' creation.

    • Company – the company that owns the orders.

    • Manager – the user who created the orders.

    • Consolidated folder status – the overall analyses' result for the folder.

    • Analysis type – the type of the analysis applied.

    • Analysis result – choose the result to display all orders where one or more of the analyses have been completed with this result.

    • Meta – you can filter orders by specific meta tags by adding their name and value using the Add button. A meta tag is any information that a programmer can transmit when submitting an order via API. Enter the name and range of values into the field manually.

  • After filling in the fields, click the Search button.

  • To reset the current filter, hit the Reset button.

– comparing multiple photos and assessing the level of similarity.

– compare the uploaded photo with the scammers' photos from the blacklist database.

– an algorithm for determining liveliness is designed to check the presence of a living person by a short video fragment. The checkbox is available for selection only when uploading a video.

type of action (what action was performed by the person in the video): scan, turn left, turn right, turn down, turn up, smile, close eyes. The video with a certain type of action is recorded via the and . For regular videos, use the Scan tag.

Image Biometry check
Blacklist check
Liveness
Oz Mobile SDK
Web SDK