Storage Get One Time URL

This task block is used in situations where you need to allow an unsecured person to set a value of a storage item. This block creates a one time use secured URL that can be used in something like a Robodoc to set a value of a storage item.
An example use case could be an email approval chain system where each time a user approves something, they can press on a button in an email and it will set a value in the storage item, which then could trigger your mission to do something else. When the user navigates to the provided URL, they will be presented with a dialog that will validate their change and will also provide a button to redirect them if needed.

You can also use Storage Items Keys to accomplish this feature, however storage item keys are not one time use access, but rather time based expirations. Storage item keys also do not provide a validation dialog screen and are mainly meant for cURL commands. Read more about how to create storage item access key here Storage Item Access Keys

This task block consists of an input and a done output.

If the input to the block is triggered the block will create a storage write URL. The URL does not contain the the "&content" portion of the URL. That is what you will need to add to the RoboDoc to tell the URL what to set the value of the Storage Item to. For example, this is an example of a RoboDoc that has a link that will set the value of a storage item to 1.

<a href="{$var1}&content=1" >APPROVE</a>

The variable var1 is what would be in the "Put URL in variable" section.

Examples

Here is a simple example of a mission that creates a one time url and places it into the variable var1. Then the email block places the url into the body of the email using {$var1}

Copy / Settings / Docs

Each task block has three buttons named Copy, Settings, and Help.

• Copy: This will duplicate the task block with all the current settings.
• Settings: Settings will show a dialog that allows some added configuration for the block
  • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
  • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
  • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.