English

Search for content...

Change file field

In the automations of an activity type, the Change file field action automatically populates a File or Gallery type field when the trigger is fired. The files can come from attachments defined within the action itself, from another field in the same activity, or from a field in the parent activity.


Accessing the action

  • Open the main menu, select the Activities module, click on Settings, and then on Activity types.

  • Open the desired activity type and access Automations (Triggers and actions).

  • Create a new automation or edit an existing one.

  • In the Actions block, click on + Add, and under Action type, select Change file field, under the Change dynamic activity fields category.

75%

The Change file field block is displayed. In the Reference file field, choose where the files will come from:

75%

Note: Despite the name of the action, the source and destination fields can be of either File or Gallery type.


Using default file

Use this option to always include the same files (for example, a template or an instruction document) in the destination field.

  • Default file: click on + Add file to attach the documents. Each file can have an optional comment, which is transferred as a description to the destination field. Use the trash can icon to remove a file.

  • Destination field (required): select the File or Gallery field of the activity type that will receive the files.

75%

A File type field accepts only one attachment. If you attach more than one file, choose a Gallery type field as the destination. Otherwise, the configuration will not be accepted.


Using field from the activity itself

Use this option to copy files from one field to another field within the same activity.

  • Source field (required): File or Gallery field from which the files will be copied.

  • File description: check Copy source file description to also transfer the description of each file. Unchecked, the files reach the destination without a description.

  • Destination field (required): field that will receive the files.

75%

The destination field must be of the same type as the source field: File to File, Gallery to Gallery. Additionally, only galleries that can hold the number of files from the source field are available as destinations. The others appear disabled in the list.


Using field from the parent activity

Use this option in subactivities to bring files from a field in the parent activity to a field in the subactivity.

  • Source field (parent activity) (required): when clicked, opens a tree-style window showing the activity types that can be a parent activity (including the type itself) and their File and Gallery fields. Only activity types you have permission to view are shown.

  • File description: check to also transfer the file descriptions.

  • Destination field (required): field of the subactivity that will receive the files.

75%75%

Here, too, the destination field must be of the same type as the source field. If the source gallery has more files than the destination gallery can hold, only the first files are copied and the rest are not transferred.

Tip: If you choose the same activity type as both source and destination, the files considered are always those of the parent activity.


When the action is not executed

  • If the source or destination field is no longer associated with the activity type, the action is not executed, and the activity log records the reason.

  • With the parent activity option, if the subactivity's parent activity is of a type that does not have the source field configured, the action is also not executed.


Tracking changes

Each execution is recorded in the activity's Change logs card, showing the date, user, and event, for example: "The "Contract" field was changed from "empty" to "Doc.pdf"". The Last Update field, in the activity overview, also updates to show the date of the change made by the automation.

Full