Hello. Clio team started new project Clio satelite - plugin for Chrome and Edge browser to improve developer experience. It works without installing packages or modification on environments. Compatible with version 8.+
When creating a Web Service, the URI is embedded in the configuration and cannot be set with a System Setting like the values of the request parameters.
Usually the endpoints of the customer to integrate are located in "production" and "test" environments.
In Creatio if we need to integrate with the customer's web services we need two web service object: one for "test" and one for "production".
Why don't you allow the Web service configuration to set the URI with a System Setting thus there can be only one Web service object that automatically "points" to the proper customer's environment just changing the related system setting?
I completely agree. When using web services, the username and password (or API key etc) is already stored in the system settings. I would love for the setup/config instructions to only have one place users need to go to set up the values (in the system settings). As it is now, users have to go to the system settings to add those values, but then to the web services to add the URL.
If the web service is part of a package we create and deploy for our customer, the Web Service is "read-only" on the customer's platform then it's not possible to change the URL. That's why I'm asking to let this field to be set also from System Settings and not only manually.
It is still possible to change the URL of the web service, even if the web service is located in a locked/installed package. That is the one value it allows changing.
Thank you for your feedback. We completely agree that this is a very useful and much-needed functionality. Our development team already has a registered task to implement it, and based on your input, we have raised its priority to highlight its importance.
At the moment, the task is still in development, so we are unable to provide a specific ETA for its release.
In the "Process File" element of a business process, when set to "Generate Report" the template can only be selected from the existing reports dropdown list.
I think it would be very useful to improve the "Process File" element for "Generate Report" allowing to set the template with a business process parameter just like the other process file parameters.
Agree, this would be useful for us too. Thanks Ryan for the guide on how to do something like this today! Ours are based on a handful of different objects, so we would have to have different paths for each object in the BP, but still nicer than having 10+ paths, one for each of the reports at the time of implementation (and could grow in future, so it's nice not to have to modify the BP for every new Printable report created).
I can't get the latest Clio Explorer 2.0.67 to load my existing appsettings.json (which I've been using with previous versions of Clio Explorer). I can't get any environments to load in the Clio Explorer left side panel in VSCode. I am using a Mac. No console errors if I open the VSCode dev tools.
If I revert back to 2.0.65 of Clio Explorer it all loads normally again.
It does appear to be an issue specifically with Clio Explorer (not the clio cli), since clio still shows the contents from my appsettings.json when executing clio show-web-app-list. Also since it works with the older Clio Explorer version.
I don't see a repo for Clio Explorer on github, does a public repo exist? (I'm all for going through the code to track down the issue or submit a pull request if it makes it easier to fix)
