:=¶
Description¶
:= always has an information field on its left (domicile, risk_level, etc.), and any kind of expression on its right
side.
Attaching a condition with := to a field, means the field will only be assigned a value based on this condition if it
doesn't already have a value.
If a user has already provided a value for the field, the system will not override that value.
To assign to a structure field, assign it a list of dictionaries.
Success
This operator can only be used when writing the assignment part of a process rule.
Values that do not fit the field¶
Info
New in Atfinity 17.
An assignment only happens when the value fits the configuration of the field it is assigned to. When the value is longer than the field allows, is not one of the field's options, or breaks any other limit set on the field, the field keeps the value it had and the Case Error Log records which rule tried to assign to which field, and why the value did not fit. A rule that reads the field afterwards sees the value the field kept, never the value that did not fit. A field that had no value stays empty, and counts as missing for as long as the rule keeps assigning a value it cannot hold. Some fields are not checked at all, and keep whatever the rule assigned to them: structure fields, fields that link instances, option fields with no list of options configured, and Number with Unit fields with no units configured. A calculated field is only checked when it is a Text, Single Line Text, option or Decimal field.
Examples¶
The field tax_countrywill be assigned the same value as the field domicile, unless another value for
tax_countryhas already been provided.
The service attached to this contract will be 'Asset Management', unless another service has already been entered in the
field service.
The field full_name will receive a value that is the combination of the values in the fields first_name and
last_name, separated by a space.
Again: only if the field full_name hasn't already been assigned a value.