GetCredential

All the credential details of the users for an application is stored in the credential vault in manager. This activity is used to obtain the credentials which is uploaded to the credential vault. It is also useful to activate/login to applications involved in this process.

Credential vault key

After adding the credential details on the “RobilityManager” for the application, the vault key for the respective project will be configured. (Click here to get detailed information on how to create credentials for the application).
Follow the below steps to find the vault key in the Designer.
Before moving to the Designer, refer the steps to create the credentials for the project.

1. Launch the Designer and create a solution named as “CredentialManagement”.
a. To access the “Vault Key,” select the corresponding project from the “Publish” section located at the bottom of the Designer. This selection should align with the project for which the credential vault has been configured. The default setting for the publish option is “This PC”.
b. Upon selecting the project, the vault key will be integrated into the solution explorer, appearing as the “Credential key” within the “Resource” category.
2. The presence of the “Credential key” within the “Designer” interface is contingent upon the configuration of the “Credential Manager” for the specific project. It will only be visible when the project aligns with this credential management configuration.
3. Click on the “Solution explorer” to view the “Credential key” in the resource. 

Properties

INPUT

ApplicationName:*  The Application name list will be auto-filled once the “Vault key” has been configured. Choose the “Application name” from the drop-down to extract the credentials from.  

Lock: This property indicates whether the “Application” should be locked during the execution. Specify “True” or “False” to enable or disable the lock status during the extraction of credentials.
True: Enables to lock the “Application” during the execution of the bot.
False: Disables to lock the “Application” during the execution of the bot.
None: If this option is left blank, the property will not take effect, and by default, the application will be in unlocked status.

TenantName:* This field will be automatically filled once the vault key is configured against the solution. It displays the “Tenant” name which the solution has been configured.

MISC

DisplayName: Displays the name of the activity. You can also customize the activity name to help in troubleshooting.

SkipOnError: It specifies whether to continue executing the workflow even if it throws an error. This supports only Boolean value “True or False”. By default, it is set to “False.”
True: Continues the workflow to the next step
False: The workflow aborts if it throws any error.
None: If the option is specified as blank, by default the activity will perform as “False” action.
Version: It specifies the version of the Robility Manager feature in use.

OUTPUT

ApplicationDetail: This facilitates the extraction and viewing of the activity’s output in a “String” datatype, representing “Application details” extracted from the “Credential Vault.”(Refer the tips below to get detailed information)

ApplicationTittle: It helps to extract and view the activity’s output in a “String” datatype, representing the “Title” provided in the “Credential vault” against the “Application”.

Domain: This facilitates the extraction and viewing of the activity’s output in a “String” datatype, representing “Domain Name” if provided while adding the “Credentials” for the “Application” (Refer the steps in creating the “Credentials).

FieldID: This facilitates the extraction and viewing of the activity’s output in a “String” datatype, representing “Field ID” if provided while adding the “Credentials” for the “Application”. (Refer the steps in creating the “Credentials).

Password: This facilitates the extraction and viewing of the activity’s output in a “Secure String” datatype, representing “Password” provided in the “Credential vault” against the “Application”.

Result: It helps to view the execution state of the activity. It returns the values in Boolean format.
False: It indicates that the activity has been faulted due to some unexceptional error thrown.
True: It indicates the activity has been executed successfully without any error.

Username: This facilitates the extraction and viewing of the activity’s output in a “String” datatype, representing “Username” provided in the “Credential vault” against the “Application”.

* Represents mandatory fields to execute the workflow. 

Create variables option

The “Create Variables” option in the “GetCredentials” activity is utilized to create variables against output properties such as “Application details, Application title, Domain, Password and Username”. This allows users to store credentials securely with the help of encryption. The variables created can be accessed in other activities using the output properties as input. This saves time and effort which would otherwise be spent creating and storing variables. 

Reset/Refresh credentials

When credentials are updated in the “Credential Vault,” the refreshed information can be seamlessly integrated into the workflow, enhancing the accuracy and security of each execution. This dynamic updating can be functioned through the “Refresh” button to help in maintaining the reliability of your processes.

Moreover, in cases where an “Application” is removed from the “Credential Vault,” the associated activity within the workflow can be promptly reset through the utilization of the “Refresh” option.