Hello Nicolas,

At the moment the scale settings can be configured and saved only for all users and there is no out-of-the-box logic that allows you customizing the gauge dashboard in the way you've described. As a solution of your case you can try to create your own custom widget via additional development (this Academy article will be useful: https://academy.creatio.com/documents/technic-sdk/7-16/adding-custom-dashboard-widget). And in the following article you can find information about how to configure the “Gauge” dashboard in general: https://academy.creatio.com/documents/base/7-16/gauge-dashboard-tile

Also, you can check marketplace application which are related to dashboards and possibly you will be able to find some tools that will resolve your business task.

For example, if you need using formulas in a dashboard - this marketplace app provides this functionality: https://marketplace.creatio.com/app/calculated-charts-creatio

Advanced dashboard designer will help to design your dashboards in easier way: https://marketplace.creatio.com/app/advanced-dashboard-designer

Best regards,

Roman

Dear,

The issue happened due to the incorrect using of the file development mode for working with the server side source code.

Please find the information about how to do it propery in the article by the link below:

https://academy.creatio.com/documents/technic-sdk/7-16/overview

Best regards,

Norton

Hi Allen, 

Sure, there is an option to block such functionality. However, please note that the development process should be applied.

1. Firstly, you need to create a replacing client module schema for the "FileDetailV2" client module. Please find the information about it in the article by the link below:

https://academy.creatio.com/documents/technic-sdk/7-16/creating-custom-client-module-schema

2. In a new replacing client schema, please insert the code below:

define("FileDetailV2", [],
	function(ViewUtilities, ConfigurationConstants, ConfigurationEnums, RightUtilities, DefaultProfileHelper) {
	return {
		methods: {
			/**
			 * ########## ######## ########### ###### ############## ######.
			 * @return {Array} ######## ########### ###### ############## ######.
			 */
			generateButtonMenuItems: function() {
				let itemsConfig = this.callParent();
				const itemsConfigUpdated = (itemsConfig = []);
 
				return itemsConfigUpdated;
		},
	}};
});

3. Save the changes and hard-reload the page.

Regards,

Anastasiia

Anastasiia Markina,

Why would you still want to call the parent method? Wouldn't it make more sense to just re-write the method to just return an empty array? e.g.:

define("FileDetailV2", [],
	function() {
	return {
		methods: {
			/**
			 * ########## ######## ########### ###### ############## ######.
			 * @return {Array} ######## ########### ###### ############## ######.
			 */
			generateButtonMenuItems: function() {
				return [];
		},
	}};
});

Hi Harvey, 

Sure, such a solution is appropriate, too. However, it's always better to use this.callParent method to avoid any issues through future updates. 

Thus, this.callParent calls the parent method firstly instead of re-writing or breaking its logic, so this is a safer approach for a client module schema replacement.

Regards,

Anastasiia

Hello Community,



Can someone help with this? Need to be able to locate where & how the changes are stored. We need to be able to migrate changes from an earlier legacy system to this change log. 

For table Activity try checking ActivityLog or SysActivityLog. I found it to be TablenameLog in my system.

Dear Thanh,

Currently, Creatio uses same schema code for all mini pages, so modifying "View Mode" will lead to changes in other modes. Our developers know that some users want to have different views and are working on implementing this task in future releases. 

Best regards,

Angela

Dear Akshit,

Unfortunately, there is no such functionality in the application. Please note that we have notified the development team about your request.

Best regards,

Norton

Hi Marcin,



To set the model to learn prediction based on similar customers purchases you should add the following columns to the query:



Id (just an identifier)

user_id (a user)

item_id (something purchased by the user)

