7.17.0 release enables the possibility to add integration with Facebook lead generation forms. All you need to do is link a landing page record in Creatio with a Facebook business page and select one of the lead registration forms on it. As a result, each submission of the corresponding Facebook form will generate a new lead in Creatio.
Furthermore, in the 7.17.0 version, customers can write private messages to your company page on Facebook or using the Facebook Messenger plug-in available on the website. You will be able to process all these messages in Creatio, they will be integrated on a customer page.
More detailed information about these topics can be found in Academy articles:
As of now, there is no Google Analytics Integration on a clean install of a standard Creatio product, also there are no similar integration marketplace applications as well. It can only be integrated with the help of the development process. In this respect, Google Analytics can be integrated through API as a separate, third-party application. Also, you can develop your personal web service to pull the data into Creatio or use OData protocol for this purpose. Please find the relevant articles on our Academy using the links below:
7.17.0 release enables the possibility to add integration with Facebook lead generation forms. All you need to do is link a landing page record in Creatio with a Facebook business page and select one of the lead registration forms on it. As a result, each submission of the corresponding Facebook form will generate a new lead in Creatio.
Furthermore, in the 7.17.0 version, customers can write private messages to your company page on Facebook or using the Facebook Messenger plug-in available on the website. You will be able to process all these messages in Creatio, they will be integrated on a customer page.
More detailed information about these topics can be found in Academy articles:
Hello colleagues, in Accelerate Global event on the session "Step-by-step guide to low-code approach realization", Nandeesh Madapadi talk about a process called "Lead from Contact" (here https://youtu.be/7g7AhrwuVX0?t=1675) I'm sure saw another session were somebody use this process also, but there a lot of videos and cannot find it :-(
Have somebody the package to this process to share it?
Scenario : For the approval action in the record page under case flow, it appears/ disappears on mouse hover the "approve", "reject" and "change approver" button
Question: Is there a option to have them fixed in the screen instead of mouse hover, so that the user can know that there is option to approve if they dont understand that they need to mouse hover on the screen to get the option
The schema name that is to be modified is called ActionsDashboardItemContainer. Unfortunately, I was not able to find any examples of code that can change that functionality,
I have noticed when attempting to build source or compile in the "Advanced" aka Configuration Tool in 7.17, I get the following error. The activity spinner continues to spin and the site is unavailable, much like it is continuing. Just wondering if some timeout value needs to be altered to avoid this?
You need to review the application logs to identify the exact error message that is received upon compiling the app. Also you need to make sure that there are no firewall restrictions for the service via the link above from your client that could prevent the client from getting the response from the server.
this error means that there is a problem with sending\receiving requests to\from IIS-server. Maybe the connection to the internet was lost upon compilation or there is some proxy that reroutes requests or there was some modification on the network layer of the IIS-server when you started the compilation. Try to compile the app once again, it should be successful now.
Again, I am local to the server... no internet connection involved LAN->LAN... same segment, no proxy and no changes to IIS layer while this was occurring (off-hours here in US). I am the only one on the network.
You need to mark this system setting as not cached (uncheck this checkbox):
And create a trigger on the database level on the SysAdminUnit table so to check if the Supervisor is logged in then the value for the setting should be modified (something like this):
CREATE TRIGGER [dbo].[SysAdmUnit_SysSettingValueTrigger]
ON [dbo].[SysAdminUnit]
AFTER UPDATE
AS
BEGIN
DECLARE @admin_unit_id as UNIQUEIDENTIFIER;
DECLARE @loggedin as BIT;
SELECT @admin_unit_id = inserted.Id FROM inserted;
SELECT @loggedin = inserted.LoggedIn FROM inserted;
IF @admin_unit_id ='7F3B869F-34F3-4F20-AB4D-7480A5FDF647' AND @loggedin ='true'
BEGIN
UPDATE SysSettingsValue SET IntegerValue =111 WHERE SysSettingsId ='F8520582-8161-4F36-A88D-028D3BDEFBDE'
END
END
where:
7F3B869F-34F3-4F20-AB4D-7480A5FDF647 - is an ID for the Supervisor user in the SysAdminUnit table
111 - value for the IntegerValue column in the SysSettingsValue table
You can do this via SQL. If this is a cloud system you can install SQL Executor (if this is a Postgresql system, enclose all column/table names in quotes)
Anyway, first get the package Id using:
select Id from SysPackage where Name ='MyPackageName'
Then get the repository Id (assuming you already added it, if not add it first):
select Id from SysRepository where Name ='MyRepositoryName'
Then update the package with the repository Id, note, the package *must* also have a version number (I'm setting it to 1.0.0 below)
update SysPackage set SysRepositoryId ='the repo id here', Version ='1.0.0' where Id ='the package id here'
Now, just refresh and you'll see the package is linked to the repository.
You can do this via SQL. If this is a cloud system you can install SQL Executor (if this is a Postgresql system, enclose all column/table names in quotes)
Anyway, first get the package Id using:
select Id from SysPackage where Name ='MyPackageName'
Then get the repository Id (assuming you already added it, if not add it first):
select Id from SysRepository where Name ='MyRepositoryName'
Then update the package with the repository Id, note, the package *must* also have a version number (I'm setting it to 1.0.0 below)
update SysPackage set SysRepositoryId ='the repo id here', Version ='1.0.0' where Id ='the package id here'
Now, just refresh and you'll see the package is linked to the repository.
I do remember someone from Creatio mentioning that they had to pull it for a couple of weeks to make updates for 7.17. If you have it in another system you could download the package from there, otherwise, you can do this with a process. Create a process that has two Read Data elements (except now you'll be reading from "Package" for SysPackage and "Storages list" for SysRepository) and one Modify data element (to update Package) then run it and you can accomplish the same.
