Hello Julio,

1) Choose the needed Desktop on the welcome screen in right bottom corner and click the settings button

2) Add the new Chart, click "Set up chart" and fill ALL required fields inside of modal window. Save the page.

3) Check in DB is record created successfully by this query (ChartWidget_r2b2wf3 - your widget name):

select  * from SysLocalizableValue
where [Key] like '%ChartWidget_r2b2wf3%'
order by ModifiedOn desc

4) To add image - open settings of the new Desktop (right top corner </> sign) and add "Images"

5) Open Advanced Settings Page, find the new Package with new Desktop, click "+ Add" -> Data. Here we have to create two connections:

5.1 Object - Desktop. BOUND DATA - name of Desktop

5.2 Object - SysLocalizableValue. BOUND DATA - Key  = "ChartWidget_r2b2wf3" (Widget name from Step 3), choose all of them

In the end you'll have new package with 3 files inside (1 Module and 2 Data)

P.S. If on the step 5 you'll receive any errors - do Flushall in Redis.

Thanks Anhelina and sorry, no-code?

Also, my instance is cloud, I have not access to db, is another way to bind this?

Julio Falcon (Cibernética),

It's a no-code method. You need DB only for step 3 but you can replace it by checking if "ChartWidget...." appeared in the Desktop settings list of strings (Advanced Settings -> enter the name of your new Desktop in search panel -> Left panel with different settings -> Open Localizable strings).

Hello!



Folders are stored in a separated table for each section, [object name]+Folder.

For example, for the contact section, it's ContactFolder.

For sections that were created exclusively in the Freedom UI, folders are stored in FolderTree.

 

Hi Kevin,



There is no such option for now.

But we've registered it in our R&D team backlog for consideration and implementation in future application releases.

Thank you for helping us to improve our product. 

Hello,

I recommend checking the academy article on Automatic data binding to find more details on how this functionality works. 

Mira Dmitruk,

This link doesn't work.



And I would like to vote for making this functionality optional. We don't transfer Workplaces and binding to our customers - they used to organize workplaces by themselves, so deleting automatic binding is extra headache for us



Kind regards,

Vladimir

Vladimir Sokolov,

 

We are sending you the instructions once again: https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…. As you were informed earlier, there is currently no way to control what data Creatio binds automatically when making saves in the section wizard.



However, we have registered this idea to our R&D team backlog for consideration and implementation in future application releases.

Hello,

Currently, there is some hardcoded logic that saves some of the changes into the Custom package regardless of the package that is set as the current one.



For example, when you turn on administration for an object it will save these changes to the Custom package, the same behavior can be seen when setting up a change log for an object.



As a workaround, you can move the created files to the desired package by using the "move to another package" feature in the configuration of the site. We have additionally added this request to an already existing task for our developers to change this behavior in future releases.

Bogdan,

Hi! When setting up advanced operations nothing appears in the Custom package. 

Hello Ivan,

I have an article here that shows how to bind the column layout to a package. 

https://customerfx.com/article/including-the-default-column-layout-for-…

Ryan

Hi, Ryan



Thank you for sending me this article. We already tried this method and it worked on some other grids, but, unfortunately, not for OpportunityPageV2OpportunityProductDetailV2.

Do you have any idea if there's any other method for binding this grid, or if could be an installation from an environment to another?



Best regards,



Rareș Ivan

Hello Javier,

Hope you're doing well.

It seems at the moment the only way to solve your business task is to create a separate SQL script that will transfer the required data:

• https://community.creatio.com/questions/binding-base-system-setting-val…

Additionally, in general, there is a general recommendation not to consider the meaning of base values, but to add new ones to the reference and bind them to a custom package. This approach simplifies the transfer of data between environments and helps avoid the hassle after an upgrade or, for example, after re-installing the data bindings in the environment.

Best regards,

Roman

Hi Roman, 

The problem is that I can't bind the default columns of an OOB section, and that is something that I can't create a new record to fix it. 

There should be a easy way to bind configuration of the section grid, R&D should take a look at that. 

Best regards, 

Javier

Hello Javier,

Thank you for your reply. I will create a suggestion for our R&D team so they could implement the logic of binding system settings values and OOTB lookup values that are already bound to base packages in the next application releases.

Thank you for finding such a system behavior and helping us in making the application better!

Best regards,

Roman

Hello Dharini,

Hope you're doing well.

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:

https://community.creatio.com/questions/how-can-we-bind-access-rights-data-section-dashboard-2

In your particular case the needed table like Sys[SectionFolder]Rights.

Best regards,

Roman

Roman Rak,

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'. 

Hello Dharini,

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 'not recommended':

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.

Best regards,

Roman

Roman Rak,

Thank you Roman. So it is more about skill than anything to do with the product.