sorry I forgot another problem I'm having. When I sent the same message from a process, 2 SMS were sent, if I send one from the contact, just send one. Some idea what could be wrong?

With this process 2 SMS are received

Hi Julio,

We have updates regarding your questions:

1. We reproduced the issue with Queued Delivery status and submitted it to the responsible developer.

2. We require more information to investigate the second issue. Please check whether the sent SMS appeared on the 'Messages log' tab in your Twilio account.

3. This feature is not supported in the user task. I have forwarded your feedback to the responsible developer.

4. We require more information to investigate the issue with 2 SMS sent by the process as well. Please make sure that only one instance of the business process was run in the Process log.

Thank you and we await your reply.

Irina Lazorenko,

Hi Irina,

Thanks for your reply, and please confirm us as soon questions 1 and 3 were resolved.

• Regarding question 4, the sent SMS's were managed by an internal from the connector, the User Task called “Send SMS through Twilio”.
• Additional info regarding what was happening here is:
  • When sent an SMS from a user process using this User Task, we receive the most of times the SMS twice, but always two SMS records are created on Creatio Section DlbSmsMessage
  • When sent an SMS from the communication panel of a contact it works OK, and just one SMS is delivered, so this symptom reinforces the suspect the culprit of the 2 sent SMS and created records, was the User task “Send SMS through Twilio”
•  Regarding question 2: We won't need to solve this "problem" for now because:
  • The client confirms that he will not need to receive SMS, only send.
  • The problem could be related with a numbering issue due to the Twilio provided phone number to send SMS. Current provided number is from the USA/Arizona, and we need to send SMS to Spanish numbers, so could be there some restriction to Spanish numbers to send/answer SMS to a foreign number…
  • When our customer needs to receive SMS, we will be back to determine where the problem is: The provided numeration, some Twilio restriction or whatever

Thanks again and best regards

Hi Julio,

The responsible team released the updated version of the connector where issues 1 and 4 have been fixed. This package is already available on Creatio Marketplace. Please install the new package version and check the updates.

I have no news regarding the third issue. I will keep you updated.

Irina Lazorenko,

Thanks Irina, we will check it right now

Hi,

Actually, there is no separate Visual Studio Extension, this marketplace

application is only a reference toward the documentation on Integrating Creatio with Visual Studio.

Regards.

Hi, Susan,

I have the same issue. Did your troubleshooting successful?

Hi to all,

You should identify the cause of the issue first and foremost.

Check the process log and make sure the process was launched and “To whom should the window be shown” field was filled out correctly.

If everything is correct, troubleshoot the issue in the incognito mode.

If you cannot reproduce the issue in the incognito mode, check your browser extensions. Some of them, ad blockers in particular, could block pop-up windows in Creatio.

Hi Luca!
We reviewed the add-on and reproduced the issue on our end. That was an out-of-the-box compilation-related error. When installing the package, the system did not compile and did not generate static content.
We plan to fix this problem in future versions of Creatio. For the time being, I recommend recompiling your system.

Hi Vincent,

Creatio platform doesn't allow installing one .dll library several times (in this case, EPPlus). Both errors indicate that you already have the EPPlus library installed on your Creatio site. The 'Excel reports builder for Creatio' app uses the library, while the 'Email approvals for Creatio' app does not.

The problem can be fixed by finding the other package that has the library on your Creatio site and manually removing the library from one of the packages to resolve the conflict.