Hello!

Unfortunately, it is impossible to do it now, but we've registered it in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product.

Thank you!

Hi Andrii,

Thank you for your response.

I have a question : If I trigger the process from different pages, such as Account_FormPage, Contact_FormPage, or Order_FormPage, is it possible to capture detailed information in the business process flow indicating from which specific page the button was triggered?

I'm looking for something similar to how HTTP request header parameters work.

Regards,

Ajay K

Hi Ajay,

Unfortunately, when triggering a business process from a button, it's impossible to determine from which specific page the process was initiated using no-code tools. However, we recommend creating a separate business process for each page. This approach lets you know exactly which page the business process was launched from.

Best regards,
Andrii

Hi Andrii Kurta,

Thank you for the clarification. I understand that using no-code tools may not allow us.

However, I would like to explore whether this can be achieved using code.

Could you please guide me on how I might implement a solution using code? Any examples or documentation you can provide would be greatly appreciated.

Best regards,

Ajay

Hello, 

Regarding the problem with counting contacts in the ad campaign section, please contact technical support for a detailed analysis of this issue. As for the question about UTM Source and UTM Campaign, these values should contain the following information: 

The UtmSourceStr property should have a "google" or "facebook" value. Depending on the campaign source.

The UtmCampaignStr property should contain a campaign identifier (identifier from platform, AdCampaignId property of AdCampaign object in Creatio). A campaign name could also be applied for this property, but to accurately identify the ad campaign use its ID.

Hi!

Currently, only Facebook forms have been adapted for Freedom UI. You can also add the old section with ALL forms to Classic UI and use it, it still works.
 

For now, we do not plan to evolve the use of Landing Page object. 

As you know, landing pages are a great way to capture leads and generate interest in your products or services. However, they can be limited in terms of the data they can collect and how they can be integrated with other systems. 

Webhooks, on the other hand, are a more powerful and flexible way to collect data from your landing pages. They allow you to send real-time data to your Creatio CRM system, which can then be used to trigger automated workflows, update customer records, and generate reports. 

Here are just a few of the benefits of switching to webhooks: 

1. More automated workflows: Webhooks can be used to trigger automated workflows in your Creatio CRM system, such as creating new records of any type. 
2. Better integrations: Webhooks can be integrated with a variety of other systems, such as marketing automation platforms and customer support software. 
3. Enhanced error handling: Webhooks provide robust error handling capabilities, ensuring that data is delivered successfully even in the event of unexpected issues. This minimizes data loss and ensures that your Creatio CRM system remains up-to-date with accurate information. 

If you're looking for a more efficient and effective way to collect data from your landing pages, I highly recommend switching to webhooks. 

To help you get started, I've included a link to our webhook setup guide below: https://academy.creatio.com/docs/8.x/no-code-customization/base-integrations/webhook-service-integration/overview

Best regards, 
Anton
 

Anton Starikov,

Hi Anton, 

Thank you for your detailed answer :). 

However, it seems you do not have understood my question.

I have switched already webhooks. It does indeed possibilities. But, on a business marketing user side, the use of webhooks is really incomplete today in Creatio, there's loads to build, for things that honestly could easily be there OOTB...

For example, everytime we have a new form we want to integrate with (Landingi, Wordpress, etc...) for which we have fields we need to map in Creatio with specific values (drop downs and all), we need to work with IDs... it's not a natural nocode work like it used to be. 

Also, when sychronising the webhooks in Creatio, using the FormSubmit object for example, we only have a list of Formsubmits section rather than a structured way to put them all together under one name, like the "Facebook form" section offers... This is quite inconvenient way to work.

Also, the documentation and examples on how to use webhooks is really scarce in the academy, and mainly limited to using FormSubmit. Which has unforeseen limitations, such as creating a contact record not using all the contact fields available (Eg: https://community.creatio.com/questions/contact-data-submitted-form ). 

On theory, it is great that possibility of using Webhooks is provided. 

In practice, the use of them is not polished and could be greatly improved both on the admin and on the non-admin user side of things.

Damien

I do love using webhooks for landing pages, much more flexible for the most part. However, one thing I miss is the ability to set defaults. For the older landing pages, you had a record defined for each form, and then could define default values for a specific form inside of Creatio. You could change those defaults in Creatio without needing to modify the HTML for the form on the website. That was great and is a missing part of using webhooks. 

I would love to see the following changes for webhooks. 

1. Ability to create a specific webhook for a specific purpose (it could be named in a way that defines it's purpose)
2. Records could be tied back to the webhook it came in through, so you know it came from webhook "ABC" in the same way you knew a record came from Landing Page ABC. This is really more of a way to identify the form (in the same way you could identify a record came from a landing page) - this one might not really be doable since not every usage of webhooks is a "form", but maybe that could be a simple option on the webhook to add an entry to some table that can generically link to any object type?
3. Defaults could then be added on a webhook-by-webhook basis so any record that came in via a specific webhook would have those default values added

Sure, you can do all of this with webhooks now by including extra data or maybe an extra process to add some of the default values based on data that identifies where it came from, which would exist as hidden values in the HTML of the form. But that means possibly changing the HTML if the defaults ever need to change and it was so easy to manage the defaults for landing pages before - it would be great to have for webhooks. Plus, it's up to you to include some way to identify that a record came from a specific webhook (really meaning from a specific form)

Ryan

Ryan Farley,

thanks, exactly what I was trying to say for the setting defaults part, but in much better writing 😅

There is a section with defaults used at the moment in Freedom UI, the Facebook form section. If you create  a form their with defaults, and you add that form ID in your webhook (field that already exists by the way...), there should be an easy and OOTB way to add those defaults. Which as such is not a new feature, just bringing back classic UI landing page integration feature of defaults... 

We would have then the best of both worlds 🙂

Hi, 

Good question indeed, was wondering recently how to increase that. Documentation is scarce on how to configure webhooks further than FormSubmit and OOTB behaviour.

Damien

I guess there might be another way: to build custom business process that will start on creating of new Submitted form record and will map and transer data from form record to corresponding contact record. But I'm not sure. 

There is an out of the box process that does this that you could extend. It's called "Populating Contact with Submitted form's data". It's a pretty simple process and would be easy to include additional fields. 

If you didn't want to create a new version of that process, you could also just create a new process that had a start signal of Submitted form added and contact is filled in or Submitted form modified in contact field (and it's filled in) and then copy over the remaining values.

Ryan

Ryan Farley,

Thanks a lot, will go to try

Hello!
 

I am afraid the deletion of already sent emails is not possible. 

Only "draft" and "planned" ones may be deleted.
Deletion of sent is against our company policies, as they are connected to Active contacts in the licensed amounts.

Thank you for understanding.

Best regards,
Anton

Hello,

We recommend you to try out this marketplace addon that allows you to manually mark any communication option as primary, which is not overridden by adding new options to the list:

https://marketplace.creatio.com/app/primary-communication-options-creat…

Mira Dmitruk,

Hello, could you please, clarify, if one installed that add-on, whether that option is available in import also? Or only for Contact form?

Artem Evdokimenko,

Yes, it is possible to mark the emails as primary with this addon when importing from excel, the column is "IsPrimary" and has values "yes" or "no". 

Hi Ajay,

Let's look at how the customization process works in general. 

When a customer makes any changes to the installed application, your core logic remains unchanged. Instead, the app is extended with a new package where replaced schemas are created, inheriting your core schemas. When you make new changes to the app and customize these core schemas, after delivering a new version to the client, only those core schemas will be updated. The customer's inherited schemas will remain unchanged.

Therefore, custom changes will not be overwritten. However, we recommend supporting backward compatibility to avoid breaking custom changes after delivery.
 

If you are going through the update process together with the client, we suggest using the delivery process article to build a safe delivery process.

Hello,

Please find the example of such a filter on the screenshot below:

Bogdan,

Hi, Thanks for your help, anyway to know which click part in the email content the audience click in the result? Say, if there are two click parts in the edm, One is interested in "A" product, the other is "B" product, how to use filter to know who is the contact interested in "A" product" ?

thanks. 

Hello,  

Thank you for your question!

Unfortunately, there is no way to filter and group contacts by clicking on a specific link. However, we have registered a request for the responsible R&D team to implement this feature in future versions of our app.

Jeffrey,

You can filter for contacts that clicked a specific link in a bulk email using the related object "Click through links with email". See details here: https://customerfx.com/article/creating-a-filter-of-contacts-that-clicked-a-specific-link-in-a-creatio-bulk-email/

Ryan

Hi!

We do not currently support file transfers, but we will register a request for a description of the documentation if possible.
 

If you have any further questions, please send them in response. We will be happy to help.
 

Thank you for contacting Creatio Support!
 

It's not very straight forward, but it is possible. Basically, you'd need to encode the file as a Base64 string, then transfer it as a string value to the webhook. Once received decode the Base64 string back to a file byte array to save as an attachment somewhere. 

If this is coming from a web form, you can use Javascript's FileReader to convert the file to a base64 string. See https://stackoverflow.com/questions/36280818/how-to-convert-file-to-base64-in-javascript

Then send the value as a string to the webhook. You could add a process to trigger on record added of your entity. Then decode the string to a byte array. See https://learn.microsoft.com/en-us/dotnet/api/system.convert.frombase64string

Then save the byte array as an attachment on the record. See https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/back-end-development/api-for-file-management/examples/file-management-examples

Ryan

Hi, Victoria!

Please turn to us via Creatio Support so we can examine the system behavior in further detail.