Landing Page Creation Freedom UI

Hi Community,

I’m setting up Creatio landing pages that submit to Creatio via webhooks and are processed by a business process. I can design, publish, and download the page as HTML. Example snippet:

<script src="https://webtracking-v01.creatio.com/JS/crt-landing-page.js"></script>
<script>
  crtLanding.webhookServiceUrl = 'https://webhooks.creatio.com/webhooks/bb0c54c1-f7f0-4d8b-a405-c94d24ceed0d';
  crtLanding.setParameter('LandingPageId', '51de0cbe-fd8a-4be6-92f2-300019f77fc3');
</script>
<form method="POST">
  <input name="FirstName" />
  <input name="LastName" />
  <input name="Email" type="email" />
  <input name="EntityName" type="hidden" value="FormSubmit" />
  <input name="FormId" type="hidden" value="05c63f9b-ea9d-626c-6f51-c1e917502582" />
  <button type="submit">Submit</button>
</form>

Questions:

  1. Cross-environment design & binding
    • If I design the page in DEV and export the HTML, can I “data bind” it and transfer to another package?
  2. Webhook URL per environment
    • Is it a best practice to publish a unique landing page per environment (so that the corresponding crtLanding.webhookServiceUrl and IDs are environment-specific)?
    • Any recommended pattern for switching the webhook URL and IDs when the single HTML designed (landing page) in one environment and hosted outside Creatio and required to be used in multiple environments?
  3. Local DEV system settings
    • When working in local DEV I get:

      “We’re unable to connect to service. Please complete ‘Identity server Url’, ‘Identity server client id’, ‘Identity server client secret’ and ‘Social Web App Account’ system settings and try again.”

    • What’s the correct way to populate these system settings for a local developer environment specifically for landing pages/webhooks?
      • Do these have to point to an environment-reachable Identity Server, or can local placeholders be used?
      • Any docs/checklist for minimum settings required for landing page publishing and webhook processing in a local DEV?

References:

Looking for confirmation of the recommended approach (per-environment pages vs. one HTML with variable config), and concrete steps for filling the Identity Server / Social Web App settings in local DEV so I can publish/test. Thanks!

Like 0

Like

1 comments

Good day,

Answering your questions below:

    1. Cross-environment design & binding

  • If I design the page in DEV and export the HTML, can I “data bind” it and transfer to another package?

From a technical standpoint, it is possible to move LandingPage records from one environment to another using data binding.

This will not, however, move the page itself, but will only move the value of a URL text field. 

The landing page itself is generated from a LandingPage record when you "Publish" it  :

landing page URL


Depending on your requirements, you may design you own custom landing page and connect it to a LandingPage manually. 

The important prerequisite is to include the HTML code responsible for webhook processing an google analytics in the landing page.

    2. Webhook URL per environment

  • Is it a best practice to publish a unique landing page per environment (so that the corresponding crtLanding.webhookServiceUrl and IDs are environment-specific)?

Our strong recommendation is that one landing page is used only for one environment.

If your intention is to reuse the code only, it is possible to use the overall structure of the code and substitute only the webhookServiceUrl and the LandingPageId values within it.

webhookServiceUrl is a URL, which corresponds to the webhook API key specific to each environment. 

LandingPageId is also generated based on the LandingPage record id. 

In the event that modifying these values in the HTML of the page is problematic, our suggestion is to publish unique landing pages on each environment instead

  • Any recommended pattern for switching the webhook URL and IDs when the single HTML designed (landing page) in one environment and hosted outside Creatio and required to be used in multiple environments?

As previously outlined, usage of the same landing page for multiple environments is not advised from a technical standpoint.

A landing page has a strict binding to a webhook API key and a LandingPageId.

However, if the purpose is to reuse the code, we advise to make sure to substitute the values of webhookServiceUrl and LandingPageId contained within the code

    3. Local DEV system settings

  • When working in local DEV I get:

    “We’re unable to connect to service. Please complete ‘Identity server Url’, ‘Identity server client id’, ‘Identity server client secret’ and ‘Social Web App Account’ system settings and try again.”

This message points to the fact that the environment does not have a registered identity service.

We can complete a registration of this sort for your environment. 
Should you require assistance with this, please reach us out at support@creatio.com for further assistance 

  • What’s the correct way to populate these system settings for a local developer environment specifically for landing pages/webhooks?
    • Do these have to point to an environment-reachable Identity Server, or can local placeholders be used?
    • Any docs/checklist for minimum settings required for landing page publishing and webhook processing in a local DEV?

When it comes to filling out these values on a local environment, placeholder values will not be sufficient. 
Local environments, similar to cloud requirements, have to be registered on identity service on our end, and whitelists are to be set up on both ends to make sure that the site and the identity service may communicate.

Identity service reachability is one of the prerequisites for landing pages and webhooks to properly work.

More information on basic setup details required for webhooks (and, by extension, landing pages) may be located here:

https://academy.creatio.com/docs/8.x/no-code-customization/base-integra…


Thank you for contacting Creatio support!

Show all comments