Solved

Zip file / Delete folder connector requires full path to Source folder

  • 1 March 2023
  • 2 replies
  • 57 views

Userlevel 2
Badge +1

Can somebody explain why the full path to the Source Folder (pointer) is required in a “Zip File” or “Delete Folder” connector (see image below)? 

 

For these connectors, a storage location is already specified in the Process Action. So, to let this process action work, we’ve to include the storage location in the path. However, this decreases the maintainability. Changing the Storage location in the model, will also require an update of the process flow.

I would expect a relative folder to be set in the “Source file or folder” for these actions.
 

Am i missing something?

icon

Best answer by Mark Jongeling 1 March 2023, 11:19

View original

This topic has been closed for comments

2 replies

Userlevel 2
Badge +1

Hi Mark,

 

Thanks for your reply. In the process flow the Write file connector is used, so i will investigate the possibility to retrieve the absolute path from the output.

 

Userlevel 7
Badge +22

Hi André,

When implementing these process actions, the initial implementation led to that the Delete process actions and the Zip file use Absolute paths over Relative paths. That is due to for example the Write file path outputting the Absolute path for you to store in your database. That path can then be used to Delete the file.

We are aware this is causing more difficulties than being helpful and have User stories on our backlog to revise this.