Woah you guys are quick! It was my fault obviously. A preceding request was failing and apperantly you cannot extract data that isnât there.
So, a few things that Iâd liked to have for debugging purpose:
maybe a small lable with the latest http status code in the âsend requestâ box, and/or a button to view the return button (this is possible already by either using the console, or the terminal, where both can become cluttered really quick)
Buttons for âRun this box againâ, âStart Flow from this boxâ , âRun until hereâ
Decoupling of âcreated variablesâ and variables used in a request, so they dont necessarily match. âSend requestâ could have a mappingconfiguration of incomming variables to variables used in the request
In general I appreciate the feature, this feedback blog and the super friendly and helpful team and the quick reaction to feedback! This feels great!
changing the environment variables via flows is NOT possible. I tested this with a really simple flow, which just executes a request to google.com and does this in the prerequest script:
pm.environment.set(âtestâ, âabcâ);
After executing the flow and checking the environment, it is still empty
Currently, variables created using the âCreate Variablesâ block are set in the âdataâ scope. They do not edit/override/create environment variables.
inside a prerequest script and this is not done in a flow. I would expect to run the flow and then when i look in my environment to see âtestâ = âabcâ, but its empty. Iam not creating any variables via my request node
I have answered in the issue. Iam also copying my response here:
This is sad to read, as i have a usecase where we setup different environments for different users. I would argue that this is a decision which should be on the user. there is no reason to protect the users from themselves
Hi @askmeagain , you are absolutely right, could not agree with you more. This is not a permanent decision, just a temporary one while we figure-out the logistics of environment with flows.
We also want to letâs uses define and use multiple environments with flows so that they are not limited to defining a single environment for the entire flow. It is also possible to use one flow inside another flow in the future, which again brings in the question which environment should be used.
We also are exploring providing a storage block which will be capable of storing any kind of data, and not limited by the key value pair format the environments allow. We wish environments to be truly Environment variable - Wikipedia where we are also able to load Environments from your native OS when we enable running flows in CI environments.
There are a lot of decision that we have not taken yet, so it was safest for us to make the current environment readonly We promise to figure this out soon. Thanks again for the feedback
We are seeing the massive interest in Flow and this topic was turning out to be contain lot of information that everyone in the community to take value from. But the single threaded mode of discourse is turning out to be to confusing.
For a better experience for feedback, we have decided to move to using Github discussion for the same Discussions ¡ postmanlabs/postman-flows (github.com)
Hope to you see you all there. We will also be posting regular release notes and making major announcement there.
Iâm trying to run the request and passing it to another request, but before that I want to add or actually modify the value of one of the header parameters. For example, my first request header continued access token (which is not string) and I want to add text (String) in this access token before I pass it to the next request. There is any way to apply this?
Currently, you cannot append custom values to input. Weâll definitely work on implementing it. Meanwhile, would you mind raising an issue or an idea here Discussions ¡ postmanlabs/postman-flows ¡ GitHub
We promise to figure this out soon. Thanks again for the feedback
.
