Blueprint Global Input, Type Hidden

Hi @ksaper@tsieda.com,

See this idea, it looks similar:

https://community.quali.com/idea/655/storing-reservation-specific-information-for-later.html

Yaniv

Yes it looks very similar to what Omri is asking for, I think I just proposed a specific way solve it based on the use case I have

Ok, we will keep this idea separate from the previous one

Thanks Kimo!

@ksaper@tsieda.com Do you see this data as something tied to a specific blueprint? will it have "default" for a blueprint? should it exist only in some blueprints but not others (even if it's hidden)?

@Alona.G I see it as something that only specific blueprints would need. In the example I I'm thinking of, I specifically would like to share information between the setup and teardown scripts. Something I do in the Setup script needs to be undone by the Teardown. This information isn't relevant to the user, it's noise to them, but vital to be passed along. I would see it as just a different type to existing blueprint level global inputs created today - so the Globals would be "Text, Number, List, Hidden*, Password*" where Hidden & Password are new (password request is in a different idea post, but you get the idea). When the Sandbox starts the Hidden variables wouldn't show to the user, but would be available to the Setup and Teardown script to read/write to (write to for setup).

Let's get both the Hidden and Password type fields added to the global inputs!!!!

This should be now marked as delivere