Hi! Real happy that you have introduced the new zip functionality, but i have some questions regarding deeply nested folder structures and the limitations of use.
Nested folder structures:
Lets say i have a folder structure with a 4 layer depth (1. – 1.1 – 1.1.1 – 1.1.1.1 File) and want the zip file to keep this structure identical when downloaded, what would be the best way to achieve this using the path property on the action node?
Limitations of use
I am struggling to understand if the limitations of 1GB per month stated in the product glossary regarding the file archive action node also applies if you only use the “download immediately” option for the file target?
Hi, regarding #2, the 1GB limit is for the total size of files “sent” to be archived in a given month. Whether you store the final archive in your solution or download it immediately has no impact on this quota.
With regards to specific pricing please get in touch directly with your Appfarm representative.
The included 1GB is a generous quota that will meet the needs of most solutions. We’ve structured it this way to ensure that the vast majority of our solutions can utilize this feature at no additional cost.
For some solutions, particularly those with more intensive use cases or larger-scale operations, this feature becomes a core part of their workflow. The higher quotas are designed to support these power users who derive significant value from the increased capacity.
Our goal is to maintain a sustainable model that allows us to continue developing and supporting this feature for all users while also meeting the needs of our most demanding use cases. We believe this approach strikes a balance between accessibility for all and scalability for those who need it most.
Hi, regarding your first question I would use a Javascript function to set the path. I have solved a similar case with two levels in the picture below, where rootFolder is the name of the first level and folder is the name of the folder in level 2.
