Skip to content

Person ​

Selects an HCAPP user through the form's user selector.

When to use ​

Use it for an internal contact or a named colleague associated with a task. Choose Form for a customer or driver represented by a separate record, and Text for a name that is not an HCAPP user. Author represents task creation metadata instead of a manually chosen person.

Settings ​

The backend schema supports name, default value, bold text, title inclusion, and inline layout, together with common workflow conditions.

Selecting a person does not grant access to the task. The optional Set responsible setting assigns the selected user when a task is created; otherwise configure workflow responsibility separately. The current backend request schema does not define an automatic-current-user setting for Person.

See shared field settings for workflow visibility, requirements, and layout options supported by this type.

Backend type: PersonField.

Auto fill from the selected user ​

A super-admin opens Profile → Configuration → form → Fields → Person, enables Auto fill, maps each destination field to a user attribute and saves the field.

Available attributes: full name, first name, last name, email, phone, Telegram, position, department, branch, rate, working hours and absences.

DestinationSource
NumberRate
EmailEmail
PhonePhone
Text / TextareaUser attributes, including readable working hours and absence periods
LinkA text value; make sure the chosen attribute is meaningful as a link

Working hours and absences are inserted as readable text, not as editable Schedule or Date fields. Selecting a person copies values into the mapped task fields. Selecting another person overwrites those fields; clearing Person clears the mapped values. This is not a live link that updates old tasks whenever a user profile changes.

For example, map Rate → Hourly rate (Number) and calculate cost using that value multiplied by a separate Hours field. See working hours, absences and rate.