Copy Data
Last updated
Was this helpful?
Last updated
Was this helpful?
The Copy Data node only works in Runtimes v4.2 and up.
In current Shared Europe (v3 Windows) or 4.1 kubernetes runtimes, an error will show: "The current flowchart node is not supported by this version of the WEM runtime."
The Copy Data Node enables you to transfer data from a Source List to a Destination List with optional filtering. You can apply a list filter or filter expression to refine the data being copied with the 'source list filter' property. Additionally, a user-friendly Mapping overlay allows you to align source values with destination fields efficiently.
Once a Source List is selected, it cannot be changed. If a different source is needed, a new Copy Data Node must be created.
When copying to a persistent (database) list, the option Save directly to the database becomes available, allowing data to be stored immediately without requiring an additional save step.
If the Source List is a nested list, you can choose to limit the copy action to the context of the parent row. If this setting is disabled, all rows from the nested list will be copied across all parent rows.
Before defining the Mapping, the Destination List must be selected. This ensures that the source data can be correctly mapped to the appropriate fields in the destination.
By streamlining the data transfer process, the Copy Data Node makes it easier and faster to copy data between lists while maintaining accuracy and flexibility.
Use-case: Copy Sent Emails list to the email archive.
There is a transient/temporary list called Sent Emails that contains all recently sent emails and an email archive database list to keep track of sent emails.
The first step is locating the flow in which the process needs to take place and adding the Copy Data Node to the flowchart. This opens a popup where the source list is selected, In this case we select the Sent Emails list as this is the list where the application should copy from.
Once this is done the node is shown in the flowchart with the source list in the name. The next step is selecting the destination folder by dragging and dropping the list to the correct property or by selecting the property first. The filter field is left empty for this usecase as we do not use a filter for now, this field can be used for a filter or filter expression to select a certain set of rows from the source list.
As there are no other actions in this process and no additional steps need to be saved, we can enable saving directly to the database, eliminating the need for a Save Database Node.
In the previous section the node has been set up and added to the application flow with the right properties. The node now needs to know which fields are supposed to go into which field of the destination list. For this example, this is straightforward because the source and destination have the same name; however, this is not always the case, so mapping is always necessary.
The mapping screen can be opened by selecting 'Edit Mappings' in the node properties or by double-clicking the node.
The destination fields can now be selected by either clicking the 'Add' button at the top left of this window, clicking the dotted line box, or dragging and dropping the destination fields into the dotted box. The add button and clicking the box will open a overlay with the available destination fields to select.
The added fields are displayed in two columns: the destination field name on the right and the source value column on the left. The source values are typically fields from the source list, directly inserted into the expression field. Alternatively, they can be expressions that generate values or values derived from other fields through expressions.
