tomy2105
tomy2105
I think deletion view should have those two methods too. This would allow you to have some custom actions after delete is done on server or custom handling if delete...
When a field has default value validation is not made against that default value (when displayed initially field doesn't turn red or green depending on default value). In addition if...
Thought I mention it here to save somebody else some trouble and time.... This is, not directly, fault of Elsa but of Visual Studio and the build tools it uses...
I believe this fixes #3020, maybe even #3001. I've tested `For`, `For Each`, `While`.... loop inside loop, etc..... What I don't know how it "interacts" with compensation activities......
Fixes #3031.... The changes in 3 catch handlers were needed to pass correct activity (current, not starting one) to `Fault` and Journal `AddEntry`. The additional `if (workflowInstance.WorkflowStatus != WorkflowStatus.Faulted)` was...
Elsa 2.7.0 from NuGet..... It seems that first/trigger activity is marked as faulted instead of the correct one. [wrong-error.zip](https://github.com/elsa-workflows/elsa-core/files/8680618/wrong-error.zip), second SetVariable has an error but HTTP Endpoint is marked as...
This solves #3022. In addition it solves #3247 and #3248 I've discovered while implementing #3022. I've also added new sample which demonstrate how to add new Activity derived from `HttpEndpoint`...
`getConfig` is visible in Javascript Monaco code complete even if not enabled in script options `EnableConfigurationAccess`.
Currently all input and output properties of an activity are visible in Javascript Monaco code complete (since `DefaultActivityTypeDefinitionRenderer::RenderTypeDeclarationAsync` adds them to the TS definition). For example for SendHTTPRequest activity: ...
I have a feeling that http connection is closed/flushed only when workflow instance is finished or suspended. I have workflow which has HTTP Response activity near beginning then some "lengthier"...