.NET proxy
A .NET proxy is an interface that lets you connect to a web service with code in .NET format. The .NET proxy can return a requested resource from its cache, or forward the request to a server that has the resource.
Integrations and Connectors
AgilePoint NX integrates in these ways with .NET proxy:
- Activities in Process Builder
- Access tokens
Activities in Process Builder
You can use out-of-the-box activities for .NET proxy to execute actions in process-based apps.
An activity is a functional unit, or task, in a process-based app. Activities that integrate with a third-party system provide access to the API functionality for that system in a simple, point-and-click, form-entry format. This means that you can easily leverage APIs without writing code.
The following activities are available.
- .NET Proxy
For more information, refer to .NET Proxy activity in Process Builder:
Access Tokens
You can create access tokens for .NET proxy.
An access token is a secure object that stores an endpoint (usually a URL) and authentication credentials to connect to a service or technology. Often this is an external or third-party service, like Salesforce or SharePoint, but access tokens can also connect to an AgilePoint NX enviornment, local database, or other types of technologies. Once an access token is created, application designers can simply select and reuse it, rather than entering the credentials each time they are needed.
For more information, refer to Access Token for .Net proxy.
Related Topics
Examples
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
About This Page
This page is a navigational feature that can help you find the most important information about this topic from one location. It centralizes access to information about the concept that may be found in different parts of the documentation, provides any videos that may be available for this topic, and facilitates search using synonyms or related terms. Use the links on this page to find the information that is the most relevant to your needs.
Keywords
.NET proxy, proxy, proxies, DOT NET proxy, .NET, dot net