Regarding Bot modification

yah of course we can
–enable simulate click and simulate type in the property panel type into and click activity so that it can run in background as well, if any such activity is used
–other than that if any input dialog box is used remove them and pass that value as input along the process itself or from orchestrator as a asset so that it wont ask for user input while running
–once after this run the process and check whether it is working even when from background
–and if that works then in orchestrator create a robot with unattended bot type or if it already exists change the robot type
–and to create a robot and machine kindly have a view on this thread
Kindly check with these stuffs that would surely resolve your issue
— first create a machine in orchestrator and that machine name should be same as in your system
To get that name go to start-> search as robot-> settings and get the machine name from there and paste the same while creating machine in orchestrator and copy the machine key after this from orchestrator and paste it in your system robot tray and mention the orchestrator url as well
— the. Make sure that we have a robot created in the orchestra with the same machine name and while entering the detail for username and password go to cmd window and type as whoami which will give use domain and username, enter the same in the orchestrator while creating robot
— create a environment now In the robot tab and tag the robot created in the previous step to this environment
— now back to our system in robot tray we have machine key, and orchestrator url mentioned readily and now we can connect

and ensure that while entering the Orchestrator URL in robot tray…
follow the steps in these thread

kindly try this and let know for any queries or clarification

hope this would help you
Cheers @SauravYadav