I tried downgrading packages to 7.18.2.1236 and everything is working fine. The next thing I need to do is downgrading the database version from 7.18.4.1532 to 7.18.2.1236. Which is the correct way to fix this issue because I'm getting "Versions of application "7.18.2.1236" and configuration "7.18.4" are incompatible"
It the fields are mandatory then make them mandatory in the section wizard directly, but not applying red asterisk via css. Using the wizard the fields will be mandatory even when adding a new record.
Hi Oscar, the labels that you can see are field default values that is being used as field label which I have implemented for proper alignment of section fields layout.
The Label Group Name is itself a field and the blank space for the value for Group name is another field whose title has been hidden.
I am trying to implement JIT when a user is not present. But by default it is creating a user as "Company Employee". Any suggestions how I can identify and create either Company Employee or Portal user based on the response that has been received in the SAML token.
If you want to enable JIT for portal user you need to make sure that key <add name="UseJit" value="false" /> is added to the block related to the "SSPSsoAuthProvider"
After that please make sure that SspLogin.aspx is specified in all keys instead of NuiLogin.aspx to make sure that user will get a proper portal cookie in case if you want to use a Service Provider initiated SSO flow to create portal users.
Also please note that in this case ordinary company employees will have to login via direct link only or use the link to NuiLogin.aspx module if they want to use SSO as well.
We have an observation from 7.18.5 Cloud Version of Creatio. User A has added his email inbox. When User B logs in using User B's credentials and goes to Contact record of User A, User B is able to see all emails sent by User A!
This could be a possible security issue unless we are missing something.
This option should be disabled for the user in question. In case, this is not enabled for user B - please, reach out to us at support@creatio.com so that we could have a closer look at the problem.
I'm trying to install a package using update from file system. After the installation everything is added successfully, except for some objects which have the following status (Source code update required).
I tried the following commands but nothing happens.
The structure of the object in the database is modified successfully but this message is displayed again.
I tried the recommendations you sent but it still did not work. This happened because I was using the landing version 7.18.2.1236 and the package version was newer (7.18.4.1532). After downgrading the package version everything was compiled successfully.
As for the first error message, find this Id from the error message in the UI sources in the developer console F12 -> Sources tab -> Search and see which object is returned in ViewModule.aspx when searching for the Id from the error message (like here https://community.creatio.com/questions/how-overcome-item-unique-identi…). Then you need to remove the SysModule record from the system that is related to the object found in the UI sources.
We have concerns about security of lodash module used in client app. As we understand, version 4.17.19 is used in 7.18.5. Do you plan to update it, or can we have an instruction on how to do so. Thanks in advance!
Sorry for the delay with the response. Unfortunately, it is not possible to add cases to the detail page because the DCM module is not compatible with the detail page.
We will create a request for the R&D team to implement functionality to create a DCM in the detail pages as well.
I urgently need to confirm if we can install the package with the development done on instance with version 7.18.5.1500 to the instance with the new version, i.e, 8.0.
We do not recommend transferring customizations with a package between instances with different versions as it may lead to the errors while applying customizations and as a result affect the system.
I'd suggest to first update the instances to the same version, double-check whether the customizations are still working properly and then proceed with transferring it from one instance to another.
