...
The section of the configuration allows users to map the Convertr Fields to the excel spreadsheetFile Output
On the left-hand side, this is the naming of the columns on the right-hand side these are the fields that those columns will be referencing.
...
The leads sent to this file type will be stored in the database and encrypted. They will only be appended to the existing CSV file when the reports runs at the scheduled time. This means that any of the new leads that have been deleted, invalidated, marked as test or undelivered will all be removed from pending batches, right up until the scheduled delivery date and time.
Scenarios
As a user of Batch CSV Integration, I should be able to:
Scenario | |
---|---|
“default” type | Schedule my batches to send all the valid “On hold - pending batch” leads between each batch window. E.g If I set my batch to run 9 am everyday, on Tuesday I would expect all the compiled leads since 9 am Monday → to 8:59 Tuesday morning to be in a single file |
“cumulative” type | Each schedule should append the “On hold - pending batch” leads to a single file and send it. Using the example above, by Friday I would see all of the leads from Monday, Tuesday, Wednesday, Thursday and Friday morning in a single file. The file would still be sent to its destination as normal at 9 am each day with all leads for the time period. |
Info |
---|
I should be able to run multiple batches on a single campaign without the files conflicting with each other, either using job groups or value-based routing, or just having two batches which collect different information. I should be able to zip and password protect my files - this should work with cumulative and default batch types and not impact the expected behaviour of each type - this seems to be broken with cumulative files. “Password protecting” seems to just send the new leads, and not append to the existing file. When the file is sent it should use the configured filename in the settings to create the actual filename. |
CSV Delimiter
...
The CSV delimiter will only be used if the file format is set to CSV. This setting determines how the CSV is separated.
...
Below are all the placeholders:
Placeholders | Description |
---|---|
%campID% |
...
This will pull through the Convertr Campaign ID |
...
%campaignName% |
...
This will pull through the Convertr Campaign Name |
...
%Y% |
...
theyear that file was created eg 2020 | |
%y% | theyear that file was created showing the last 2 digits of the year eg 20 |
%D% | eg theyear that file was created (non-numeric) eg Mon, Tue, Wed |
%d% |
...
the day that file was created (numeric) eg 01,02,03 | |
%H% |
...
the hour that file was created in a 24-hour format eg 23:00 | |
%h% | the hour that file was created in a 12-hour format eg 11 |
%i% |
...
theminute that file was created eg 00:01:00 | |
%M% | the month that file was created (non-numeric) eg JAN, FEB |
%m% |
...
the month that file was created (numeric) eg ) 01, 02 ,03 etc | |
%s% | the seconds on when the file was created with leading zeros eg 00:00:01 |
Info |
---|
Finally, the file can be saved with .XLSX , .CSV or . |
...
TXT conventions. |
Path
...
This setting is used when configuring a connection for either and FTP, SFTP, SFTPS and or Dropbox.
When using the path the user can specify exactly , in the directory when the file needs to be saved.
Info |
---|
Eg /mainfolder/subfolder/saving folder |
Send ZIP (recommended)
...
For the send ZIP, this allows the user to put a password on the file.
...