Due those schemas usually have the EmailBody binded and this is a large string is very difficult to found the name of the binded templates, this is due Creatio show its names centered in the row where they are.
Suggestion, could export the data binded in those schemas or select which columns to see (not binded ones),
Although I do have a strong technical background, I would prefer a more user-friendly "no-code-way" of creating data bindings.
I like the flexibility of the existing data binding feature, but it would be awesome for a lot of people to have the functionality to select what they want to bind and the system does the heavy lifting and generates the technically necessary data bindings.
For instance, if the element that should be bound to the package is an email template, then you would just select the template and the system creates the bindings for you. The same applies to workplaces, dashboards, reports (incl. reports table and the word template), lookups (including their manager), etc.
Very well put. For a nocode tool, there still a lot to be implemented. A lot of great new stuff with Freedom UI but still quite some things missing for it to be truely nocode.
Can someone in Creatio please improve this? Deploying certain Org Roles is essential, it makes very little sense for this to not be possible. It really causes a lot of problems. The error I get in the deployment logs before following Vladimir's suggestion is the following (as I couldn't see any pages mentioning it when searching before):
P0001: Cannot add root administering unit. Invalid unit type specified.
I can confirm that disabling the trigger worked for deploying for me in Postgres envs, but it's concerning this kind of workaround is needed. In our case, we used the following SQL Script set to run before package installation:
ALTER TABLE "SysAdminUnit" DISABLE TRIGGER "TRSysAdminUnitRoot";
And then the following SQL script set to run after schema data installation:
ALTER TABLE "SysAdminUnit" ENABLE TRIGGER "TRSysAdminUnitRoot";
What you did is bind the SysModuleEdit record for the page supposed to open for the portal section which was missing before.
That's necessary to make sure you bound data from this table along with data from SysSchema, SysModuleEntity, SysModuleEntityInPortal and SysModule to make sure that the portal section and it's pages are correctly transferred.
It would be nice to add one more 'Delete&Bind' action to Sections, Details, Lookups etc. Id's of deleted records should be bound to the package and deleted on other environments as well when package is installed.
Thank you for bringing your idea to our attention!
I have registered it for review by the development team. They will process your suggestion and decide whether to add it to future updates of our product.
I am trying to bind the processes that I'm running from section to the package, so when we transfer the package into prod the processes will remain attached to the sections. How can I achieve this? It is unclear.
In want to bind a specific product , and its product features (ex Term,months , amount, Currency etc).Which are the objects involved in this process for successful binding ?
We use 'Data binding tool for Creatio' to bind lookups and other data to their 'data package'.
And when we bind data, the tool offers to choose one of packages. By unknown reason there are also 3rd party packages offered. And it is possible accidentally to bind data to them and not possible to delete from such packages after.
What is the filtration condition to display/hide packages in this tool?
