- Credential manager is a Windows concept.
You can find it on the Windows search quickly.
You will obtain/Add Credential there using the activity from the package
Regarding Credentials, You will use Get Credential activity to query asset from the Orchestrator, assuming that you Robot is connected to one.
As @KarthikByggari mentioned, you will there only be Storing the asset Credential Name and be using it as input of an invoke workflow of the file “GetAppCredentials.xaml”
This workflow will effectively be using both the previous concepts (Credential manager & Orchestrator asset).
- It will look first for the Credential according to the given name within the Orchestrator assets credentials.
- If asset is found, it will return you the Credentials values from the Orchestrator
- If an exception occurs (assets not found, Robot not connected to Orchestrator etc…) It would be looking inside the credential manager to find and return you the credentials valuse.
- If it does not find it, it will prompt you a dialog to enter the credentials values manually under the name the invoke workflow requested, so next time, it would not have to ask it again and would pull it from the from the Credential manager.
The advantage of this is that during development where maybe you will not have access to an Orchestrator in Orchestrator, you can input a temporary password, but one you will be moving to production, it could use the effective Crendential value stored in the Orchestrator.
All of this, without having to change anything in the workflow.
Hope that makes sense!