Handler - ChangeStamp
ChangeStamp handler generates automatically a new value in the target attribute field. The handler responds to the change of the parent attribute's value with stamping the target attribute with a new value. The target attribute must be denoted it by its individual attribute code in the parent attributes metadata.
For example, if the target attribute's value is editor's ID, the value appears automatically in the target attribute field when the user edits the parent attribute's value. In the following picture, the ChangeStamp handler belongs to the Contract contact person attribute. The target attribute denoted in the Contract contact person's metadata is Last changes by. Since a user whose ID is AndyB is currently editing the Contract contact person attribute, the Last changes by field gets automatically the value AndyB.
Last changes by attribute with ChangeStamp handler:

Target attribute's datatype appoints the target value that can be a string, a reference, a date or a date and time. If the target attribute is a string, the stamped value is always a user ID. If the target attribute's is a reference, the value is a reference to the editor's User card by default. If the target attribute is date or date and time, the value will be date or date and time.
Use the ChangeStamp handler with attributes, whose change of value you want to observe.
The following tables provide information on the attribute settings and metadata requirements for ChangeStamp handler. Compulsory metadata is provided in a Required attribute metadata table including proposals for possible metadata values.
Table 1. Attribute Settings
| Handler name | Datatype |
|---|---|
ChangeStamp |
Any except embedded reference |
Table 2. Required Attribute Metadata
| Name | Value | Description |
|---|---|---|
stamp_target |
[attribute_code] |
Attribute code of the targeted attribute that gets stamped. Value of the target attribute depends on the data type of the target attribute. Valid datatypes are string, reference, date, date and time. |
Table of Contents