Encrypted Field RRTs

AutoStore supports encrypted fields with protected RRTs and restricted RRTs.

Protected RRT

A protected RRT encrypts its replacement value through all components in a process and shows as encrypted in Status Monitor. A protected field value remains encrypted when the Knowledge Package builder component stores or reads information in XML format.

Restricted RRT

A restricted RRT has the same characteristics as a protected RRT with the addition that it can only be used in fields that are explicitly marked in a configuration to use restricted RRTs. These are typically password fields.

Using protected RRTs

Prepend the field name with an $

You can create a protected field by using the dollar sign ($) as the first character of a field name. An FRTN that starts with the $ defines a protected RRT.

For example, a field named $invoice defines an encrypted field. The $ as the first character in the FRTN, as in ACC::%$invoice%, defines the corresponding protected RRT. The $ at the beginning of the file name signals AutoStore to encrypt values that it saves to the field and decrypt values when it evaluates an RRT string.

Using restricted RRTs

Prepend the field name with a @

You can create a restricted field by using the at sign (@) as the first character of a field name. An FRTN that starts with the @ defines a restricted RRT.

For example, a field named @invoice defines an encrypted field. The @ as the first character in the FRTN, as in ACC::%@invoice%, defines the corresponding restricted RRT. The @ at the beginning of the file name signals AutoStore to encrypt values that it saves to the field and decrypt values when it evaluates an RRT string.