Documentation Improvement Request
Documentation Issue Overview
The section under Guides / HTTP Workflows / Designer has issues.
Proposed Documentation Changes
- This section is out of date:
regres.in now requires you make this call with an API key. Currently, the actual response is this:
{"error":"Missing API key.","how_to_get_one":"https://reqres.in/signup"}
Of course, this prevents the rest of the workflow from functioning.
Either (1) notes need to be added re: getting an API key, and the HttpRequest activity updating to show how that key should be sent with the request, or (2) another source of fake data should be found.
- The link in this section is incorrect:
I am using the ElsaServerAndStudio solution. Out-of-the-box, the Elsa Studio project fires up on https://localhost:64884; http://localhost:64885. The Elsa Server project fires up on https://localhost:64882; http://localhost64883 ... but has a "BaseUrl" of https://localhost:5001.
None of these appear to match the http://localhost:13000 shown in the documentation.
(As a new user, I actually haven't been able to get ANY of these to work, and am facing the dreaded "localhost refused to connect error. But I don't think that's documentation related.)
Affected Sections
The page for Guides / HTTP Workflows / Designer
Impact of Changes
Fixing this will assist new users (like me) in getting started and will provide the new user with confidence that the application is up to date.
Documentation Improvement Request
Documentation Issue Overview
The section under Guides / HTTP Workflows / Designer has issues.
Proposed Documentation Changes
regres.in now requires you make this call with an API key. Currently, the actual response is this:
{"error":"Missing API key.","how_to_get_one":"https://reqres.in/signup"}
Of course, this prevents the rest of the workflow from functioning.
Either (1) notes need to be added re: getting an API key, and the HttpRequest activity updating to show how that key should be sent with the request, or (2) another source of fake data should be found.
I am using the ElsaServerAndStudio solution. Out-of-the-box, the Elsa Studio project fires up on https://localhost:64884; http://localhost:64885. The Elsa Server project fires up on https://localhost:64882; http://localhost64883 ... but has a "BaseUrl" of https://localhost:5001.
None of these appear to match the http://localhost:13000 shown in the documentation.
(As a new user, I actually haven't been able to get ANY of these to work, and am facing the dreaded "localhost refused to connect error. But I don't think that's documentation related.)
Affected Sections
The page for Guides / HTTP Workflows / Designer
Impact of Changes
Fixing this will assist new users (like me) in getting started and will provide the new user with confidence that the application is up to date.