Issue with HandleViewModelAttributeChangeRequest — Incomplete Value Handling on Input

Hello Community,

We are experiencing an issue with calculated fields in Creatio using the HandleViewModelAttributeChangeRequest handler, as described in the official documentation.

The implementation generally works as expected, but we've observed a problem when users input decimal values quickly. For example, when entering “8,11”, the handler sometimes receives only “8,1” — effectively missing the last digit. This seems to happen because the handler is triggered before the full value is finalized in the UI.

We would appreciate any help on the following:

• How does the Creatio UI handle attribute change events internally?
• Is there any debounce or delay mechanism before triggering HandleViewModelAttributeChangeRequest?
• Is it possible to delay or debounce this handler to ensure that the value has been completely entered before processing?

Are there any best practices or alternative patterns recommended by Creatio for implementing calculated field logic that depends on precise and complete user input?

Best regards.