Skip to content

[MS-1217] Adding custom OCR configuration#1434

Merged
alexandr-simprints merged 1 commit into
release/2025.4.0from
MS-1217-create-custom-config-for-mfid-ocr
Oct 29, 2025
Merged

[MS-1217] Adding custom OCR configuration#1434
alexandr-simprints merged 1 commit into
release/2025.4.0from
MS-1217-create-custom-config-for-mfid-ocr

Conversation

@alexandr-simprints
Copy link
Copy Markdown
Contributor

JIRA ticket
Will be released in: 2025.4.0

Notable changes

OCR configuration can now be set in Custom Config tab in Vulcan.

  • "ocrCaptures": 5 - sets how many images to run OCR on. Default is 3. Range: [1, 10]
  • "ocrHighRes": true / false - if true, captures high-res images to run OCR. If false, captures heavily-compressed images from the video feedback.

Additional work checklist

  • Effect on other features and security has been considered
  • Design document marked as "In development" (if applicable)
  • External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
  • Test cases in Testiny are up to date (or ticket created)
  • Other teams notified about the changes (if applicable)

Copy link
Copy Markdown
Collaborator

@ybourgery ybourgery left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the reason to not put this into the multiFactorId configuration? Is it something that should be temporary?

@sonarqubecloud
Copy link
Copy Markdown

init {
viewModelScope.launch {
ocrConfig = configManager.getProjectConfiguration().experimental().let { config ->
OcrConfig(
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not return the class directly from the experimental config? MIN/MAX could be defined in the experimental config the same way.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The settings are feature-related, and the idea was for the feature to provide the configuration data classes within its scope (as done with OcrCropConfig).

Currently, the values are coming from the experimental part of the project configuration, and I'd like to keep them atomic, and not feature-specific.

The idea is to test what project settings work best, and later move the configuration to Vulcan 'MF-ID' tab. That means that this part will be refactored in the following releases, and the only thing that we will need to change is where the setting values are coming from

@alexandr-simprints
Copy link
Copy Markdown
Contributor Author

What is the reason to not put this into the multiFactorId configuration? Is it something that should be temporary?

@ybourgery it is an experimental idea that me and @jonsimprints came up with, and we would like to experiment with the values before asking the Cloud team for the Vulcan implementation.

It's not yet certain whether we will need specifically these settings, something else, or none at all

@alexandr-simprints alexandr-simprints merged commit 0d864e6 into release/2025.4.0 Oct 29, 2025
13 checks passed
@alexandr-simprints alexandr-simprints deleted the MS-1217-create-custom-config-for-mfid-ocr branch October 29, 2025 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants