Hello,
on freedom-ui, i would like to add a custom sidebar component, to handle phone calls notes.
When a call is over, the sidebar would open to let the user enter some notes about it.
So far i made an angular app to test, according to this guide :
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…
Now that my angular app is ready to upload, it seems i can't do it because our creatio development instance is not deployed on-site : the system cannot be used with file system development.
(https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…)
Is there any workaround for this ?
Should i try to make it in a different way ?
Best regards.
Patrice
Like
You don't need a local system to add it. See https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/front-end-development/freedom-ui/remote-module/implement-a-remote-module/overview#title-3971-11
Also, you could use a clio workspace as well. Video tutorial here: https://www.youtube.com/watch?v=CE5uETqTsyQ&list=PLnolcTT5TeE2BMFf_XmJrSwpnbcLCLJkb
mmm, i cannot create clio workspace : "Error running command ClioSQL.createw: Command failed: clio createw . This is likely caused by the extension that contributes ClioSQL.createw."
I tried to reinstall .NET 8 / clio 8.0.1.32 / clio-explorer, but no luck :/
Have you installed the correct clio tool? There are other tools available for installation with the .NET tool. Did you use
dotnet tool install clio
and what is your output for this command:
clio ver
I installed clio with "dotnet tool install clio -g"
the output of clio ver is :
[INF] - clio: 8.0.1.32
[INF] - gate: 2.0.0.34
[INF] - dotnet: 8.0.14
[INF] - settings file path: C:\Users\myuser\AppData\Local\creatio\clio\appsettings.json
Hello,
try running clio createw manually (via terminal in your project directory). If you get an error, the output will provide more details (e.g., missing parameters, authentication issues, or misconfiguration).
Thanks for the tip, i finally could create workspaces :
it was an appsettings.json issue, the environment id was incorrect in that place.