Support:
E-mail: support@netal.com
Forum: support.netal.com
Phone: +43-1-5851414

DisclaimIt 3.x - New Features
Product
Download
License Information
Order Information
New Features

DisclaimIt 3.3 contains the following new features:

  • The new optional Format parameter of Print Directives allows text to be inserted to be converted to lower or upper case.
  • The message processor will now process the HTML text part of a message even if the HTML text part is not validly constructed, i.e. is missing <HTML> or <BODY> tags.

 DisclaimIt 3.2 contains the following new feature:

  • A new placement condition has been added to placement policies: Date range.

DisclaimIt 3.1 contains the following new feature:

  • A new filter criteria was added to processing rules: Recipient filtering by AD group membership.

DisclaimIt 3.0 contains the following new features:

  • Support for processing of internal and inbound messages.
  • Support for rich-text messages. Rich-text messages are processed like plain text messages, this means that the plain texts of text modules are added to rich-text messages, with the added functionality that the font properties of an added plain text are preserved in the resulting message text.
Changed Features

DisclaimIt 3.0 implements changes to the following features:

  • The font properties of the texts of a text module are now stored along with the text. They are no longer saved in the MMC file (.MSC) as global properties. This change was implemented to allow for different font properties per text because the font properties are preserved and used when the plain text is added to a rich-text message.
Removed Features

DisclaimIt 3.0 does no longer support the following features:

  • Excluded external domains have been removed. When upgrading from a previous version, the excluded external domains are added as excluded recipients to every processing rule.
  • The feature of adding the address ignore@disclaimit.test to the recipient list to prevent processing of this message by the message processing engine has been removed. Two workarounds are possible: Either configure on a processing rule a header fields filter for a specific trigger word in the Subject header field or configure a placement policy to not add text if a specific trigger word is found in the message text.