This marketplace addon will remove it

https://marketplace.creatio.com/template/agent-desktop-without-feed-area

Ryan

Ryan Farley,

It worked, thank you very much!

Hello Sandra,

There is no OOB tool that can help you to achieve your business task but you can do some inserts via SQL tools. The table that you need is called 'SysProfileData' and the Key that you need is called 'Section-Account-MainGrid-Summary'. So having this information you can do the insert for some specific Contacts in the system.

This may help: https://community.creatio.com/questions/hide-section-button-edit-page

First of all, rather than using operation: remove, change that to operation: merge, which will let you modify the properties of the element. Then, you'll bind the visible property of them to an attribute. To show or hide them, you'll set the attribute to true or false. See this article here for more details: https://customerfx.com/article/how-to-enable-or-disable-a-field-on-a-pa…

Also, to set the attribute to true or false, you'll either need to add that to a change event for whatever fields use the conditions or when the page opens, using the onEntityInitialized function. To base it on the selection of fields, you can wire a change event as shown here: https://customerfx.com/article/triggering-an-event-when-a-field-is-chan…

Info on the onEntityInitialized function and other basic info on working with page code here: https://customerfx.com/article/getting-started-with-writing-code-for-bp…

Hope this helps get you started.

Ryan

You can do this using the sandbox. See https://academy.creatio.com/docs/developer/front_end_development/sandbo…

Basically, if detail1 needs to call a function defined in detail2, in detail1 you'd define a message with mode PTP and direction PUBLISH. In detail2, you'd define the same message with mode PTP and direction SUBSCRIBE. Detail1 would publish the message via the sandbox when it wants to invoke the function in the other detail. Then in detail2, when the message is received, it would execute the function. 

Hope this helps get you started. Here's a sample from an older post of sending messages between details: https://community.creatio.com/articles/implementing-messages-sandbox-de…

Ryan

Dear Gareth, 



The logic behind this behavior is that when any changes comes in the package they should not be directly changed since packages can be distributed by third-party publishers. 

Only way to change functionality installed is to re-define the code or add new methods within the new replacing module in your custom packages. 



Kind regards,

Roman

 

Dear Anu, 



Can you please specify with more details on how exactly would you like to trigger the process? 



Thank you. 

Anu, Roman Brown,



Here is the Academy article to call the BP (Business Process) from the Action items menu.

https://academy.creatio.com/docs/developer/integrations_and_api/busines…

 

Sample,

 

define("AccountPageV2", ["ProcessModuleUtilities"], function(ProcessModuleUtilities) {
    return {
        entitySchemaName: "Account",
        methods: {
            // Проверяет, заполнено ли поле [Основной контакт] страницы.
            isAccountPrimaryContactSet: function() {
                return this.get("PrimaryContact") ? true : false;
            },
            // Переопределение базового виртуального метода, возвращающего коллекцию действий страницы редактирования.
            getActions: function() {
                var actionMenuItems = this.callParent(arguments);
                actionMenuItems.addItem(this.getActionsMenuItem({
                    Type: "Terrasoft.MenuSeparator",
                    Caption: ""
                }));
                actionMenuItems.addItem(this.getActionsMenuItem({
                    "Caption": { bindTo: "Resources.Strings.CallProcessCaption" },
                    "Tag": "callCustomProcess"                
                }));
                return actionMenuItems;
            },
            // call you porcess
            callCustomProcess: function() {
                var contactParameter = this.get("PrimaryContact");
                var args = {
                    // Process name
                    sysProcessName: "UsrCustomProcess",
                    // parameters process
                    parameters: {
                        ProcessSchemaContactParameter: contactParameter.value
                    }
                };
                // run process
                ProcessModuleUtilities.executeProcess(args);
            }
        }
    };
});

BR,

Bhoobalan Palanivelu

Hello Frederico,

I have the steps written up to override a module here: https://customerfx.com/article/overriding-modules-in-creatio-formerly-bpmonline/

Ryan

Ryan Farley,

Thanks Rayan. Regards,

Hello Frederico,

Hope you're doing well.

Thanking Ryan for creating and sharing the useful article. We can confirm that the steps described in the mentioned instruction can be used for overriding the needed module.

At the same time, we don't recommend this way because in the case when you have more than 2 overriding modules, it will not work properly or won't work at all.

Best regards,

Roman

Roman Rak,

Since you don't recommend this way, may I know any other way to do this?



Regards,

Solem.

Hello Ramnath,

rootEntitySchemaName is the name of the parent object. This is likely the object for the page where the detail is located, so if the detail is on the Account page, this would be Account

rootColumnName is the name of the column on the detail object that relates it to the parent object. In the example of being on the Account page, this would be the name of the column on the detail object that is the account lookup, such as UsrAccount

relatedEntitySchemaName is the name of the object you're looking up to add to the detail. So, if the lookup is looking up contacts, this would be Contact

relatedColumnName is the name of the column on the detail object that the result from the lookup is stored in. So in the example of looking up contacts, this would be a contact lookup on the detail object, such as UsrContact.

Maybe this article will help? https://customerfx.com/article/adding-to-a-detail-from-a-lookup-in-crea…

Ryan

Ryan,

Thanks for helping me out.

Please guide me in this situation more.

Overview of whole scenario

I created a custom detail in a custom section.  I have created a Section Contacts (neither base object nor replacing object, It is custom made) and Clients Section. Clients section has a detail Contacts. The detail's object name is the Contacts section.

Section Page - UsrClients

Detail object - UsrContacts (has lookup of UsrClient for connecting record to UsrClients with other inherited columns present in UsrContacts)

Now the name will be

rootEntitySchemaName - UsrClients (section page object name)

rootColumnName - UsrClient  (the referencing lookup present in UsrContacts)

relatedEntitySchemaName - UsrContacts (Section page from where records will be read)

relatedColumnName - UsrContact (lookup present in detail)

Now the problem is how can I create a lookup pointing to the same object on which detail is build.

Lookup points to UsrContacts and detail is also created on UsrContacts.

RAMNATH SHARMA,

The detail should be a separate object. Like in the example on the academy, OpportunityContact object on which the detail is built on contains Opportunity and Contact columns. In your case, you would need to create a separate object for the detail that would contain UsrClients and UscrContacts columns, and build the detail on this object. 

Dennis Hudson,

Yes, you are right. I have created a new object with 2 looks fields to add this functionality. And it works.

Thanks

Please create a replacing client module for the OpportunityMiniPage schema. Then remove the fields which aren't needed in the diff block in the newly created replacing client module. Please feel free to use the example below. Note that the isRequired property of the LeadType attribute must be set to false.

define("OpportunityMiniPage", [],

        function() {

    return {

        entitySchemaName: "Opportunity",

        mixins: {

        },

        attributes: {

            "LeadType": {"isRequired": false}

        },

        methods: {

        

        },

        diff: /**SCHEMA_DIFF*/[

            {

                "operation": "remove",

                "name": "LeadType"

            },

            

        ]/**SCHEMA_DIFF*/

    };

});

 

Hi!

In order to override the CampaignConnectorManager module you can create a new module and use "override" as it showed on the screenshot by the link below 

http://prntscr.com/o1pibh



In order to activate the newly created module, you need to define it according to the documentation by the link below.

https://requirejs.org/

Best regards,

Angela