Dear Mitch,

In order to implement the required functionality please do the following:

1. Create a replacing client module for the “OpportunityPageV2” schema. Please find more 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. Add the following code to the schema:

define("OpportunityPageV2", [], function(){

    return {

        attributes: {

            "Client": {

                    "multiLookupColumns": ["Account"]

            }

        }    

    };    

});

3. Save the schema and enjoy the result:

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 Mitch,

It seems that you have added custom section by development tools, but not via out-of-the-box tools like Section Wizard. For example, I have created new section via standard tools and was able to choose custom section in the process settings:

unfortunately, at the moment there is no possibility to choose the Section/Page implemented by development in the Open Edit Page business process element. You can find more information about Open edit page element in the following link:

https://academy.creatio.com/documents/technic-bpms/7-16/open-edit-page-process-element

As a workaround we suggest try to use Pre-configured page element and set code of the edit page created using section designer in "Source code" of pre-configured page settings:

More detailed information about Pre-configured page element in the next link:

https://academy.creatio.com/documents/technic-bpms/7-16/pre-configured-page-process-element

Best regards,

Roman

Roman Rak,

Is there a way to get the edit page to automatically open for the user instead of the user needing to click on the business process task?

Dear Mitch,

Please double check the signal element. Most likely it has active "Run the following element in the background" checkbox. It sets the whole process to the background and that's why the page is not getting opened automatically.

Apart from that, please disable the debug mode. It can influence the proper page loading.

Regards,

Dean

Dear Allen, 

You can do it by extending or overriding class Terrasoft.Grid (you can find it in the web console, you won't be able to find it in configuration) and changing the method formatCellContent to call formatCellLink, forming the link in a way that it would call the needed service with needed parameters when you need it to do so. You can debug method formatCellContent and see how it works in OOB version and create your own based on that. Unfortunately, we don't have examples of such implementation. 

Please see the following articles on how to override modules: 

https://community.creatio.com/questions/substitutionreplacing-modules

https://community.creatio.com/questions/change-task-displayed-fields

Best regards, 

Dennis 

Dear Harvey, 



This part of the code is needed for the correct work of multi-select in the grid of the detail. I would not recommend removing it as various issues with multi-select may occur. 

Best regards, 

Dennis 

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

Hi Akshit, 

Thank you for contacting us!

The link below contains client core library where you are welcome to check BasePage schema methods described:

https://academy.creatio.com/api/jscoreapi/7.15.0/index.html

Best regards,

Anastasiia

Dear Mitch,

You can use SupplyPaymentDetailV2 as an example of how such functionality can be implemented (for example methods linkClicked and "useLinks").

Best regards,

Angela

Hi, I have the same need.

If the process is triggered just BEFORE he record is actually deleted, It could be possible... but I am not sure...

An alternative is to use a "delete" button that actually does not delete the record, but triggers a process instead. This process then does all the cleanup needed, and eventually deletes the record...

Hello Mitch, 



Unfortunately, there is no possibility of using the information from the record deleted to trigger the business process signal.  

This is the known issue when the process created upon deleting some object cannot use the information from the deleted object in it's further elements in the flow.



However, If you want to have process triggered before the record deletion please check this community article: https://community.creatio.com/questions/deleting-process 



Kind regards,

Roman