DCS Services 2.4.0 and SysPack 24.0.1
February 9th, 2024
This update brings refinements to the Computer Vision processor, performance improvements, security updates, and multiple out-of-the-box examples for better user enablement and productivity.
Mandatory Changes
The Simplified Processor Settings for Computer Vision have a restructured JSON schema which you will have to update on existing implementations. Since the new schema does not support multiple document types in the same processor settings entry, you may have to create additional processor settings for each document type and refactor other dependencies.
What's New
Computer Vision Updates
Support for Romanian Passports
Romanian passport MRZ scanning, body parsing, and validations have been added to OCR. See the automation blocks documentation for the full list of validations supported.
Simplified Processor Settings
The AvailableDocumentTypes and Validations processor settings for Computer Vision have been merged into a single setting called DocumentSettings with a simplified structure:
"DocumentSettings": {
"DocumentType":"Passport",
"Provider":"Azure",
"Validations":"V01,V05,V06,V07,V10",
"RequiredFields": ["PersonalNumberBody", "DocumentNumberBody", "LastNameBody", "GivenNameBody", "NationalityBody", "PlaceOfBirthBody", "BirthDateBody", "SexBody"]
}You must now create dedicated processor settings for each document type as you can no longer define multiple document types in the same processor settings entry.
Required Fields
The new DocumentSettings key also allows you to specify mappings that are mandatory for a successful scan, as shown in the example above.
In-Processor Validations for Romanian IDs
In addition to the validations performed by the OCR service (V01, V06, V10 etc.), Romanian identity cards now support two new validations for the birthday and personal identity number (CNP). These validations are performed by the OCR processor after receiving the OCR service response. For more information see the Computer Vision documentation.
Example Use Cases
You can find examples in FintechOS Studio for how to use automation processors in real life scenarios, with complete data model, flow settings, and journey configurations.
| Processor | Form Driven Flow | Flow Settings |
|---|---|---|
| Computer Vision | FTOS_Test_OcrFDF | FTOS_Test_OCR |
| Liveness and Face Recognition | FTOS_Test_FaceRecognitionFDF | FTOS_Test_FaceRecognition |
| Video Streaming | FTOS_Test_Operator FTOS_Test_Moderator |
FTOS_Test_Operator_Client |
| Video Streaming (recording) | FTOS_Test_RecordingFDF | FTOS_Test_Recording |
| eSign | FTOS_Test_ESign | FTOS_Test_ESign |
| Co-browsing | FTOS_Test_Cobrowsing | FTOS_Test_Cobrowsing |
| AriadNext | FTOS_Test_AriadNext | FTOS_Test_AriadNext |
| Onfido | FTOS_Test_Onfido_FDF | FTOS_Test_Onfido |
Fixed Issues
| Processor | Issue |
|---|---|
| Video Streaming |
The moderator was not able to join the video call due to an unexpected error. |
| Video Streaming | The operator's call queue was not refreshed regularly. |
Known Issues
| Platform Version | Issue |
|---|---|
| 20.2.11 | There is a video streaming issue when importing the FTOS.ECOS.Utils client script library - not working with async/await or when refreshing the page. |