Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] Stored Response Status Code as Individual Variable. #5823

Open
RunnenLate opened this issue Jun 22, 2023 · 1 comment · May be fixed by #6170
Open

[IDEA] Stored Response Status Code as Individual Variable. #5823

RunnenLate opened this issue Jun 22, 2023 · 1 comment · May be fixed by #6170
Labels
enhancement New feature or request Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10857 triaged

Comments

@RunnenLate
Copy link

Is your feature request related to a problem? Please describe.
Would it be possible to add a Response Map variable to store just the status code
EXAMPLE: '200', '500', '401'
This value is used a log in the response logic to determine what the next action is to be taken in the channels workflow.

Describe your use case
I need this feature so I can accomplish .

Describe the solution you'd like
Seems like the following code could be added to the HttpDispatcher code here

connectorMessage.getConnectorMap().put("responseStatusCode", statusCode.toString());

connectorMessage.getConnectorMap().put("responseHeaders", new MessageHeaders(new CaseInsensitiveMap(headers)));

Describe alternatives you've considered
The current method requires parsing it out from the $('responseStatusLine') like so $('responseStatusLine').toString().substring(9, 12)

@RunnenLate RunnenLate added the enhancement New feature or request label Jun 22, 2023
rogin added a commit to rogin/connect that referenced this issue Jun 22, 2023
@pladesma pladesma changed the title [IDEA] Stored Response Status Code as Indavidual Variable. [IDEA] Stored Response Status Code as Individual Variable. Jun 28, 2023
@lmillergithub lmillergithub added triaged Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10857 labels Jun 28, 2023
@rogin
Copy link

rogin commented Apr 17, 2024

PR created this morning.

@rogin rogin linked a pull request Apr 17, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Internal-Issue-Created An issue has been created in NextGen's internal issue tracker RS-10857 triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants