Support for Packages
　　A package is a container of rules and decision tables; and a package can contain other packages; thus allowing users to organize rules and decision tables in a hierarchical manner with the hierarchy running any deep. Elements of a package can be included in as many rulesets as required without any restriction on the number of inclusions, thus allowing users to reuse rules and decision tables. The properties of the included elements can be redefined in the ruleset in which they are included. If an element of a package needs to be modified, the modification needs to be made only in the source package, and all changes are reflected in the rulesets where the elements are included. This renders change easier to manage, and projects easier to create and update. The Repository now allows users to also store packages related to a project in the hierarchical structure in which it was created. Package versioning and access control are also made available.

Support for a Secure Channel
　　Typically, the repository is accessed by clients located across a network, in which case, most of the communication happens over a channel.Currently, the Repository provides support for working with the TCP and HTTP protocols. However, a need was felt to supplement support for these protocols with security over the wire. The 2.5 version of the QuickRules.NET Repository implements an algorithm that transports data securely. All information exchanged between the repository and its clients is encrypted, ensuring complete security to all transactions performed using the Repository.

Support for Encryption / Decryption
　　Although rules accessed using the repository were stored in a database, it sometimes becomes necessary to encrypt the data stored in the database to protect its integrity. The 2.5 version of the repository can now encrypt the data before saving it. This feature is available as a pluggable component, and be independently configured by the user to ensure complete project integrity.

Repository API Secured from Unauthorized Access
　　The repository exposes its functionality through the API for clients to be able to build custom applications on it. However not all API methods should be available for all categories of users. API that changes permissions on ROM objects, for instance, should be available only to a certain class of users (e.g.: administrators). As such it is necessary that these methods be restricted to only administrators. The QuickRules.NET Repository 2.5 now implements access permission checks for all administrative methods, ensuring that only authorized users are able to work with even the custom applications created using its API.

Authentication in the Repository
　　Before any operation can be performed on the QuickRules.NET 2.5 Repository, the user needs to provide appropriate authentication. Depending on the group to which the user belongs, permissible operations are enabled. The Repository offers this feature as a pluggable component, and if the user wishes to utilize the authentication module used within the organization, it can be plugged into the Repository.