Released: March 2022
This release contains no new features.
This release contains no functionality changes.
This release contains the following changes to third-party libraries:
The jQuery library was updated to version 3.6.0.
The jQuery UI library was updated to version 1.13.1.
This release contains no closed issues.
This release contains the following known issues:
Schema compilation does not support all rule types. If you want to use action permission rules to set service permissions, you have to add the 'com.orchestranetworks.addon.rpfl.DefaultRulesSchemaServicePermission' class to those services manually.
You must keep your D.E.C.'s current. This is especially true if you add or remove the mandatory attribute, the computed value attribute or maximum number of values attribute from a data model field.
Default classes are those available to be added automatically-including the default schema extension. However, one data model can only have one schema extension. So, if you have your own schema extension in the data model, you have to remove it from the data model before adding a default class. To reuse your programmatic access rules, invoke them in the add-on using the method described in the appendix.
From version 1.5.0, the add-on provides the following views: 'D.E.C. hierarchy' on D.E.C. table, 'Rule by D.E.C. hierarchy' on Rule table, and 'Rule execution by D.E.C. hierarchy' on the Rule execution table. However, on the old snapshot of the add-on, new views do not display any data. In this case, you have to use the default view or the old view.
This release contains the following known issues related to the scripting language:
The script does not support to 'query' data by the association node.
The script does not support to modify data on other data spaces. You can modify data on the current data space only.
The wizard panel only shows the model of the data set that the rule will execute.
Released: December 2021
This release contains no new features.
This release contains no functionality changes.
The jQuery library was updated to version 1.13.0.
This release contains no closed issues.
This release contains the following known issues:
Schema compilation does not support all rule types. If you want to use action permission rules to set service permissions, you have to add the 'com.orchestranetworks.addon.rpfl.DefaultRulesSchemaServicePermission' class to those services manually.
You must keep your D.E.C.'s current. This is especially true if you add or remove the mandatory attribute, the computed value attribute or maximum number of values attribute from a data model field.
Default classes are those available to be added automatically-including the default schema extension. However, one data model can only have one schema extension. So, if you have your own schema extension in the data model, you have to remove it from the data model before adding a default class. To reuse your programmatic access rules, invoke them in the add-on using the method described in the appendix.
From version 1.5.0, the add-on provides the following views: 'D.E.C. hierarchy' on D.E.C. table, 'Rule by D.E.C. hierarchy' on Rule table, and 'Rule execution by D.E.C. hierarchy' on the Rule execution table. However, on the old snapshot of the add-on, new views do not display any data. In this case, you have to use the default view or the old view.
This release contains the following known issues related to the scripting language:
The script does not support to 'query' data by the association node.
The script does not support to modify data on other data spaces. You can modify data on the current data space only.
The wizard panel only shows the model of the data set that the rule will execute.
Released: January 2021
The add-on no longer supports the Document Type Definition declaration in XML files. If this causes an exception, the add-on will inform you that this declaration is not allowed.
Release Date: September 18, 2020
The add-on has been updated to support the OpenJDK8 and OpenJDK11 libraries.
Libraries were updated to fix some potential issues.
Release Date: June 23, 2020
The jQuery library has been updated to version 3.4.0.
[RPFL-563] An add-on description in French is not translated.
Release Date: June 20, 2019
The add-on has been updated to ensure compatibility with the TIBCO EBX® 5.9.4 release.
Release Date: February 15, 2019
[RPFL-550] D.E.C. does not show all tables and fields in the hierarchy view.
Release Date: October 26, 2018
The EBX® Rules Portfolio Add-on has undergone significant updates to ensure compatibility with the EBX® 5.9.0 GA release.
Release Date: May 19, 2017
[26010] A new button is available on the 'Java Implementation' tab to clear your selection when configuring the 'Property data' type as Boolean.
[26011] An exception occurs when deploying on an application server that strictly validates web.xml.
Release Date: May 9, 2017
[08337] It is now possible to search for a specific rule implementation when creating new rules.
[10356] A new UI is available to select which rules execute after launching the 'Execute rules' service.
[20490] The 'Publish rules portfolio' service now can be used to override an old publication.
[19505] [Documentation] The user guide for scripting language needs to be updated.
[15487] A wizard has been added to facilitate business rule configuration.
BusinessRuleDefinition's API Javadoc has been updated to clearer information.
It is now possible to get the label of hook in the Hook's API.
Release Date: January 23, 2017
[23916] The 'Business/Permission rules logging' group has been changed to record in the Logging Level table.
Permission and validation rules have been optimized so that the overload against a pure Java EBX® API implementation is insignificant when implementing a Java based rule.
[23454] There are always error messages in the log file when starting EBX® Rules Portfolio Add-on in an empty repository.
[23788] Portfolio - import XML error.
Release Date: October 12, 2016
D.E.C. creation is based on the data model instead of data space and data set.
The Java implementation post-fix is changed to (A), (V), (M), and (T).
In the EBX® Rules Portfolio Add-on UI, services have been improved and are more user-friendly.
The D.E.C. records will now display using the correct structure based on their types and relationships in the data model.
On the rule execution table, only the 'Rules' field is displayed instead of the two fields 'Rule' and 'Rules set'. An option is available that allows you to select one or the other.
You can now apply the existing rule publication to other data spaces instead of creating a new publication with the same content.
The API's Javadoc has been updated to provide more in-depth information.
[21555] Unexpected exception occurs when importing an XML file.
[21707] User should not be allowed to delete the predefined configuration provided by the add-on.
Release Date: May 19, 2016
With the new wizard displaying on the right of script editor, you can easily insert a record object property or table path to the script. This wizard will display the full structure of the data model on which the script will be executed.
Now all predefined objects and their published methods are available in the script editor's contextual help.
New methods in the 'session' object check whether the user is in administrator or read-only role.
New methods in the 'query' object allow users to query data from another data set, or data space.
Release Date: April 13, 2016
This version is only compatible with EBX® 5.7.0 fix C or higher.
Previously, to enable the EBX® Rules Portfolio Add-on, you had to manually add default classes to your data model. Now, schema compilation automatically adds any required classes.
Dependencies limit validation execution to the specific events of interest, such as on node creation and deletion. It is now possible to set a dependency on a validation rule applied to a field using the 'Dependencies' tab in the UI. Previously, this functionality was only available via an API in the context of a constraint and its containing data model.
It is possible to migrate your old data and improve backward compatibility using classic access rules.
Release Date: December 11, 2015
[18519] Ajax validation using a scripting rule does not take into account a record's updated value.
Release Date: December 2, 2015
[18471] A value of 0 is reported as invalid input for the 'Value' field, which is located in the 'Java implementation' tab's 'Property data' group.
Release Date: November 19, 2015
[18129] An exception occurs when executing a scripting rule on a field.
Release Date: November 3, 2015
Script execution has been optimized.
Release Date: October 9, 2015
[17710] An exception occurs when executing a scripting rule on a field.
Release Date: September 16, 2015
Scripting language is a newly available and significant feature that allows you to define a rule by writing a script in scripting language. See the Scripting Language for more information.
You can now define conditions for rule execution by using a script or Java implementation instead of using 'Context' and 'Simple expression'.
Rules now execute on publications of rule configurations and no longer execute via the EBX® Rules Portfolio Add-on configuration. A new data set, 'TIBCO EBX™ Rules Portfolio Add-on - Production', contains the 'Rule publication' and 'Rule repository' tables. Respectively, these tables store:
Published snapshot information.
Mappings between data spaces and rule publication.
A new 'Publish rule portfolio' service is available on the 'TIBCO EBX™ Rules Portfolio Add-on' data set. This service creates the publication of rule configuration and saves all information in the 'Rule publication' and 'Rule repository' tables, which are located in the 'TIBCO EBX™ Rules Portfolio Add-on - Production' data set.
New services are added into 'Context', 'Simple expression', 'Rule publication' and 'Rule repository' tables which allow users to delete records from these tables.
Release Date: January 26, 2015
You can now execute a 'Validation rule' using a constraint set on a field.
The logging data set is now divided into two data sets in relational mode: 'Rules Portfolio - Logging' and 'Rules Portfolio - Logging archive'. Logging configuration has been moved to the 'Logging level' group in the 'TIBCO EBX™ Rules Portfolio Add-on' data set.
A new EBX® task can execute the archive log procedure using the EBX® scheduler.
A new "Purge log" service is available on the "Rules Portfolio - Logging archive" data set. This service deletes the log data from imported archives.
A new "Query log" service searches log data using criteria, such as, User ID, data space, data set, table, execution time, etc.
New classes DefaultConstraint and DefaultConstraintOnNull execute validation rules via constraints.
Release Date: June 10, 2014
In order to improve the rule execution response time, 'Manual validation rules' now execute in a multi-threaded environment.
The rules execution context is extended with a 'User-Profile' property that activates or deactivates a rule depending on the user/profile combination.
The following pre-built rule properties are now configurable:
'Is active'
'Data set execution'
'User profile'
Release Date: April 14, 2014
The EBX® Rules Portfolio Add-on is extended with a new traceability function to track rules execution. An automatic archiving process is applied to keep log over time. A purge service is used to clean up the logs on demand.
Release Date: January 24, 2014
The EBX® Rules Portfolio Add-on manages two categories of rules:
The 'Business rules' for the data validation that are executed from triggers or through the EBX® data validation service. They are classified into four types as follows:
'Automated rule' can modify the user data. It is executed through triggers on tables and raises an error in case of failure.
'Validation rule' cannot modify the user data. It is executed through triggers on tables and raises an error in case of failure.
'Manual rule' cannot modify the user data. It is executed by a user through the EBX® validation service, and raises either an error or a warning.
'Table set rule' can modify the user data. It is executed by a user through the 'Execute rules' service.
The 'Permission rules' for the rights management that is implemented in compliance with the EBX® permission scheme applied to data and services. They are classified into two types as follows:
'Access permission rule' defines permission for data set, table, field or record.
'Action permission rule' defines permission for service.
Every rule is configured through a set of metadata such as:
'Property data': Parameters that can be modified at the level of the configuration, and used as input data for the execution of the rule. These properties are defined through the Java Interface that allows to publish a rule into the EBX® Rules Portfolio Add-on.
'Is active': a rule can be active or inactive (the rule is deactivated). It is not possible to execute the rule even if the other conditions of the execution are valid.
'Validity date': date from which the “Rule execution” can be executed.
'Expiry date': date from which the “Rule execution” is impossible to execute even though it is configured to be active.
'Data set execution(s)': one or more data sets can be selected as a context of execution. This means that the rule execution happens only if the execution is requested in the defined data sets. It is possible to use the special tokens '[All data spaces]' and '[All data sets]'.
'Simple expression': used to define the conditions under which the rules can be executed.
A set of predefined business rules are available to get 'True' or 'False' results directly. By combining these assertion rules with the 'Simple expression' configurations, it becomes possible to create new assertion rules based on any field of a table:
[ON] Assertion true (Manual validation)
[ON] Assertion true (Validation)
[ON] Assertion true (Table set)
[ON] Assertion false (Manual validation)
[ON] Assertion false (Validation)
[ON] Assertion false (Table set)
A set of predefined permission rules are available:
[ON] Hidden service
[ON] Disable service
[ON] Enable service
[ON] Hidden the data set
[ON] Permission read-only for the data set
[ON] Permission read-write for the data set
[ON] Hidden table
[ON] Permission read-only for the table
[ON] Permission read-write for the table
[ON] Hidden field
[ON] Permission read-only for the field
[ON] Permission read-write for the field
[ON] Hidden record
[ON] Permission read-only for the record
[ON] Permission read-write for the record
Java API for declaring rules into the EBX® Rules Portfolio Add-on.