Experience the Power of Trisotech Digital Enterprise Suite - Discover the cutting-edge features that revolutionize data validation in a low-code environment. With Trisotech, you can effortlessly validate data based on their defined data types, empowering both IT and business professionals. By externalizing and generalizing data validation aspects, you can optimize decision-making, streamline processes, and enhance case management. Boost your operational efficiency with automated services, while minimizing production errors.
Learn the art of defining constraints using personalized messages and system codes, and witness how these constraints seamlessly integrate into the services you create and deploy.
Call Girls In Sikandarpur Gurgaon ❤️8860477959_Russian 100% Genuine Escorts I...
Data Validation in a Low-Code Environment
1. Trisotech.com
Data Validation in a
Low-Code Environment
Using Trisotech Digital Enterprise Suite
Presented By
Simon Ringuette, Trisotech
Mélanie Gauthier, Trisotech
2. Trisotech.com
Introduction
Data validation in low – code services created using the DMN and BPMN standard.
Pros and cons of using different data validation methods
How Trisotech implements Data Validation at the Data Type level.
3. Trisotech.com
Overview of Modeling and Automation
Trisotech offers a Modeling suite that implements popular business oriented OMG
standards such as BPMN, CMMN and DMN to model Workflow, Cases and
Decisions.
4. Trisotech.com
Overview of Modeling and Automation
Trisotech also offers an automation platform that uses those models augmented with low-code attributes to
create containerized services.
5. Trisotech.com
How people typically do data validation in DMN
Extra decisions and logic added
Data manipulation to ensure correctness
Decision failure when unexpected data is encountered
o Identifying the cause is harder for end-user
7. Trisotech.com
Introducing enhanced data validation
Three predefined rules
o Range, enumeration and not null
Powerful expression
o All the power of FEEL with auto completion
o Values of previous fields can be used
o Multiple expression can be combined (AND)
Each rule may have its own user-friendly message
o Easier for users to understand what is wrong
o Default messages provided by the DES
Error code can also be set for easier API integration
Fail fast
8. Trisotech.com
Data validation level
Three levels of validation
o None
o External data entry
o Always
Setting in the preference for testing
Through the deploy modal for services
10. Trisotech.com
Turning the model in a service
Validation error returns a 400 HTTP response
o Message
o Code
o Location
Only when validation level is set to Always or External data entry.
12. Trisotech.com
Showcase in Workflow automation
Validation rules can be defined on the four modelers supporting data types
o Decision, Case, Workflow and Knowledge Entity
Shared across models when reusing from the graph.
Data validation levels available in Workflow and Case automation.
Some validation needs to be done in the flow, Worfklow automation should be used in that case.
Ouvrir le modèle Time Off Request – Original
Expliquer l’exemple (data store pour le nombre de jour de vacances et service pour le nombre de working days)
Montrer le data type, une seule contrainte, une énumération standard
Montrer l’appel du service avec la manipulation pour mettre le From/To en ordre au besoin
Exécuter le modèle sans mettre de date, on a une erreur avec un message cryptique
Montrer la logique de approve avec la justification requise pour le family day
Same expression as the input of a decision table
Fail fast: avoid unnecessary call that would fail anyway
None : No data validation at all
External data entry: For values entered by user (input data in DMN, data input in BPMN)
Always: Also validates between decisions (if previous decisions introduces invalid data, it will log an error)
Always requires more processing
It should be use while developping the models to ensure correctness
External should be use when the model is ready for production
Faire un save as du modèle Time Off Request
Aller modifier tTime Off Request
- Vérifier le level dans les préférences
Mettre not null à employee ID, from and To
mentionner le allow null sur l’énumération
Test with no value to view the default messages
Aller modifier To pour mettre une contrainte after(?, From) or From = ?
Aller modifier Justification pour le mettre obligatoire si le type est Family dev
if Type="Family day" then ? != null and string length(?) > 5 else true
A justification of at least 5 characters must be provided for family days
Tester les conditions
Aller simplifier le modèle: enlever le mapping du start/end et la colonne de justification
Location is the name of the data plus the path
Deploy the model making sure data validation level is set to External data entry
Select the diagram in the tab
Briefly show the RestAPI file with the 400 code
Run the test form, show the different errors in there too (Employe 1, 1 day, 7, 7 days and 14 14 days)
The validation about the employee that is found or not makes the DMN model complex for no reason.
This can be moved out and be done by a Process instead
Open Time Off Request – To be used by process
No more data store here, we expect the Remainging days
Time Off Approval is now simpler too, only the decision
Open the process model
Show the data type, it has all the same expressions
Show the handling of the error through condition
Test the previous rules to show it works the same
Show the rule on the response (reason provided when rejecting)
Deploy
Test it and manual rejection on the user task, we have the error there too