Best practice and issues with moving to different environment

[ShobhitMalaviya]

Hi,

I am working on an automation wherein I am automating a process that has the following steps.

1. Looks for data file on a shared folder.
2. Runs SQL Query:
    Run on the data file in step1 . Database gets updated with new data
3. Open PowerBI server :
    There is a dashboard already present on the server that is connected to a SQL Database
4. Click the refresh button to refresh the power BI dashboard:
    The dashboard is already published on the server with a connection to the SQL Database
5. Send email with link (URL) to refreshed dashboard.

I need help with two things here.

1. Moving the code from one environment to another: To explain this I will take an example.

For example: On the development environment I have a BOT assigned say BOT123@xyz.com. On the development environment what happens is when I open the PowerBI server it automatically opens the server space, that has the dashboard, for BOT123 without asking for any credentials. My question is when the process is in production and the controller is running the process from the control room he needs to make sure that on whichever computer the process is run that computer should have the windows account for BOT123. If this is not the case say for example the controller runs the process on a computer with windows account for BOT456, then when the process runs and opens the PowerBI server the server space for BOT456 is opened. Since the dashboard was present in the server space for BOT123 and not BOT456 the process will throw an exception.

Please let me know the best approach for this.

2. Run schedule: Below points explain the run schedule for this process.

a. Process is scheduled to run once a month i.e. 14th every month.
b. If the bot is unable to find the input file on the 14th then it should shoot an email "Input file missing" and again check for the file on the 15th.
c. If the bot finds the file on the 14th itself it should run process and not look for the file again on the 15th.

My question is do we need to include a logic for this in the process or is this something that the controller will take care of.

It would be very helpful if someone can help with the above mentioned points

------------------------------
Shobhit Malaviya
------------------------------

[MadhurChopra]

Hey Shobhit,

Please see my response below:

1. Moving the code from one environment to another...Please let me know the best approach for this. 
As I had previously indicated in your last thread (https://community.blueprism.com/communities/community-home/digestviewer/viewthread?MessageKey=a7315220-8639-45bf-a823-9ba719f2eb86&CommunityKey=3743dbaa-6766-4a4d-b7ed-9a98b6b1dd01&tab=digestviewer#bm...), the best approach will be to share the dashboard with any user (digital worker) account that requires access to it. If this approach is not feasible in your case, then you should be looking to address the Single Sign-on settings in Power BI for the accounts in question so as to force a login screen to appear.

2. Run schedule: Below points explain the run schedule for this process. My question is do we need to include a logic for this in the process or is this something that the controller will take care of.

This should be handled by the digital worker and not a Controller. The controller's role is to ensure smooth process run operations. One way to achieve the above functionality within your automation could be to archive the file once it has been processed. The Digital Worker will then be scheduled to run on both 14th and 15th. If the file is found on 14th, it will be processed and thereafter archived. On the 15th, check in the archive folder to see if the file exists; if it does do nothing, else proceed with processing the file.

I hope this helps.

Regards.

------------------------------
Madhur Chopra
Sr. Product Consultant
Blue Prism - Professional Services
America/Los_Angeles
------------------------------