📄️ Rules engine
TMS provides customers with a generic approach to model its test processes. Different business entities al-low to the administrator
📄️ Write your first rule
To get a quick understanding of the integration of rules into TMS we start with a quick example:
📄️ Validator
The “validator” is a global variable, which is available in each TMS rule.
📄️ Session context
The “sessionContext” is a global variable, which available in each TMS rule.
📄️ Function libraries
When uploading rules files, TMS offers the functionality to declare those as libraries. The following example shows a function which just calculates the average of 2 number:
📄️ Examples
Along with some examples in following a few ideas for how to write rules in the Drools language and therefore enhance your
📄️ API - Activity
The attribute class provides read and write access to attributes of resources, activities and projects.
📄️ API - ActivitySeries
The ActivitySeries abstract class represents a series of related activities.
📄️ API - Attribute
The attribute class provides read and write access to attributes of resources, activities and projects.
📄️ API - AttributeGroup
The AttributeGroup class represents a group of related attributes.
📄️ API - Project
The Project abstract class represents a project in the TMS system.
📄️ API - Resource
The Resource abstract class represents a resource (e.g., person, department, equipment).
📄️ API - Restriction
The Restriction class provides validation constraints for attributes.
📄️ API - SessionContext
Provides information about the context of the current rules execution.
📄️ API - TMS
The TMS enum defines global constants for identifying different fields and entities in the TMS system.
📄️ API - User
The User class represents a user in the system.
📄️ API - Validator
The Validator interface provides methods for issuing warning and error messages during rule execution.