Rafael Menezes

Hi Andreas, Thank you very much for the detailed feedback and suggestions! I just updated our environment from version 2.8.2 to 2.8.3, and I'm happy to report that it completely solved the issue regarding the parameterization of ports and other numeric/boolean values. This helped me a lot in simplifying our YADE configurations. The update couldn't have come at a better time—I had been struggling with this limitation over the past few weeks and hadn't noticed the new release earlier this month. I...

Hi Andreas, First of all, I apologize for posting in the wrong forum! It seems I can't move the thread myself, so if an admin could move this to "Help" or "Open Discussions," I’d appreciate it. Thank you for the detailed feedback. Let me clarify my current architecture and assumptions: Generic Profiles & Job Resources: I’m actually following your advice on generic workflows. I’ve created about 10 YADE profiles in the Inventory that use variables (e.g., ${source_host}, ${source_dir}). These profiles...

Hi everyone, I'm currently implementing a JS7 solution to handle thousands of different workflows for SFTP transfers using YADE. A large portion of these workflows will send files to customers, so I plan to use File Order Sources for these (since I need to monitor different directories and send to various destinations). The rest will use Schedules to pull files from remote SFTPs where I can't install an agent. Given the volume, I’ll likely have around 5,000 workflows running daily, split roughly...

Hi everyone, I'm currently implementing a JS7 solution to handle thousands of different workflows for SFTP transfers using YADE. A large portion of these workflows will send files to customers, so I plan to use File Order Sources for these (since I need to monitor different directories and send to various destinations). The rest will use Schedules to pull files from remote SFTPs where I can't install an agent. Given the volume, I’ll likely have around 5,000 workflows running daily, split roughly...