elsa-workflows / elsa-website Goto Github PK

Should we have a section to describe all implemented activities?

Hello Team ,

I want to connect Elsa.Sample.RabbitMQWorker to Elsa Studio to visualize the workflow but unable to connect it.. Please let me know how to connect console workflow to Elsa Studio.

TIA
Regard
Rahul

I am getting the below reference errors in my dotnet core 3.1 application.
1.) I am trying to generate an absolute URL containing the security token as "context.GenerateSignalUrl("Approve")" but getting error as below:
'ActivityExecutionContext' does not contain a definition for 'GenerateSignalUrl' and no accessible extension method 'GenerateSignalUrl' accepting a first argument of type 'ActivityExecutionContext' could be found (are you missing a using directive or an assembly reference?)

2.) I am trying to divide the workflow into multiple branches as "activity => activity.WithBranches("Approve", "Reject")" but getting erros as below:
'IActivityBuilder' does not contain a definition for 'WithBranches' and the best extension method overload 'ForkExtensions.WithBranches(ISetupActivity, params string[])' requires a receiver of type 'ISetupActivity'

It would be great if anyone could let me know what I am missing.

Thank you.

When you are on:

https://elsa-workflows.github.io/elsa-core/

Go to the lower left corner menu under docs. None of the links are working and resulting in a 404

URLs behind the menu links:

Getting started:
https://elsa-workflows.github.io/elsa-core/docs/installing-elsa-core

Concepts:
https://elsa-workflows.github.io/elsa-core/docs/concepts-workflows

Guides:
https://elsa-workflows.github.io/elsa-core/docs/concepts-workflows

The links seems to be missing /installation/ path after the /docs.

Example of working link:
https://elsa-workflows.github.io/elsa-core/docs/installation/installing-elsa-core

also give proper syntax for OutPut

One of two "elephant in the room" issues relating to docs. This one deals with docs that users will want to read, wheras #17 deals with docs for developers. Users will need some documentation for Elsa 2.0. We are going to need to decide how much we are planning on preparing, and start scheduling the work to write it.

It might be best to treat this particular issue as a spike, with the intended outcome of analysis & agreement. That way this issue doesn't inflate like a balloon and become a never-ending "Do all the work!" issue. In that case, the outcome of this will be to create a series of follow-up issues to write specific, agreed-upon pieces of documentation.

Here are some ideas of docs which users might want to read. We could use this as a starting-point for discussion, and it's almost certainly not complete:

• Conceptual overviews
• Introduction to each pre-created activity
  • What does it do?
  • What are its configuration parameters?
  • Does it expect any specific inputs?
  • What are its outputs?
• How-to guides for the Dashboard & Designer UIs

Acceptance criteria

Presuming we treat this issue as a spike, then the team should have worked-up and agreed upon a list of user documentation topics which we plan to provide for Elsa 2.0.
In that case, further issues should be created and scheduled so that each of those may be worked-upon.

I would like to try to translate it into Chinese.

The following pages are still under construction. I think it would be helpful if they are complete.

Raised the same issue here as well.

1. Master Child Workflows
2. Composite Activities
3. Runtime List Values
4. Json Workflows
5. Custom Activity Providers
6. Customize Existing Activities
7. Property Editor types
8. Correlation
9. Workflow Recovery

One of two "elephant in the room" issues relating to docs. This one deals with docs that developers will want to read, wheras elsa-workflows/elsa-core#701 deals with docs for users. Developers will need some documentation for Elsa 2.0. We are going to need to decide how much we are planning on preparing, and start scheduling the work to write it.

It might be best to treat this particular issue as a spike, with the intended outcome of analysis & agreement. That way this issue doesn't inflate like a balloon and become a never-ending "Do all the work!" issue. In that case, the outcome of this will be to create a series of follow-up issues to write specific, agreed-upon pieces of documentation.

Here are some ideas of docs which developers might want to read. We could use this as a starting-point for discussion, and it's almost certainly not complete:

• Installation & set-up
  • How to use each of the persistence back-ends
  • How to install & integrate with some of the other elective techs (Hangfire, Quartz etc)
  • This probably doesn't need full docs, because we can refer to docs for those techs
  • Setting up the dashboard/designer
• Conceptual overviews
• Integration with other technologies
  • ASP.NET Core
  • Dependency Injection
  • Logging
  • Again, not all of these need full docs, because we just need to point out that we use XYZ known mechanism
• Extending Elsa: Creating your own activity classes
• Minimum requirements
  • Compatible runtimes
  • Browser compatibility for the dashboard/designer
  • Compatible persistence back-ends
• API docs
  • Specific service interfaces which devs should know about to perform common tasks
  • Like some of the stores, to get workflow instances and definitions
  • Triggers & signals
• What's available?
  • A list of the elective NuGet packages
  • An overview of what each one provides

Acceptance criteria

Presuming we treat this issue as a spike, then the team should have worked-up and agreed upon a list of developer documentation topics which we plan to provide for Elsa 2.0.
In that case, further issues should be created and scheduled so that each of those may be worked-upon.

As per the guides Signal received activity - Scope selected -> Instance
but in ver 2.6.0 Signal received activity the Scope Dropdown is missing.
the example in the guide does not work, is it due to the missing Instance selector

The fact that the documentation doesn't have a search box takes up too much expensive work time.

Is there going to be a separate branch for Elsa 2.0 documentation?

Not able to comprehend a use case for User Task.

Understood that its a blocking activity. But how to use it?

Need a guide and working example.

Also is the IContentSerializer used any where there?

Hello Elsa,

As I am going to explore ELSA, but documentation part is not complete on this https://elsa-workflows.github.io/ and
current running version of Elsa 2.8 and documents are on 2.2

Kindly update the document as well, so it could be easy to understand

This is a follow-up issue raised due to some confusion about when Workflow instances should persist and when they should not.

The information is in this issue comment but could be reworded and should be added to some documentation.

Note that after that discovery was made, the default persistence behaviour was changed to WorkflowBurst (previously it had been Suspend). This means that more workflow instances will persist than before.