value (how much did the user purchase, but you can leave it 1 if it's important to see the fact of a purchase)



You should add those values to additional metadata as it is shown here:

https://academy.creatio.com/documents/technic-sdk/7-16/how-implement-custom-prediction-model

You can find more information regarding queries here:

https://academy.creatio.com/documents/technic-sdk/7-16/creating-data-queries-machine-learning-model?document=administration



Unfortunately, we don't have a separate article regarding this type of ML model (Recommendation).



Thank you.

Bohdan Zdor,

Thank You for explanation. To better understand this tool please clarify me some concerns:

Is this “advanced tools to add columns” overrides basic training data set resulting from “Recommendation dependency” query or this is additional data which are corellared with basic query ?

I mean .. “Query for selecting additional training data”, “Query metadata for selecting additional training data”.

I yes, then what is principle to building additional select ("new Select") to maintain relation between 2 queries (basic and advanced) ? Eg. that selected object should be the same (“Recommendation dependency” = "select .. From x"), what else ?

“Query metadata for selecting additional training data” – In posted documentation

https://academy.creatio.com/documents/technic-sdk/7-16/how-implement-custom-prediction-model?_ga=2.41994279.328510928.1596630980-1487324197.1596630446

additional columns are set:

{

    "inputs": [

        {

            Id

        },

        {

           attr1

        },

        {

           attr2

        }

    ],

    "output": {

        attr3

    }

}

In recommendation case in "inputs" tag i may add Id and eg. Account Country, Account Category ??

What I have to add then in "output" tag ?

In Your example I understood that as a input I have to add

Id -> Object Id

user_id -> Account Id

item_id -> Product Id

value  -> Quantity

when eg. Query data set is a “Product in Quote”, right ?

Regards,

Marcin

Marcin Kott,

Advanced parameters are merged with parameters that are formed by standard tools and as a result are formed one common set of parameters. Moreover, in the advanced settings, you can also specify additional filtering parameters.

For recommendation models, no "additional" parameters need to be passed, since the models are trained on transaction data, or any other interaction of the client with the product, for example, the product in the order. The model will not accept any other parameters.

Extended selection is needed for these models, for example, in order to combine data on purchases of goods and views of goods on the site. Then a selection is written that somehow aggregates this data, but as a result, it is necessary to still get a selection of the type - client, product, number.

In recommendation case in "inputs" tag i may add Id and eg. Account Country, Account Category ? - It is impossible to divide this way, since the selection should contain only Id (just an identifier)

user_id (a user)

item_id (something purchased by the user)

value

Finally, there are actually two options for recommendations – selection by standard tools or completely form it using a custom query.

Best regards,

Norton

Hi Ankit,

Pivot tables were developed using angular in our system and connected to the app as custom element and use shadow dom for styles encapsulation. And the screenshot cannot be done because of the shadow dom. Screenshot is performed using html2canvas library and it has an issue on GitHub https://github.com/niklasvh/html2canvas/issues/430. We tried updating the html2canvas library to the latest version but the error still reproduces and we are now working on developing our own rendering. So as for now there is no workaround for this problem, but using third-party screenshot tools.

Best regards,

Oscar

Hi Allen, 

In order to remove "Select multiple records", "Apply filter", "Sort by" you can do the following: 

1. Create a replacing client module schema for the detail schema. Here is the article on how you can do it:

https://academy.creatio.com/documents/technic-sdk/7-16/creating-custom-…

2. In a replaced client schema, please override method addGridOperationsMenuItems as in the example below:

define("UsrSchemac2207388Detail", [], function() {
  return {
    entitySchemaName: "UsrPets",
    details: /SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
    diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/,
    methods: {
      addGridOperationsMenuItems: function(toolsButtonMenu) {
        const switchGridModeMenuItem = this.getSwitchGridModeMenuItem();
        if (!switchGridModeMenuItem) {
          toolsButtonMenu.addItem(this.getButtonMenuSeparator());
          toolsButtonMenu.addItem(switchGridModeMenuItem);
        }
        const exportToExcelMenuItem = this.getExportToExcelFileMenuItem();
        if (exportToExcelMenuItem) {
          toolsButtonMenu.addItem(exportToExcelMenuItem);
        }
        const fileImportMenuItem = this.getDataImportMenuItem();
        if (fileImportMenuItem) {
          toolsButtonMenu.add("FileImportMenuItem", fileImportMenuItem);
        }
        Terrasoft.each([
          this.getGridSettingsMenuItem(),
          this.getRecordChangeLogMenuItem(),
          this.getObjectChangeLogSettingsMenuItem()
        ], function(buttonConfig) {
          if (buttonConfig) {
            toolsButtonMenu.addItem(this.getButtonMenuSeparator());
            toolsButtonMenu.addItem(buttonConfig);
          }
        }, this);
      },
    },
  };
});

If you want to do that in all details you can override BaseGridDetailV2 and override the method in the same way. 

Best regards, 

Anastasiia

Hello,

Such an option is not available for fault-tolerant installation. 

Fault-tolerant architecture implies that when one node fails, users will be able to work with the neighbouring one. If two neighbouring nodes are different, then this is no longer a fault-tolerant architecture, but two different applications.

Best regards,

Angela