The Hyland Login Service is an optional module of Hyland RPA, adding additional comfort and security while executing RPA processes unattended.
Without the Hyland Login Service, it is required to have the RPA client logged in all the time. The windows console session must be unlocked to have the Hyland RPA Conductor running and being able to execute tasks as soon as they exist in the database.
Having the Hyland Login Service installed, it is possible to have the RPA client logged out from the windows session while there is no task in processing. As soon as there is a task available for the client, the Hyland Login Service will log in into windows automatically and hands over the control to the Hyland RPA Conductor for task execution. Depending on the actual configuration, the Hyland RPA Conductor logs out again after the task, and the Hyland Login Service can scan for new pending or delayed tasks to start the cycle again.
The Hyland Login Service supports two common usage scenarios:
- In the "single-account mode" there is only one Windows account for a physical (or virtual) machine (called system). The Hyland Login Service (in cooperation with the Hyland RPA Conductor) will use this account only for task processing.
- In the "multi-account mode" there are multiple Windows accounts for a physical (or virtual) machine (called system). The Hyland Login Service (in cooperation with the Hyland RPA Conductor) will use different accounts for task processing. Which account is used depends on the actual configuration of the process and the privileges the account has. This mode supports stringent security policies you might have in your company. At the same time, the available resources of the system are used optimally.
You can choose the scenario on a system base. So, having a bot farm with both scenarios up and running is possible, but you cannot use both scenarios on the same system.