Cache Node

This node is part of the Aivo node category and allows temporary data to be stored in the cache, so that it can be retrieved later, at any point in the integration. That is, the stored data persists to a flow and remains available once the step close is reached.  

Additionally, it can be configured so that the stored values are specific to a session or shared by all sessions.  

 In the video we tell you the parameters to configure it:

Download the flow with the examples in this link.     

Below find the description of the fields that you will use in the process, as we show in the video    

1. Name: custom name given to the node and will be visible from the Studio workspace.   
2. Key (Required):name of the key that will be stored in the cache and then used to retrieve the saved value.   

   This field supports the {{varExample}} syntax, which is used to access properties of the MSG object, for example, msg.varExample.

3. Global: you will select false to indicate that the saved value is exclusively linked only to the specific session of a user and true if the value is required to be saved globally for all existing sessions in the instance.   
4. Method: lists the 4 methods used for cache operations GET/ SET/INCREMENT/ DELETE.  
   1. GET: used to access cached information. 

      If this value does not exist, “null” will be returned.  If the data to be retrieved was previously saved with the Global parameter selected: True: It will be available for all sessions, as if it was a public bot.  False: it will be available in the session where the cache was recorded, as if it was  a session-specific cache.

      1. Output: name of the variable where the value retrieved from the cache will be stored, it can be an existing or new variable.   
      2. Decrypt: decrypts cached data that has been previously encrypted.   
   2. SET: it is used to store information in cache, using a key, to retrieve it later. 
      1. Input: name of the message variable, string or JSON to store in the cache.
      2. Expires: indicates the amount of time in minutes that the data will be cached. By default, data is stored for 60 minutes. The time can be at least one minute and at most 1440 minutes, which is equivalent to one day.   
      3. Encrypt: encrypts the data that you want to cache. If we encrypt the stored data, we must activate decrypt to be able to read it. That is, if you save data and place encrypt, then to recover it you must do the reverse process. The difference is that internally the data is stored in the cache in an unreadable, encrypted form.   
   3. INCREMENT: it is applied as a counter, with each execution the value is increased by 1 (one), if the variable does not exist prior to the entry of the node, it will be initialized with the value 1. In this method, the Output is completed, as in GET. 
   4. DELETE: it is implemented to delete the stored key and value (previously saved with the cache node), from a key specified in the Key field.  

      When a cached data expires or is deleted, its value becomes null.  If the data was saved with the Global variable set to True, the node configured with the DELETE method must have the same property. The same concept applies to the case where the Global property was set to False when the data was saved.