Sidramappa,
Launch and Attach are actions that can be built into a Visual Business Object (VBO). VBOs are built in order to interact with another software application. Very simply, Launch actions will start the application (usually from a file path to the application, or a URL to a web application). Attach actions are built to make sure that the application the Digital Worker thinks it is interacting with is actually correct. In Blue Prism processes, a Digital Worker often bounces from one application to another and back again. Including an Attach action in your VBO will prevent the Digital Worker from "losing sight" of an application as it does this jumping around.
Here is an example of a Launch action. All it does is launch the application from a file path that was configured in Application Modeller:
Next, an Attach action is needed so that the Blue Prism Digital Worker can identify and connect to the correct application it should be interacting with. In order to ensure the Digital Worker doesn't "forget" which application it should be interacting with, an Attach action should be built into the VBO like so:
The Attach action lives in the other actions you build into your VBO. For example, the Log In action (screenshot below) calls the Attach action page first to make sure it's connected to the right application before proceeding with the log in steps. In general, it is best practice to always call the Attach before carrying out any work in the rest of the action. The only action that doesn't need to call the Attach action first would be the Launch, because there is nothing to attach to prior to the launch.
Cheers
------------------------------
Charles Kovacs
Developer Consultant
Blue Prism
America/Chicago
------------------------------
Launch and Attach are actions that can be built into a Visual Business Object (VBO). VBOs are built in order to interact with another software application. Very simply, Launch actions will start the application (usually from a file path to the application, or a URL to a web application). Attach actions are built to make sure that the application the Digital Worker thinks it is interacting with is actually correct. In Blue Prism processes, a Digital Worker often bounces from one application to another and back again. Including an Attach action in your VBO will prevent the Digital Worker from "losing sight" of an application as it does this jumping around.
Here is an example of a Launch action. All it does is launch the application from a file path that was configured in Application Modeller:
Next, an Attach action is needed so that the Blue Prism Digital Worker can identify and connect to the correct application it should be interacting with. In order to ensure the Digital Worker doesn't "forget" which application it should be interacting with, an Attach action should be built into the VBO like so:
The Attach action lives in the other actions you build into your VBO. For example, the Log In action (screenshot below) calls the Attach action page first to make sure it's connected to the right application before proceeding with the log in steps. In general, it is best practice to always call the Attach before carrying out any work in the rest of the action. The only action that doesn't need to call the Attach action first would be the Launch, because there is nothing to attach to prior to the launch.
Cheers
------------------------------
Charles Kovacs
Developer Consultant
Blue Prism
America/Chicago
------------------------------
