ENV Variables for end users

(Tatiana Perry) #1

I noticed that my variables don’t save from endpoint to endpoint. Is there a way to have it so that once they input the credentials once, it’s populated until they change them or clear the cache?

It would be really helpful for the testing credentials.

I didn’t see anything in the docs, unless I missed it.
09%20PM

(Taylor Barnett) #2

What browser are you using? I believe they should be carrying over.

(Tatiana Perry) #3

I am using Chrome. Version 73.0.3683.103 (Official Build) (64-bit)

(Taylor Barnett) #4

Could you link me to somewhere in your docs it is doing it? I tested it on another area of your docs and saw it carrying over from endpoint to endpoint.

Do you have any cookies settings changed where it might be able to go from one page to another?

(Tatiana Perry) #5

After testing on a few different machines, its the path params that are mostly touch and go. Which they are technically not an env token.

Are those supposed to carry over as well?

(Taylor Barnett) #6

Could you try to make them env variables by setting their default value to {$$.env.pathParamName}?