Looking for:
Liveperson agent console windows download |
Liveperson agent console windows download.Liveperson Agent Console - CNET Download
This page will introduce you to all available methods to configure your functions. Please also look at the allowlisting domains as this is required to access external resources. You can use environment variables to make your function more configurable without adjusting the code.
Access to the environment variables is possible at runtime using process. The LivePerson Functions platform does reserve a few environment variables for internal use. In case of a conflict, you will see the following message: Variable name is reserved and thereby blocked for use. You can create a new environment variable by pressing the "Set variable"-button within the side panel of the editor UI.
Once you click the button, a dialogue window will open and ask you to enter a variable name and its value. Changes made to the environment variable at runtime via process. They are not propagated to the UI or any other running instance. The modification of existing environment variables is possible via the side panel of the editor UI.
Select the environment variable you want to change by clicking its name on the list. Once you click on "Set", you will have to save the function to store the changes permanently.
Environment variables are static. Changing an environment variable via the UI will not automatically push this modification to any function in a productive state. Instead, you will need to redeploy the function to have the change take effect. Your configured environment variables are accessible via process.
You have both read and write access to the environment variables you configured. Be aware that environment variables are interpreted as strings within JavaScript by default. Hence if you want to use special types like JSON e. We discourage storing credentials that cannot be easily revoked, like passwords. If possible, we recommend using credentials for token-based authentication methods instead. We offer secure storage for storing sensitive data such as credentials and tokens.
Functions can read and write to this store at runtime. By default, your store will contain secrets created as part of the provisioning. Secrets can only be created through the web interface and not via CLI. To add a secret, you need to head to the "Settings"-Page with a user meeting the required permissions.
Then select the "Secret Storage"-Tab where you should see a list of existing secrets and a button "Add a secret". After clicking the button, you will be presented with a dialogue that allows you to select a name and provide the content of the secret. You can select the data type of the secret from the drop-down menu. This only modifies the validation and does not influence the access to the secrets later. You might notice that you cannot see the contents of the secret after the creation.
This is intended and related to security restrictions. Therefore, updating a secret is only possible by deleting and recreating the secret.
Secrets can be updated during the runtime by the function. The next chapter will explain the details of this process.
As mentioned above, we do not allow the modification of secrets from the UI. You may, however, change them at runtime. You can leverage the SecretClient , which is available in our Toolbelt for this task. Please notice the try - catch block in the code below. This highlights the importance of error handling, since accessing a secret can fail. Access to the secrets of the account is possible at runtime thanks to the SecretClient offered by our Toolbelt.
If you know that your secret will not be changing as it is static and not getting updated at runtime. You may load it once into memory and then store it. This example code shows a lazy initialization of a secret using a variable. The functions have access to a set of libraries, which we define in our functions template. You are not able to add your dependencies. Please see the following list of dependencies that are available to you. This website uses cookies to ensure you get the best browsing experience.
By continuing to use this website, you consent to our use of these cookies. This website contains proprietary content that belongs to LivePerson and that is intended for educational use by our customers and prospects. Your use of this site is subject to our Terms of Use , which include restrictions on any use of our information for unauthorized purposes. Sign in. Read time: 10 mins. Environment Variables You can use environment variables to make your function more configurable without adjusting the code.
Creating an Environment Variable You can create a new environment variable by pressing the "Set variable"-button within the side panel of the editor UI. Any environment variable will be checked against the following restrictions: Is it a reserved environment variable? Is the name exceeding characters? Is the value exceeding characters? Updating an Environment Variable Changes made to the environment variable at runtime via process.
Accessing Environment Variables Your configured environment variables are accessible via process. I agree.
Comments
Post a Comment