Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Allow transfer of file without deleting source

Avatar

Avatar
Shape 1
Level 4
eeidbgsu
Level 4

Likes

82 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Shape 1
Shape 10
Boost 50
Boost 5
Boost 3
View profile

Avatar
Shape 1
Level 4
eeidbgsu
Level 4

Likes

82 likes

Total Posts

17 posts

Correct reply

0 solutions
Top badges earned
Shape 1
Shape 10
Boost 50
Boost 5
Boost 3
View profile
eeidbgsu
Level 4

14-02-2019

The Transfer File step in a workflow can be configured to optionally delete a source file after transferring the file when the protocol is SFTP or Amazon S3.

This option is not available when the protocol is "File(s) present on the Adobe Campaign server".

If I am developing a new workflow or am troubleshooting an existing workflow, I may want to run the workflow on the same file several times.  It is inconvenient to have to upload the file to the Campaign server each time I run the workflow because the Transfer File step automatically deletes the file.

Please add a "Delete the source files after transfer" option for the "File(s) present on the Adobe Campaign server" protocol so that the workflow author can turn this option on and off as needed.

2 Comments

Avatar

Avatar
Affirm 1
Employee
Perrininho
Employee

Likes

0 likes

Total Posts

42 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back
Establish
View profile

Avatar
Affirm 1
Employee
Perrininho
Employee

Likes

0 likes

Total Posts

42 posts

Correct reply

1 solution
Top badges earned
Affirm 1
Give Back
Establish
View profile
Perrininho
Employee

10-06-2019

Hello, this option has been added for cleansing process. We can't change this behaviour for files hosted in Campaign Server.

Please use a S3 or SFTP protocol for this use-case.

Avatar

Avatar
Level 1
gary_h_dev
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
gary_h_dev
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
gary_h_dev
Level 1

02-03-2020

I don't like Eric's reply here:

1) The system defaults to NOT deleting the file for the other methods, so users expect the same behavior for all methods.

2) Documentation does NOT currently say the file will be deleted.

3) Users expect the Historization settings in this Activity to be followed. Selecting "file on server" does not gray out or disable Historization settings, so we expect them to continue to be followed.

4) Historization already exists. Why do we need to automatically delete the file on top of that?

 

Either documentation needs to be updated, or the GUI needs to make it clear that the behavior of "file on server" is different from the other methods - specifically that Historization is not respected.