Hello. Is there a way to fill the field values from the master window in which you opened the lookup (lookup field) and clicked the "New" button? Something similar to how adding a record in a datagrid detail works. When you click add a record, a window with fields opens and these fields can automatically pull values from the master page.
For example, I have 2 DCM cases. Let's say that I'm on Opportunity section and I am on Case 1. If a condition is met, could the DCM automatically change to Case 2? Without having to select the button shown in the next picture:
My colleague and I are trying to develop applications with specific dependencies but Creatio keeps adding dependencies we don't want to the package when we save a business process. Is there a way to turn off the automatic adding of dependencies? I'd prefer to receive an error message if I'm using something for which I don't have access.
I would love to turn this off and have an error telling me what it needs instead. The auto adding dependencies could be nice but I’d prefer to control that myself. I’ve ran into issues where it attempts to add a dependency for the same package that the item is already located in and then complains that it’s a circular dependency.
Not getting the exact same error, but similar behavior:
modifiying customer 360 list & form pages, getting account new objects, pages etc saved in my current set package, and the contacts saved automatically in a new package of Creatio's choice.... Quite confusing
There are some system settings, email templates which we would like to change according the environment in which the package is deployed. For example, we want to change the URL in email templates to that of BUAT/Production URL. Is there a way to automate this process? Is it possible to run a Business Process/ Stored Procedure exactly once, as soon as package is installed successfully?
When you add a web link or object link to your template, they are saved in Html code of an indicated template in <a href="">name</a> tag. The link in a tag is static and within template transfer, it will not be changed.
This functionality did not include the logic of creating all-purpose links, which would work when migrating templates to another environment.
This has been already reported to our R&D team so they can work on implementing the needed logic upon future releases.
