Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Use case: using a StartMyDay service in an automation

Updated on November 10, 2021

The Start My Day feature of Pega Robot Studio has several methods and events you can use to launch the applications and processes you use to begin your workday.

This innovation lets you specify activities a Robot Runtime or Agile Desktop user is presented with when he or she first starts Runtime/Agile Desktop. This list can include non‐Pega programs and URLs, as well as Pega Robot Studio solutions. Users can use the Manage Applications dialog to prioritize the order in which applications are launched to maximize their readiness.

In addition, each Runtime/Agile Desktop user can add to and remove from the list of processes to be started by Runtime/Agile Desktop. The items on the list are specific to the user.

To enable an application to be used for StartMyDay, first add the application.

  1. From the Project Explorer, select Add > Application.

    Add application

  2. Set the application name to use in the automation, and set the Path to the executable for the app.

    Application name and path

  3. Click Add.Result: The application opens.
  4. In the Properties Grid to the right, scroll down to the StartMyDay properties.
  5. Select StartMyDay as the StartMethod and Automatic as the StartMyDay property.

    StartMyDay property

  6. In the Toolbox to the left, open the Accelerators folder and then the StartMyDay folder.

    StaryMyDay Accelerators

  7. Start by dragging a StartMyDay method to the Automation Surface.

    StartMyDay method

  8. Next, drag an AddExeApplication to the Automation Surface.
    We already added one application, when we started our project. We can add another using a StartMyDay method. For this use case, you can use any executable that you have installed and know the path for. We're just going to launch the apps, and not perform any tasks in them.
  9. Define the friendlyName of the app and its path.


    Now let's pause and link up these automation blocks, to establish a workflow.
  10. In the StartMyDay automation block, click the small orange circle to the right of the StartMyDay text and drag the arrow to the right, to the orange circle to the left of the AddExeApplication block.

    Workflow link

    Now that we've added these apps, let's start them up.
  11. Click and drag a StartApplications method to the right of the existing workflow.
  12. Click on the first FriendlyName field and enter the name of the Windows app you added in the first AddExeApplication block (Notepad in our example.)
  13. Click on the second FriendlyName field in the StartApplications block and add the FriendlyName you gave to this second app.
  14. Create the workflow link leading to this automation block.
    The workflow should now look like this:

    Updated workflow

    Since we're launching two apps in our StartMyDay automation, we need to make sure we can see both. StartMyDay lets you define exactly where apps will display on the desktop.
  15. Click and drag the SetApplicationPositionAndSize method; place it underneath the current workflow, at the left side of the screen.
  16. Set the values for each position field as follows.

    Position1st App Values2nd App Values
    These position values will place the first app (Notepad) to the left of the desktop, and the second app (BankerInsight) to the right of the first app. Both apps will be the same height and width.
    Position diagram
  17. Now connect the workflow arrow to the position and size block you just created.Result: Your automation workflow should look similar to the following:
  18. Select the Test button.Result: The automation runs, opening the two applications and placing them side by side.

    Successful StartMyDay

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us