Looks like it was the Playbook that broke this, since it also creates a BootstrapModulesV2. As a workaround to get this to work, for now, you can create a new replacing view module for BootstrapModulesV2 (in Custom package, or any package that is further down in the dependencies than Playbook and the BpmCharts packages) with the following code added (*this adds what is in the maps package as well as what is in the Playbook package)
Looks like it was the Playbook that broke this, since it also creates a BootstrapModulesV2. As a workaround to get this to work, for now, you can create a new replacing view module for BootstrapModulesV2 (in Custom package, or any package that is further down in the dependencies than Playbook and the BpmCharts packages) with the following code added (*this adds what is in the maps package as well as what is in the Playbook package)
We have renamed Activities section to Interaction Logs and also configured fields using mobile application wizard under Main workplace. But when we install the package in cloud instances, the Activities section is not getting replaced with the fields that are configured in local. I have bound the "Main workplace" in SysMobileWorkplace once again with force update on Name.
I would like to know about binding the sections within the Main workplace in Mobile Workplace Setup.
The output of the section is stored in the mobile application manifest, therefore, if you transferred all the records about the section and the manifest, then the section in the mobile application will also be transferred.
Please check out the information about mobile application manifest:
Thanks for the detailed reply Bogdan. We have transferred all the files related to mobile application and workplace. As we use the default workplace the
MobileApplicationManifestDefaultWorkplace is getting transferred.
All sections and its page setup got transferred as part of the package except for "Interaction Logs" which is nothing but "Activities" section with some customizations. Is there a way we can data bind this?
It seems not possible to bind just one section. Just import the package like you did before. If you are going to do it, please firstly make sure that you have this section on your dev/prod app, from which you import it.
Actually we performed some tests and most likely the problem in Manifest file.
Please check your MobileApplicationManifestDefaultWorkplace file in configurations and make sure that you don't have any comments here(because json doesn't like any comments).Make sure that you have "Interaction Logs" instead of my "Activity" here. Also please check if the attribute "Hidden" is false and you have the same json properties. Screen below:
Also please check out the this link, here is manifest file with all needed properties which were created automatically in manifest json file. Please compare it to your manifest and you might find the error there:
We have implemented custom section for opportunity similar to OOTB with DCM. The stage movement is restricted to few users as per acess rights.
The stage movement happens on click and should be allowed only when reason is provided which is captured as detail through pre-config page in business process
if it s cancelled it is reverted back to previous stage.
(Business process is called when on change of value in DCM stage look up happens- through js code in edit page)
Right now it is allowing users without edit access to edit the DCM though insuffient permissions error shows up.
Can someone guide me implementing the same or suggest any alternate approach?
Also let us know if this stage movement can de denied to other valid users unless the current user initiates movement and gives reason or cancels it.
The users can update the record with the processes, even if they do not have rights to edit the record manually. This is longstanding logic. In your case it is better to add some some condition with code. The idea is the following - if the user has to modify the record (the condition is met) - the button becomes visible and user can update the record with the process. Else - the button is not visible on the page.
One more idea is to restrict process launch completely in the process properties. This feature is available in 7.18.0
I have tried adding new communication option under lookup "Communication option types". but I want it grouped under existing "Phone" type. Please help in implementing the same.
In order to add the new value to the group, please open the lookup "Communication option types", open the new record you've added and add "Communication option" on the detail(see the screenshots below)
Thank you Yurii. Incase of databinding lookup to package, Is it enough if I data bind "Communication option types" alone? because addition in communication type is not reflecting. should I add it directly in respective instance?
It's not recommended to bind the access rights to the package. All system administration settings like object permissions, operation permissions, roles, users, distributed licenses must be set up in the production environment directly.
However, you may find this Creatio community post useful if you would like to try to transfer access rights using an SQL script in the package:
Hi Roman. Can you share why it is not 'recommended'?
We have heard different versions from different sources in Creatio. The take away for us has been that - It is 'feasible' to data bind access rights in a package but not 'recommended'.
At the moment, the mechanism for import/export of access rights, the structure of organizational/functional roles cannot be performed using the basic tools, as far as it complex for the architectural implementation. Our R&D team is currently working on its implementation and it will be available in future releases.
About the question of why it is 'notrecommended':
from a development point of view, this business task is complicated, since unique record IDs are created for each system, so that's why we do not recommend transferring access rights by development. And in case you decided to bind this data and transfer to another environment we suggest checking all changes on the copies before delivering it to the prod sites.
"responseText": "{\"responseStatus\":{\"ErrorCode\":\"RequiredColumnsEmptyValuesException\",\"Message\":\"Title, Account, Country fields are required.\",\"Errors\":[]},\"rowsAffected\":-1,\"nextPrcElReady\":false,\"success\":false}",
Hi Team, Require a clarification on the API key related to OCR.Space . Should the API key be unique for every instance (cloud/on-site) that we test in mobile for using the business card scanner app?
The API key should not necessarily be unique. However, we recommend using a different API key instead of the default value. If you use the default API key, the number of sessions to the OCR.Space service will be limited.
Hi Ivan, Can you please provide an update on this ticket? Its of high priority, has been open for more than a week and we require this for one for clients.
You added required contact fields which is why it is not possible to create a contact without filling out those fields. The error description includes the list of these fields: "Title, Account, Country fields are required". You should make those fields optional on the database level to resolve this issue.
Kindly suggest a way to lock fields within a detail when we click on Save button of the detail. This should happen without any dependency on other fields within the detail (unlike we usually do based on boolean value true or false).
You could use the CreatedOn field for this. It doesn't get populated until the save button is clicked (not the CreatedBy - it gets populated right away when the page is opened in add mode).
You can create a business rule that makes the field locked if the CreatedOn has a value. Then, the field will be editable when creating a new record, but will be locked as soon as the save button is clicked.
If this route doesn't work, you'll have to use an attribute and code as Oscar mentioned.
Attributes are required to use to lock fields on the page based on some conditions so it's hardly possible to do without any dependency on attributes. Or you can use document.getElementById JS method and change the .style.pointerEvents to 'none'.
You could use the CreatedOn field for this. It doesn't get populated until the save button is clicked (not the CreatedBy - it gets populated right away when the page is opened in add mode).
You can create a business rule that makes the field locked if the CreatedOn has a value. Then, the field will be editable when creating a new record, but will be locked as soon as the save button is clicked.
If this route doesn't work, you'll have to use an attribute and code as Oscar mentioned.
