Skip to main content

Using Integrations in UiPath Studio

Identify Required Activity Packages:

Identify the activity packages needed for integration tasks (e.g., Microsoft Office 365, Salesforce, servicenow, Slack).

Install Activity Packages:

Ensure you have the latest activity packages installed in UiPath Studio to leverage the most up-to-date features and integrations available.
Enable "Use Integration Service " Option:

After adding a connector to the workflow, checkmark the "Use Connection" box from the properties panel. This will automatically establish the default connection.

Access integration Activities:

Go to the "Integrations" section in UiPath Studio and select the relevant category (e.g., "Microsoft office 365 Activities") for your integration needs.

Define Input Arguments:

Define the necessary input arguments (e.g., UiPath Event, Event connector, Event Object id, Event Object type) to receive information from the Integration Service.

Utilize Switch Activity:

Implement the Switch activity in your workflow to route the process flow based on the triggering connector (e.g., OneDrive, Salesforce, ServiceNow).

Set Up Switch Cases:

Set up individual cases in the Switch activity for each connector to execute specific actions based on the triggering connector.

Use Connector-Specific Activities:

Inside each Switch case, employ activities specific to the triggering connector (e.g., Office 365 activities for OneDrive, Salesforce activities for Salesforce).

Handle Errors and Notifications:

Include error handling mechanisms to identify issues during the process and take corrective actions, such as logging warning messages or creating incidents in ServiceNow.
Send Stakeholder Notifications:
Use appropriate notification activities (e.g., Slack's "Send Message" activity) to keep stakeholders informed about progress or exceptional scenarios.

Save and Publish:

After successfully implementing the integration and completing the process, save and publish the automation project in UiPath Studio.

Publish the process.

  • Once the automation project in Studio is completed, you need to publish it to the Orchestrator instance on the same tenant where the Integration Service is enabled and the trigger will be used.
  • The publishing process remains the same as usual, where you can publish the automation project either to a specific folder or to your personal workspace within the Orchestrator. This allows the Integration Service to access and utilize the published project to respond to the specified triggers and events.

 Read Complete Series on UiPath Integration Service:
1. Introducing UiPath Integration Service
2. Using Integrations in UiPath Studio
3. Configuring Triggers in UiPath
4. Overview of UiPath Connector Builder

Source: UiPath Academy

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...