Scheduling Productions - Conductor - Foundation 23.2 - Foundation 23.2 - Ready - Hyland RPA - external

Hyland RPA Conductor

Hyland RPA
Foundation 23.2
Due to maintenance windows, it may be useful for a robot not to perform tasks within a certain time interval.

Therefore, the robots must be automatically deactivated at a certain point in time and reactivated automatically later.

With the help of an SQL statement executed in the database, all robots can be deactivated:

"update Production set PROIsActive = 0 where PROIsActive = 1;"

And with the following statement all robots are reactivated:

"update Production set PROIsActive = 1 where PROisActive=0;"

The statements must later be executed at defined execution times. For instructions for MS SQL Server Standard or Enterprise Editions, see Create a Job on

If you use the Express Edition of the MS SQL Server, a workaround must be selected via the Windows Task Scheduler.

To do this, create two batch files (.bat) with the following content:

Batch file for deactivating your productions:

sqlcmd -S "%SQLServer%" -d "%DatabaseName%" -Q "update Production set PROIsActive = 0 where PROIsActive = 1".       

Batch file for reactivating your productions:

sqlcmd -S "%SQLServer%" -d "%DatabaseName%" -Q "update production set PROIsActive = 1 where PROIsActive = 0".

Afterward tasks must have to be created in the Task Scheduler with the defined execution times. There the specific file is then referred to. For instructions on how to create a task, see How to create an automated task using Task Scheduler on Windows 10 on