I have discussed your case with the responsible R&D team. Unfortunately, as of now, there is no possibility to implement your business task and we do have the correspondent problem registered on our side. The R&D team is currently working on implementing this new functionality in one of the future releases of the application.
Thank you for helping us to make our application better.
I have developed a service in Creatio that will be called from third parties. The service is called successfully in postman but programmatically it doesn't work. The authentication works fine and returns status code 200 and the BPMCSRF cookie. When the third party tries to call the service it gives the following message "401 - Unauthorized: Access is denied due to invalid credentials." How can we investigate this issue? Does Creatio offer a logging option so we can investigate the request and response or is there something else that we have forgotten during the implementation of this service?
For a specific page schema, the metadata of the page differs from Dev and Test env. The nr of rows is the same , but the content isnt. Is this supposed to be correct ?
Please be informed that the sole fact of the schemas being a bit different is not a problem, the question is does it cause any actual issues to the performance of the site? Also, please specify if the Test env is a full copy of Dev and if so, was that schema present on the Test env before copying? Also, did you make any changes to the schemas yourself?
Full generation is needed to build links between
configuration items. Items can be objects and schemas or
links between packages and their dependencies.
Full generation links them.
Compilation, in addition to its main purpose also generates
source files along the /src path which are necessary when
working with no-code elements and allow you to create an
instance between an object and a table in the DB.
Full generation is needed to build links between
configuration items. Items can be objects and schemas or
links between packages and their dependencies.
Full generation links them.
Compilation, in addition to its main purpose also generates
source files along the /src path which are necessary when
working with no-code elements and allow you to create an
instance between an object and a table in the DB.
Parameter IsLocked mainly affects if you can edit the schema or the package. Only the author of the lock can edit these elements. In the database, this author isn't mentioned and you can see only IsLocked.
The system will check the author on the other level.
I'm using isDetailEnabled method in client side to remove add button in detail based on specific conditions. For users in "System Administrator" role I want to allow the add button for every detail.
JSCODE:
isDetailEnabled: function(detailName){
var esq = Ext.create("Terrasoft.EntitySchemaQuery", {
rootSchemaName:"SysUserInRole"});
esq.addColumn("SysRole");// add filter for current user
esq.filters.add("UserFilter", Terrasoft.createColumnFilterWithParameter(
Terrasoft.ComparisonType.EQUAL, "SysUser", Terrasoft.SysValue.CURRENT_USER.value));// add filter for role name, joining to SysRole (which is where the name is stored)
esq.filters.add("RoleFilter", Terrasoft.createColumnFilterWithParameter(
Terrasoft.ComparisonType.EQUAL, "SysRole.Id", "83a43ebc-f36b-1410-298d-001e8c82bcad"));
esq.getEntityCollection(function(result){if(result.success&& result.collection.getItems().length>0){returntrue;}returnfalse;});returnthis.callParent(arguments);}
Since EntitySchemaQuery is asynchronous, it doesn't wait for the results to return before the isDetailEnabled function returns. You'll need to pre-fetch if the user is in the role (maybe in the init, or elsewhere) and save that result in an attribute or something, then just check the attribute from the isDetailEnabled function. Does that make sense?
I want to resctrict the file formats uploaded to creatio. For example I want to allow uploading only pdf,word, excel, jpeg files and restrict Json files.
Please note that you should register such questions as Cases for our Support team, as we will need to check your instance to see what the problem is. So please, register a new case and provide us with all the details there.
