Hello Community,


Logging of incoming and outgoing API requests via Custom configuration services in Creatio is a very typical use case wherever system integration is in the picture. Logging the absolute URI, request/response body, response status code, any custom headers added to the request are standard in any enterprise system. 

I could not see any utilities or out of the box features to help log these requests. This is right now done by maintaining custom tables in the DB and logging any incoming or outgoing requests through custom logic.


The following features would help - 

  1. Logging inbuilt into the WebService element. It would help to have all outgoing requests using WebService elements be auto logged in the data base and be available for quick reference on the UI. An additional idea could be enabling a 'manual retry' option from the UI for use cases where an outgoing request failed  even after N number of configured retries.
  2. Utility or helper Classes on the server side which assist in tracking outgoing or incoming requests in the data base. A UI view of these logged requests could also help. Right now, we have to use 3rd party logging solutions like Loggly and write custom logic to maintain these logs.



Our R&D team has a problem registered on this topic on their side so to enable easy logging setup in the application UI for custom web-services and this problem is in the "Accepted" status so we can expect this logic implementation in one of the nearest releases. I will also let them know about this community idea so to speed up the problem solution.


Thank you for reporting this issue to us and helping us to make the application better!


Best regards,


Oscar Dylan,

Thank you Oscar.

Show all comments

Hello all


We have a Package with a few object schemas and source code schemas and we work out of file development mode. When we upload the files from file system to the application, we get an error saying "The type or namespace name 'Logging' does not exist in the namespace 'Terrasoft.Configuration'. Are you missing an assembly reference". This error happens in a few Autogenerated files (In the C# Class files for new objects we had created).


This is weird because we tried installing this on a brand new Vanilla instance and the same issue persist. Few questions below - 

  1. Why does this happen and what is the fix for this?
  2. Is this related to the contents of our package or related to the setup of the instance itself?

Appreciate your help!


Like 0



Hello Community!

This has been a recurring problem for us with no root cause/fix in sight. Request your help. 

Hello community! Would appreciate your help here

Show all comments