The Adobe Sign activities use an (Client ID) and (Client Secret) as well as an (Base URL) to establish an OAuth connection between UiPath and your Adobe Sign application. This connection authorizes a Robot to call the Adobe Sign APIs and access resources on your behalf.
After establishing a connection, a parent Adobe Sign Scope activity can output a record of the connection in a
Connection object (Connection) that you can use in subsequent child scope activities.
The following steps are an example of how the activity works from design time (i.e., the activity dependencies and input/output properties) to run time.
- Complete the Setup steps.
- Add the Adobe Sign Scope activity to your project.
- Choose the (Authentication Type) you want to use.
- Enter values for the properties located in the body of the activity.
- Create and enter a
Connectionvariable for Output property. You can use this variable in subsequent uses of the Adobe Sign Scope activity.
- Authentication Type - The type of authentication to use. You can use one of the following three options: Existing Connection, OAuth Passthrough, OAuth Authorization Code
- ExistingConnection - Uses a connection from the parent application scope instead of a new connection. This field supports only
Connectionvariable must be from a previously run AdobeSign Scope activity (parent) that still has an active connection.
- Base Url - The base URL for the connection. This field supports only
- Client Id - The client identifier issues to the client. This field supports only
- Client Secret - The client secret issues to the client. This field supports only
- DisplayName - The display name of the activity. This field supports only
- Environment Type - The environment type you are authenticating against. You can select one of the following options: Development or Production.
- ReportApiErrorAsException - When selected, API error responses are reported in BusinessActivityExecutionException by all child activities that use this application scope. When cleared, the child activity populates the API error message in the ResponseStatus output property and workflow execution continues. Check the ResponseStatus property to confirm successful execution.
- Connection - The connection which can be passed to a child application scope. This field supports only
Updated 2 months ago