Good Day Mayank,
Regarding Date for Blue Prism we have to remember that best practices is to have the entire environment on the same time zone. The interactive client should be on the same time zone as the application servers, as the runtime resources, and as the database to prevent issues like this occurring. This way your PST or EST users logging into your IST environment will not experience any difference. Reporting for a given environment should be done at the process or UI level by converting it to the target timezone and updating the related information from a display standpoint.
That being said lets address what would happen with the proposed scenarios.
- Process/Object saved log - This would be written from the machine that the work is saved on, potentially losing the timezone it was recorded in as a Datetime value derived from .Net
- Control Room Work Queues - Dates associated with Work Queues Item records (e.g. created, started, deferred date) are stored as UTC, so it is UTC times that you will see in log files. When viewing work queues in the Control Room the times are converted from UTC to the local time of the user profile (Link to Knowledgebase Article)
- Session Manager: The local time will be passed in but it may not be converted to UTC, which can lead to inconsistent time being reported.
- Scheduler: You are correct this will be executed based on the local time of the Application Server.
For more information our KB article on How are dates and times stored in the Blue Prism database tables? may be of use.
I hope this helps and have a great day.
------------------------------
Charles Trott
Senior Product Consultant
Blue Prism
------------------------------