Skip to main content
pearlf4501
pearlf4501
November 13, 2024
Question

How to use Integration & WebAPI with a!urlForRecord() for Portals?

  • November 13, 2024
  • 6 replies
  • 0 views

I could not find any Appian documentation that describes how to add dynamic variables to Integrations/Web APIs for use with a!urlForRecord() and I was wondering if anyone had any guides or advice I would greatly appreciate it!

6 replies

stefanhelzle0001
stefanhelzle0001
November 13, 2024

I am not sure I understand what you are looking for. Integrations are used to call other systems from Appian. Web APIs are used to receive calls from other systems to Appian. And then there is urlForRecord() ....

This does not fit together in my head.

pearlf4501
pearlf4501Author
November 13, 2024

The recommendation for using partially Portal compatible functions (e.g. urlForRecord()) is to use a Web API and Integration as outlined in greater detail here: https://docs.appian.com/suite/help/24.3/portals-design.html#using-partially-compatible-functions-and-objects-in-a-portal
Essentially my question is how to pass in the Record Identifier to the Web API where urlForRecord() is called?

stefanhelzle0001
stefanhelzle0001
November 13, 2024

Got it. Let me first ask a question. What are you doing with that URL? I mean, portals are meant to serve anonymous users. This unknown user will not be able to access that record URL.

somasundaram.d
somasundaram.d
November 14, 2024

Since portal is intended for public users, there are some functions which cannot be used as it may require some user context. So, we try to achieve it using a service account which is an Appian account primarily used together with API key.

You can create a Web API that gets the record identifier from the query parameter of the HTTP request and construct the record url of the record. Then you can pass the url as an HTTP response.

Also, create an integration that gets the record id as rule input, call the Web API created above and pass the rule input as query parameter. The identifier will be passed to web API as part of HTTP request.

You can then use the result of Integration in your portal objects.

    Terms & ConditionsAccessibility statement