The final window of the LAUNCH flow is completely customizable and influenced by the HTML entered at:
Console > Settings > Customize Appearance > Launch Complete HTML
In the example above, some simple HTML is displayed to the end user with a button that, when clicked, calls the closeWindow() function, which:
- Posts result back to the window that opened the LAUNCH flow popup (i.e. the host application); and
- Closes the LAUNCH flow popup.
The result object has the following properties:
|cycleId||The Id of the newly installed integration within your end user’s account||xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|
|status||A string indicating the status of the newly installation integration cycle.By design, will always be active, unless an issue arose during installation, in which case it will be paused.||active|
|webhooks||An array of URLs representing the endpoints of the webhooks included within the newly installed integration template. This is important where your application needs to send data to Cyclr to trigger the newly installed integration template. Where the newly installed integration template makes use of more than one webhook, the order of the URLs in this array matches the order of the webhook steps in the template.||["https://webhooks.cyclr.com/Jd78JHd9"]|
Cross domain issue in IE10
Internet Explorer 10 does not allow window.opener.postMessage() to be used from a page on a different domain to the opener. There are ways around this to enable the result of the LAUNCH flow to be posted back to your application.
Redirect after LAUNCH Complete page