FlowSynx v1.1.3 is officially released!

We're excited to roll out version 1.1.3 of FlowSynx — our lightweight, secure, and plugin-driven workflow engine.

Features​

• Add workflow metrics summary feature via API
• Add user-specific event publishing for task updates
• Add LastModified property (#438)
• Add Status to the AddWorkflowTrigger (#439)
• Add AddEventPublisher service into WorkflowOrchestrator to publish event (#437)
• Add AddEventPublisher service (#436)
• Add IEventPublisher and its implementation to support event submiting (#435)
• Add WorkflowHub to make Executions list update (#433)
• Add authenticaton token to the hub communication (#432)
• Add SignalR to the service collection to make application ready to use Hub (#431)
• Add position to the workflow task (#430)
• Add ExecuteWorkflowResponse and change code to return ExecuteWorkflowResponse instead of WorflowExecution Id only (#429)
• Add new feature to get list of workflow execution tasks (#427)
• Modify IWorkflowTaskExecutionService All method to add WorkflowID in query data (#426)
• Add ability into JsonDeserializer to remove trailing commas before ] or } (#425)
• modify gitignore file and add result path to the ignores list (#424)
• Add Workflow Queue Configuration (#422)
• Add DurableWorkflowQueueService based on PostgreSQL (#421)
• Add InMemoryWorkflowQueueService (#420)
• Add ability to configure Https endpoint (#417)
• Add Cors policy feature (#416)
• Add ability to return version in required as argument (#414)

Other Changes​

• Order logs by descending TimeStamp in LoggerService
• Delete the code related to SignalR hub and clean-up code (#434)
• Change WorkflowExecutionDetailsResponse to return workflow definition and workflowid also (#428)
• Replace throw exception with actual result return in GetApprovalStatusAsync (#423)
• Introduce an execution queue mechanism so that workflows are first enqueued and then executed by a background processor in FIFO order (#419)
• Refactor the code to support IClaimsTransformation (#418)
• Clean up the code (#417)
• delete unused log (#417)
• Update getting started link (#415)
• Update SECURITY.md file (#413)
• Update README file (#412)
• Correcting typo (#408)
• Update README file (#408)
• Update CONTRIBUTING file (#409)
• Delete plugin virtual solution folder (#410)
• Correcting BasePath in Storage configuration section (#411)

📦 Available now via GitHub, and Docker.

FlowSynx v1.1.2 is officially released!

We're excited to roll out version 1.1.2 of FlowSynx — our lightweight, secure, and plugin-driven workflow engine. This release focuses on performance improvements, stability enhancements, and continued support for scalable, no-code automation.

Thank you to the community and contributors helping shape FlowSynx into a powerful platform for orchestrating workflows across cloud and on-prem environments.

📦 Available now via GitHub, and Docker.

Welcome to the FlowSynx blog!

We’ve created this space to share FlowSynx news and a variety of content from and for the FlowSynx community. This content may include deep dives into specific technical topics, examples of how FlowSynx can be used in various scenarios, and other interesting contributions from the community.

Whether you're an experienced developer, a solution architect, or just getting started with FlowSynx, this blog is designed to offer insights, tips, and inspiration to help you get the most out of our platform. Expect regular updates covering topics such as:

• Behind-the-scenes updates on new features, roadmap items, and architectural decisions.
• Step-by-step guides and tutorials to help you build and deploy your own custom workflows and plugins.
• Use case spotlights showing how FlowSynx is being applied across different industries and real-world scenarios.
• Community contributions including guest posts, extensions, integration ideas, and tips from users like you.
• Best practices and design patterns to help ensure your solutions are robust, secure, and scalable.

We believe in building together, and your feedback, questions, and ideas are not only welcome—they’re essential. We hope this blog becomes a valuable resource for learning, sharing, and connecting with others in the FlowSynx ecosystem.

Stay tuned, and thanks for being a part of the FlowSynx journey!