Allow user to collapse a scope to a smaller box with the name visible. This would allow a better overall view by hiding implementation details

A feature to wrap selected tasks in a scope

Highlight the tasks where a specified variable is read or written. This would help to understand large processes and to debug issues.

Extend Regex task to return capture gruops based on a pattern.

It would be great if you could create a task for merging separate pdf files in to one file. It seems like using pdfsharp could be a simple solution for this task. https://www.pdfsharp.net/wiki/ConcatenateDocuments-sample.ashx

IBM MQ tasks for receiving and sending messages.

Businesses are transitioning to PEPPOL as it offers a more secure and reliable way to exchange business-critical information between companies for things like purchase order, sales orders, invoices and more. It's developed as a EU standard, but also in a way that allows for the format to adapt over time without losing consesus. What's more is that PEPPOL connects participants in their network to ensure that business transactions are stored and delivered, which ensures that things like invoices always make it to recepeints with the terms those entail. EDI, while having been useful for many years, has never achieved a sufficient level of standardization, which means it's prone to a lot of customization, and carries higher operating costs. With a task for PEPPOL, it would allow businesses to accelerate supply chain automation connected to critical business transactions between companies, and make it more reliable.

Better parsed message structure for Edifact tasks, using official Edifact property names in parsed output instead of more generic parse results.

Task for parsing and creating HL7 documents