elsa-workflows / elsa-workflows/elsa-core

Only done outcome in Studio if subclassing FlowSendHttpRequest

Open
#7,407 0 comments 0 reactions 0 assignees View on GitHub
triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

## Description
If I create a subclass of FlowSendHttpRequest (like MyFlowSendHttpRequest) then the only outcome shown in Studio is "Done". No outcome/port for expected status code, tiomeout etc as with the original FlowSendHttpRequest. Not even if you duplicate the entire class.

## Steps to Reproduce
Create a subclass of FlowSendHttpRequest activity (inherit from FlowSendHttpRequest). Run Studio and add the custom activity to workflow. Only Done outcome.

## Expected Behavior
Should have same outcomes / portsvisible as FlowSendHttpRequest

## Actual Behavior
Only "Done" outcome.

## Environment
- **Elsa Package Version**: Elsa 3.5.3
- **Operating System**: Windows 10

## Troubleshooting Attempts
- Using FlowNodeAttribute. Seems to work but then you have no dynmaic outcome depending on status code.
- Tried to duplicate everythign in FlowSendHttpRequest (and inherit from base class just like FlowSendHttpRequest). Same.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.