Testing Embedded Interface

RE: Testing Embedded Interface

hemantha0001 — Tue, 21 Aug 2018 01:37:24 GMT

Were you able to resolve this issue?

RE: Testing Embedded Interface

komalc3 — Mon, 25 Jun 2018 08:39:16 GMT

Hi Shanmukha

In Appian CORS I have given the IP address.

Below are the issues observed in all the browsers:

1. IE Issue -

SCRIPT1028: Expected identifier, string or number

File: embeddedBootstrap.nocache.js, Line: 1, Column: 6595

2. Chrome Issue

embeddedAuthUtility-0d63ded74113090d0384.cache.js:55 GET exampledev.appiancloud.com/.../ping 401 ()
performInitialAuth @ embeddedAuthUtility-0d63ded74113090d0384.cache.js:55
authListener @ embeddedBootstrap.nocache.js:1
load (async)
registerComponents @ embeddedBootstrap.nocache.js:1
Test%20HTML.html:1 Failed to load exampledev.appiancloud.com/.../ping No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. The response had HTTP status code 401.
embeddedAuthUtility-0d63ded74113090d0384.cache.js:55 Failed to query server. Status Code: 0

3. Firefox issue

The character encoding of the HTML document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the page must be declared in the document or in the transfer protocol.
Test%20HTML.html
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at exampledev.appiancloud.com/.../ping. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Failed to query server. Status Code: 0

Any suggestions...

Thanx in advance!!

RE: Testing Embedded Interface

Shanmukha — Fri, 22 Jun 2018 12:04:53 GMT

Hi Komal,

What is the value that you have given in the Appian CORS is it ip address or the localhost? Did you test it the same in all browsers? and please let me know what you see in each browser so that we can corner the issue sometimes it may be problem with browser as well

Thanks

RE: Testing Embedded Interface

komalc3 — Fri, 22 Jun 2018 11:20:33 GMT

Hi Shanmukha

I am getting the below error now:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at exampledev.appiancloud.com/.../ping. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing)

Please suggest.

Thanx in advance!!

RE: Testing Embedded Interface

komalc3 — Tue, 19 Jun 2018 09:25:30 GMT

Thanx Shanmukha

Will try this out and let you know!!

RE: Testing Embedded Interface

Shanmukha — Tue, 19 Jun 2018 05:50:47 GMT

Hi Komal,

I thought I have replied you on your last comment. Could you please put this html in the java web application and run it from there and let me know what you see on the screen?

Thanks Raghavendra (Shanmukha) Reddy

RE: Testing Embedded Interface

komalc3 — Mon, 18 Jun 2018 09:03:33 GMT

Hi Shanmukha

I am creating a POC on Embedded interface referring to the docs:

https://docs.appian.com/suite/help/18.1/Embedded_Interfaces.html

My code is as follows:

<!DOCTYPE html>
<html>
  <head>
  <title>Test Page </title>
    <!-- This script loads the Appian Web components; change it to your Appian server's domain -->
    <script src="https://exampledev.appiancloud.com/suite/tempo/ui/sail-client/embeddedBootstrap.nocache.js" id="appianEmbedded"></script>
  </head>
  <body>
  <b> This is test page</b>
    <!-- This custom HTML element specifies an Appian report to embed on the HTML page -->
    <appian-report reportUrlStub="CZA3Iw"></appian-report>
  </body>
</html>

Here I just want to call a tempo report from my web page.

As per suggestions above, I have added the ip address of my machine in CORS. Also I have added myself in SAML group.

However, I am getting the error:

Failed to load resource: the server responded with a status of 401 ()

Test%20HTML.html:1 Failed to load exampledev.appiancloud.com/.../ping No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'null' is therefore not allowed access. The response had HTTP status code 401.

embeddedAuthUtility-ad522149e857770d25f3.cache.js:55 Failed to query server. Status Code: 0

request.onreadystatechange @ embeddedAuthUtility-ad522149e857770d25f3.cache.js:55

Any suggestions.

RE: Testing Embedded Interface

Shanmukha — Mon, 18 Jun 2018 07:00:11 GMT

Hi Komal,
Could you please elaborate what is your exact requirement and what have you done so far?

Thanks,
Raghavendra (Shanmukha) Reddy

RE: Testing Embedded Interface

komalc3 — Mon, 18 Jun 2018 06:39:46 GMT

Hi Shanmukha

I was trying to test a sample Embedded example and wanted to run the HTML code to check how it works? Basically need to demo the Embedded functionality before actually embed to our web application. Is there any way to do it?

I tried configuring my local IP Address / system IP address in COR but no luck. We are on cloud and trying to run the HTML page via browser within organization network.

Thanks

RE: Testing Embedded Interface

Shanmukha — Mon, 18 Jun 2018 06:22:06 GMT

Hi Mike,

It is better to write static page and hosted it in any server then it will pick up the localhost/IP then we can configure them in the cors in admin console so that way it will work. it is sometimes difficult to run the html in the browser where the IP will generated dynamically. We have done this type of functionality by hosting the static html page in the local Apache. either way it is only for testing then it is fine. For the bigger context we usually use embed in other web application like Java then it is better to host it in the server.

Thanks.

RE: Testing Embedded Interface

komalc3 — Mon, 18 Jun 2018 04:29:50 GMT

Hi mikec

I am also attempting the same thing.
Can you elaborate what do you mean by IP address that is generated when text editor is loaded.

RE: Testing Embedded Interface

mikec — Wed, 15 Feb 2017 17:28:23 GMT

Actually i was able to get it to work! I just took the IP address that is generated when I load the text editor page, added it in the Embedded Interfaces Cors Origin and it displayed the task. So one step down.

RE: Testing Embedded Interface

mikec — Wed, 15 Feb 2017 11:32:36 GMT

So question for you. I am attempting to do what i said above. I am using text editor brackets. It connects to Chrome. I built a simple page added my appian cloud domain .js and then added in the body <appian-task taskid="268452465"/> which is a valid open task assigned to me. Nothing opened in the page. I looked at the developer tool console and saw this error message:

Failed to load resource: the server responded with a status of 401 (Unauthorized) cors

Since Im new at this would appreciate any assistance:-)

RE: Testing Embedded Interface

mikec — Wed, 15 Feb 2017 11:16:00 GMT

yep thanks!!

RE: Testing Embedded Interface

PhilB — Fri, 10 Feb 2017 17:58:03 GMT

I've not actually tested it but I don't see why that shouldn't work; as long as you have an active Appian session it should function, as far as I know. If it doesn't, it's fairly easy to host a static page on a server, either through IIS or Apache, for example.