This article outlines our current roadmap for the Flowgear platform and is updated quarterly. Please note that this article is published for informational purposes only and does not constitute a commitment from Flowgear with respect to capabilities or timing.


Q1 2019

  • Build REST Request Connector that consumes Swagger definitions for samples and execution
  • Add tree-style containers to Workflows, Connections and DropPoints list
  • Allow trial users to sign up in closest region
  • Enhancements to activity logs including auto-loading of earlier and later logs, 
  • Persist Console session in browser storage to improve experience when working with multiple tabs

Q2 2019

  • Add client-side controls for extending session lifetime
  • Improve expired session recovery in Console to automatically re-execute last task after renewing session
  • Add support for certificate-based trust for DropPoint authorization
  • Modify Activity Logging to include meta data for root, parent and current workflows (improves usability of logs in Workflow-specific seaches)
  • Provide support for custom security roles and the ability to configure permissions at the object container level
  • Provide support for third party assemblies in Script Node when executed at DropPoint
  • Extend Workflow Promotion feature under Release Management so that multiple Workflows can be atomically promoted. Also stop auto-promoting revision 1 to all Site Environments

Q3 2019

  • Enhance Workflow flow control to provide try/catch/finally support with stack trace
  • Extend metadata available for exceptions (additional properties will likely include source Node ID, message, stack)
  • Implement parallel-processing at Workflow level. This feature will enable Workflows to call sub-Workflows in parallel
  • Modify Site Configuration data so it is persisted per Site Environment
  • Tentative: Provide authorization of Flowgear user accounts from Microsoft Active Directory

Q4 0219

  • Provide deeper self-service facilities for custom Node management including ability to revoke specific revisions. The security architecture will also be reworked so that users have more precise control over where custom Nodes can be executed

Did this answer your question?