Hi Patrice,

This error message occurs since the element with "usr-historiqueproduit-view-element" selector was already registered upon first init:

sdk.registerViewElement({
                type: 'usr.CustomViewElement',
                selector: 'usr-historiqueproduit-view-element'
            });

In your onEnityInitialized you need to add additional check if the element was registered in DOM or not (for example as proposed here) and as a result of this check perform registration or not.

Thanks Oleg,

i was not aware of the CustomElementRegistry api, i thaught it was a Creatio thing.

Now i know where the documentation is ! (mozilla.org)

Best regards,

Patrice

Hello,



It`s seems to be an issue that our support should take a look. Please send us an email at support@creatio.com



Best regards,

Serhii

 

i created two custom objects for GlbQuestionnaire and GlbQuestionnaireType but the error still appears

LÉZORAY Nicolas,

 

Hello,

 

The developer has published a new version of the add-on with fixes for these errors. Please install the latest version via the link and ensure that everything works as expected.

Q4 2023 : https://academy.creatio.com/docs/release/creatio-roadmap?check_logged_i…

@Damien, is this link now offline for you also? Can’t seem to access it! Anything in the roadmap with regards to improved analytics/excel reporting by any chance?!

Hello,

Linking a column filter of the current object with another unrelated object is currently not possible. We only operate on the object and its own columns (including columns through direct relationships). 

What you need to do is *not* set required on the field itself. This makes it required in all cases. Instead, leave required unchecked and add a business rule on the full page to make the field required. This way, it won't be required on the mini page, but it will be required on the full page.

Ryan

Hello,

There are several ways to transfer leads to Creatio. 

1)create lead manually

2)from bulk emails

3) create a lead from the landing page

The way you describe it is for working with a landing page. 

The [ Landing pages and web forms ] section is used to set up integration between Creatio and web forms on your websites. As a result, each time an integrated web form is submitted, a new record is automatically created in Creatio using data from the submitted form. Landing page integration can be used for generating leads, adding customers to event participants, automatic order registration, and more. 

The main idea of Lead channel and source is tracking from which website leads come to our system.

The channel field contains information about the type of web resource from which this lead came (for example social network). The source contains information about the name of the web resource from which the lead came. Creatio uses UTM marks to track lead generation channels. They help to analyze which resource leads come from. More information about in this article: https://academy.creatio.com/docs/8-0/user/marketing_tools/website_track…

More information about how to work with Lead channel and source can be found at the link:https://academy.creatio.com/docs/8-0/user/marketing_tools/website_track…

Viktoriia Hrynchuk,

 thanks for the reply. My question is more geared towards adding a lead manually that we get at an in person trade show. We have decided to use 'Event' as the Channel and then create an Event for each specific trade show to connect the leads to that event.



Ex.

Channel  = Event

Event = Waste Expo 2023



Thanks again for the reply.

Hello,

Yes, you can use the Event as Chanel, but after you register the lead you need to manually import it to the necessary event.

I did this in my Recently Viewed Records add-on in the marketplace, it wasn't easy and took a bit of a hack. You'll need to override the MainShell  and what I ended up doing is add a button into the shell that I move at runtime into the ShellHeaderToolbar. Feel free to look at the source of that add-on to see what I am doing to accomplish this. Ideally, it would be great if that were a container and you could add items to it, but sadly not the case.

Ryan

Hello,

Unfortunately, the logic of inserting an image through a macro into a letter template is not implemented in Creatio.

I am broadcasting your wish to the development team to consider the possibility of adding similar logic in future versions.

 

Ok thanks

Hello,

One of the ways to disable this logic is to override the method CalckOpportunityAmount, in order to do so you need:

1) Create a replacing object for the OpportunityProductInterest in your package

2) In it click "Open Process"

3) Add the following code to the Methods tab

Hi Dmytro,

thank you for your reply.

I tried but it does not work, my custom package is an assembly package.

Any idea?

Weird, it worked for me when I added this code to a Custom package.

Try adding it there and see if it works. Also, try compiling the configuration and see the result.

In [Call] object, there is also IntegrationId field, which is filled with a concatenation of time stamp and ids but i can not figure what these ids are related to...

Hello,

For each of the operators, the time will be recorded following the same logic: when the phone started ringing when it was picked up, when it was put on hold, and when it was hung up.

In this case, it is necessary to clarify how transferring a call to another operator affects the call duration of the first operator. The first operator is no longer speaking with the customer, so where is this time supposed to be added?

Conversely, the second operator to whom the call was transferred, had not been speaking with the customer before the call was transferred to them, so where should this time be attributed?

Hi Sergii,



According to the developer documentation, the transfer does not seem to be really handled, there is start / hold / drop events, not transfer.



Maybe it's still something to be ?

Maybe i'm misunderstanding the way phone actions actually works ?

Maybe it's a Asterisk configuration thing or something ?

Hello, 

At the moment, filling in the fields ParentCallId, RedirectingId, and RedirectionId is not implemented. When a call is redirected, three records are created:

1. The incoming call that arrived for the user.
2. An outgoing call is created by the user when transferring the call to another user.
3. An incoming call for the second user who accepted the transferred call.

Unfortunately, based solely on the call statuses, it is not possible to definitively determine whether the call was redirected according to the system's data. As an option, you can try implementing logic to populate the aforementioned fields as part of your project.

Is the functionality that populates the parentId and redirectionId fields, available in the new Asterisk connector ?

actually, we have not found how to identify that it is a transfer with the 3 lines created. 

Hello, 

Currently, for the AsteriskV2 connector, the fields RedirectionId and RedirectingId are not populated. However, we have plans to implement this in the future. We have already registered the idea for our R&D team to implement this functionality in further releases.