Skip to main content
Question

Best practice for customizing Thinkwise-made validations in SF?

  • May 27, 2026
  • 2 replies
  • 27 views
P
Captain
Forum|alt.badge.img+8

When developing it could take quite a while to go over all validations, so to exclude messages that are not relevant we want the validations tailored to our situation to reduce as much overhead as possible.

Currently we have modified the validations base project in the SF (40 validations in total):

  • Turned off specific validations made by Thinkwise that are not relevant for us
  • Edited specific validations made by Thinkwise to add exempts for specific situations
  • Added own validations

After each SF upgrade the validations could be overwritten, so we create a branch for the validations project, copy all our changes to the branch and merge it back.

This doesn’t seem the most ideal way to go, specially since the base projects are locked now. What would be the best practice for customizing Thinkwise-made validations in the SF?

2 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Peter,

Coming in 2026.2, you'll be able to disable validations, alter the severity, and adjust the “can be approved” setting for validations. This will allow to tailor your experience a little bit.

For custom validations, I'd recommend a separate base model, and link that base model to the work models that should receive these validations.

Platform upgrade, like the one for 2026.2, may/will have data model changes that break your validations. This means you will have to fix them after an upgrade, but that is already the case if you have a branch of VALIDATIONS with your modified and custom validations.

So in short:

  • Turned off specific validations made by Thinkwise that are not relevant for us
    • Possible from 2025.1.15 STS and 2026.2 LTS
  • Edited specific validations made by Thinkwise to add exempts for specific situations
    • Possible by creating a branch of the base model and modifying it, with the upgrade risk
    • (undesired) or unlinking the validation in your work model and modifying the code
  • Added own validations
    • (Prefered) creating a base model with your custom validations and linking that base model to the work models needing these validations.
    • or by creating a branch of the VALIDATIONS base model
"Wake me up before you low-code"
P
Captain
Forum|alt.badge.img+8
  • PeterKeerisCaptain
  • Author
  • Captain
  • May 27, 2026

Great to hear you’re already working on an improvement.

For editing, maybe an equivalent of template-parameters could be added to the validation code so we can add extra lines to the validation code where statement without editing the original code. If it would be possible to only unlink the ‘custom where code’ from the base model it will require zero maintenance on SF upgrades.

For example:

insert into validation ...
select ...
 where model_id = @model_id
   and branch_id = @branch_id
   and [custom_where_code]
 

Terms & ConditionsAccessibility statement