1.3.2

Fixes

• Null target type throws for array expressions (#416)
• Fix inaccurate parsing of HTTP headers (#417)
• Add custom type serializer to manage json deserializer from database (#420)

1.3.1

Improvements

• A small improvement was made that allows activities to sub-class Join to inherit join-like behavior. An example was added as part of Sample25.

Fixes

• When resuming workflow instances without explicitly specifying blocking activities to resume now correctly uses the blocking activities by default.

1.3.0

This release contains the following:

Fixes

• Reverse WorkflowInstanceEntity.Scopes on deserialization (#342) by @iyhammad
• Correct sample paths (#284) by @iyhammad
• Fix bug in ForEach activity when the collection is empty (#313) by @Dandevmt
• Updating ContentType in SendHTTPRequest to match WriteHTTPRequest (#322) by @martinisaksen
• Add Exception property to WorkflowFault (#283) by @aburada
• TriggerRequestHandler workflows to resume filtered by X-Correlation-ID header(s) (#289) by @flew2bits
• Make AutoMapper internal to avoid collision with other frameworks like ABP (f44d7e1) by @sfmskywalker
• Make Dashboard NotifierFilter work for non-controller based applications too, like ABP (d3032a8) by @sfmskywalker
• Foreach generic list bug (#303) by @mertyildiz41
• Update ForEach to expose Done and Iterate outcomes (#285) by @mertyildiz41

Thanks to all contributors for making this a release with many great improvements!

1.2.2

This release contains the following:

Fixes

• Literal expression now supports non-empty but blank string values (#250) @wakuflair
• Fixed stackoverflow when finding ancestors (#247) @jamesdoran
• Improve JS value converter to support object target type @sfmskywalker

1.2.1

This patch release includes a fix allowing Elsa Dashboard to be hosted in IIS.

The reason the dashboard application could not be hosted in IIS was due to the fact that IServer was being decorated, causing some IIS startup filter to fail with an exception message along the lines of: "Running in an IIS process but the server is not configured to run in IIS".

The reason IServerwas decorated was to implement a startup task runner that would execute before the web server starts accepting requests.

However, with .NET Core 3, we can use IHostedService to implement async initialization tasks.
For more information, see Andrew Lock's blog post

1.2.0

This release contains the following:

❗️ Breaking changes

Persistence Provider Registration

When registering your persistence provider, you now need to specify the DbContext type to use. For example, when using EF Core with SQL Server, do this:

services.AddElsa(x => x.AddEntityFrameworkStores<SqlServerContext>(...));

Timers Background Task

The TimersOptions in Elsa.Activities.Timers now uses the Duration type for the SweepInterval setting, instead of Period. Duration makes more sense, semantically speaking. This affects the value you specify in your appettings. For example, to configure the sweep interval to be every 5 minutes, your appsettings would look like this:

{
   "Elsa": {
      "Times": {
         "SweepInterval": "0:00:05:00"
      }
   }
}

🔨 Fixes & Changes

• Fixed yaml serialisation and updated to YamlDotNet (#236) - @jamesdoran
• Replaced YamlDotNet.NetStandard with YamlDotNet (#225) - @jamesdoran

⭐️ New Features

• MySql Support for EF Core (#222) - @terry-delph

1.1.5

This release contains a few fixes:

Fixes

• #220 Fixed Serialization for Objects (@jamesdoran )
• #219 A second operation started on this context before a previous operation completed (@sfmskywalker )
• Fixed Readme file in Elsa.Persistence.EntityFrameworkCore with functioning connection strings (omitting double-quotes) (@sfmskywalker )

1.1.4

This release contains fixes and new features:

Improvements

• Added PostgreSQL persistence provider (@nhughey-evo )
• Added Startup activity (@Andale-online )
• Custom Entity Framework Core schema support (@nhughey-evo )
• YesSQL now stores schema version, preventing the provider from trying to create tables that were already created (@jamesdoran )

Fixes

• YesSQL workflow instance store fixes (@jamesdoran )
• Variable serialization fixes (@jamesdoran )
• System DateTime and NodaTime serialization fixes (@sfmskywalker )

Misc

• Added an Elsa icon to the packages.

Many thanks to the contributors who made this release possible!

1.1.3

This release contains the following improvements and fixes:

Improvements

• Switch activity is now case-insensitive (@jamesdoran) #182
• Switch activity now supports a default branch (@Andale-online) #136
• Jint's AllowCrl is now optional (@jamesdoran) #179
• Connections are now hooked up by case-insensitive outcome names (@jamesdoran )
• New and improved MassTransit activities (@petedavis )
• Reflection-based activities (ExecuteMethod and SplitObject) (@Andale-online ) #132
• MassTransit's ShoppingCart example (Sampl21) now implemented using an Elsa workfow (@petedavis )

Fixes

• Fixed SendEmail concurrency (@Andale-online) #147, #150
• Entity Framework provider throwing errors #144, #145
• YesSql Provider throwing errors #125, #119 , #118
• MassTransit Workflow Consumer now executes in its own scope (@petedavis ) #134

All issues closed as part of the 1.1 milestone: https://github.com/elsa-workflows/elsa-core/issues?q=is%3Aissue+is%3Aclosed

Many thanks to all contributors involved in this release!

1.1.2

This release contains mostly bug fixes:

• Error handling for invalid expressions (#131)
• Multiple activity registrations of the same type would cause duplicate key exception (#128) (@jamesdoran )
• Fixed issue where named activities couldn't be used with Then() (#129) (@jamesdoran )
• Improved table list view (#127)
• Fixed broken YesSQL provider
• Improved workflow variables serialization (#120)

Many thanks to the contributors who tested, reported and fixed these issues!