Important! Read this.

We have launched a new documentation website. If you're using Enterpise Edition 10 (or higher) or Express/Business Edition 2.4.1 (or higher), visit this page.

Skip to end of metadata
Go to start of metadata

We have moved to a new documentation platform. This section is no longer supported. For the up-to-date information, see Check criminal records.


Check Criminal Records is a sample Business Process that gets a list with person's first name, last name and date of birth as an initial data set, opens the web-site and searches for criminal records using the Input data. Then, depending on whether the site has been found or not, the workflow decides either to process the information automatically or shift it to the Workspace to be processed by a Worker as a Manual Task. If the task goes to the Workspace, the workflows finishes upon completion of the Manual Task. If the workflows proceeds automatically, the brief information acquired (search results) is saved to the local S3 File Storage in HTML format (a file per person). At the next, a complete profile of the person is saved to the local S3 File Storage in the same way. Then the information about the criminal record is extracted and saved in the Business Process Output data.

Business Process Structure

Input Data

To view and change, if necessary, the input data go to the Data tab. In this Business Process the Input Data contain a list of person's first name, last name and date of birth (Personal data) to be used for the search on the web-site.

Click Next to proceed to Business Process Design to check the workflow and Business Process steps.

Business Process Workflow and Steps

Go to the Design tab to see the entire Business Process workflow and check each particular step (Task or Rule).

Attention

Tasks can incorporate variables, which are used to transfer the data from one Task to another or identify an external source (for example, pre-defined S3 bucket) for Task's input data. Such variables are declared externally, for example in configuration files and not included to the input data for the Business Process.

In such case, you will see the warning message as below:

The warning message is redundant, so you can skip it.

Workflow

The workflow of the current Business Process consists of the following steps:

  1. Start (initial step)
  2. Find Criminal Records  >>
  3. Manual or Automatic Processing >>
  4. Collect data in Workspace >>
  5. Save search results to S3 >>
  6. Save profile to S3 >>
  7. Extract information from profile >>
  8. End (final step).

Double click a Task to see its structure and properties.

Business Process Steps


Step 1 – Workflow Start

Workflow is initiated and started. The workflow is executed in cycles per each record from the Input data.


Step 2 – Find Criminal Records

Step 2 is a Bot Task. At this step, a record from the Input Data (Personal data) is checked on the web-site. If the site is found, the Bot harvests the information for the automated processing.

Input data:

  • 1 record per cycle – Personal data, defined in Data (in columns first_name, last_name, dob).

Bot Task:

  1. Check, if the site can be accessed:
    1. Site accessible:
      1.  Put this information in the Output data.
      2. Open Duval County Clerk of Courts


      3. Put the Personal data from a record in the Input data in the respective fields on the site.

    2. Site is unreachable:
      1. Put this information in the Output data.
  2. Repeat for each record from the Input data.

Output data: 

  • 1 record per cycle containing:
    • Site access attempt – found or not
    • Personal data – first name, last name, date of birth
    • Search for person – found or not 
    • Search result – brief information, if the person found by name as XML
    • Person profile – detailed information, if the person found by name and date of birth as XML
    • Case ID – ID of the criminal record
    • Case information – further details of the case
    • Search URL – the link to search on the site
    • Source name – the name of the body who owns the site

Step 3 – Type of process

Step 3 is a Rule to to decide depending on the attempt to access the site, if the workflow goes on automatically or the task should be completed by a Worker in the Workspace.

Input data: 

  • 1 record per cycle with the information from the Step 2.

Rule

  • Bot Task – the site is accessible (site_change is false)
  • Manual Task – the site cannot be accessed (site_change is true)

Output data:

  • 1 record per cycle with the data from the Step 2 either to the next Bot Task or to the Workspace.

Step 4 – Collect Data in Workspace

Step 4 is a Manual Task performed by Workers to collect the information in the Workspace.

Input data: 

  • 1 record per cycle with personal data – first name, last name, date of birth.

Manual Task: 

  1. A Worker should find the information about criminal records manually and fill in the Answer form.

Output data: 

  • All records processed by a Worker.

Step 5 – Save Search Results to S3

Step 5 is a Bot Task to save the search results for first and last names to the local S3 File Storage as an HTML file.

Input data: 

  • 1 record per cycle with the information from the Step 2.

Bot Task: 

  1. Save the search result from the Input data to the local S3 File Storage.

Output data: 

  • 1 record per cycle with the information from the Step 2.

Step 6 – Save Profile to S3

Step 5 is a Bot Task to save the Person profile to the local S3 File Storage as an HTML file.

Input data: 

  • 1 record per cycle with the information from the Step 2.

Bot Task: 

  1. Save the Profile from the Input data to the local S3 File Storage.

Output data: 

  • 1 record per cycle with the information from the Step 2.

Step 7 – Extract Information from Profile

Step 7 is a Bot Task to extract information from the Profile. 

Input data: 

  • 1 record per cycle with the information from the Step 2.

Bot Task: 

  1. Extract the following information from the Profile:
    1. Linked attorney – the attorney, who took part in the proceedings
    2. Department – police department
    3. Offence date – date of the law violation
    4. Officer badge – officer badge number
  2. Append the extracted information to the Output data.

Output data: 

  • 1 record per cycle with the information from the Step 2 with the additional fields containing the extracted information.

Step 8 – Workflow End

Workflow complete.


Run Business Process

To start the Business Process go to the Run tab.

  1. Click Run This Process to initiate execution of the Business Process.
  2. If the Business Process succeeds to launch, the following message window emerges:
  3. Click View Results to go to the Results tab to check how the Business Process is executed according to its workflow or View Business Processes list to return to the Business Processes Overview.

Business Process Execution

During execution of the Business Process you can check the results of execution for the entire Business Process and each particular Task:

  • Business Process execution results on the workflow:

    An icon in the Task's upper right corner indicates, if the Task is automatic (Bot) or Manual. Below each step you can see the step progress in percents and ratio between incoming and outgoing records.
  • On the Results page
    • 2 records from Data processed, Search results and Profile from the records are saved to S3, information extraction complete for 1 record, record 2 is in progress:


  • Search results in S3


  • Profile in S3

Business Process Complete

When all Business Process's Tasks are complete and submitted, the Business Process finishes.

  • Workflow view:


  • Results tab view:

Check Results

During execution of the Business Process or upon completion you can check the results of execution for the entire Business Process and each particular Task.

The overall progress is displayed in Submission Statistics in the Results tab:

Click the progress bar on a Task to view the records created by each step.

  • No labels