Dear Allen,

Thank you for your question!

The best way to accomplish the restrictions to add new records to a lookup without development would be to update the Object Permissions.

Navigate to the [Object Permissions], find there the required lookup, and disable the "Create" option for "All employees" (or for a different group if you are using them):

And save. Make sure to "Update the record permissions" in the Action drop-down menu.

The result would be like in the screenshot below:

 Hope this helps!

Thank you, hope you have a great day!

Regards,

Danyil

Danyil Onoprienko,

Thank you for the suggestion! Due to some complex security setup in the system, we are considering using code disable/hide the "NEW" option on the lookup. Is there a way to do this?

Hi Allen Dsouza,

 

This button is displayed if the Lookup has an edit page. If we are talking about a selection card from a lookup, the "getSelectionControlsConfig" method in the "LookupPageViewGenerator" schema is responsible for loading the list of edit pages.

 

There is no instruction, but the "BaseLookupPageV2" schema is responsible for this page \ window, the "Add" button name is: "SeparateModeAddRecordButton", the "ActionsButton" - it's action button. You can replace and customize the visibility of these buttons as you need.

 

P.S. If you have an option to hide it without using code, I'm suggesting you to do it, just by changing "Lookup view" from "Selection window" to "List" and there will be no option to add "New" City/State. (Example attached below)







Best Regards, 



Bogdan L.

Hello,

It is ActivityMiniPage of UIv2 package. You need to re-define the insert operation of CancelButton

Regards,

Dean

dean parrett, Thank you very much for your answer! It works as intended.

Cheers from Mexico

Dear Patrice,

Try to follow this guide on how to add a custom object to the timeline

https://academy.creatio.com/documents/technic-sdk/7-13/timeline-tab

Regards,

Dean

Hello Dean,

thanks for the answer.

In my case, i use 7-17 so i went to https://academy.creatio.com/documents/technic-sdk/7-16/introduction-17



So in AccountPageV2's TimelinePageSetting, i changed the original data, from 

          {

            "entityConfigKey": "0ef5bd15-f3d3-4673-8af7-f2e61bc44cf0",

            "entitySchemaName": "Order",

            "referenceColumnName": "Account",

            "masterRecordColumnName": "Id"

          },

to

          {

            "entityConfigKey": "9843b156-452f-463c-8cb6-7e9b3e3d5499",

            "entitySchemaName": "Order",

            "referenceColumnName": "Account",

            "masterRecordColumnName": "Id"

          },



which hold my new TimelineTileSetting Id.

is it not supposed to work like that ?



am i supposed to add a whole new TimelinePageSetting for my AccountPageV2 section like described in documentation ? or can i modify the existing one ?



Regards,

Patrice

Dear Dick,

Thank you for your question!

The best solution for this would be using a Business Process with parameters.

Hope this helps!

Regards,

Danyil

Dear Kavian,



If you do not wish to go with Operation Permissions, you can debug onDelete method logic in GridUtilitiesV2 schema.

You need to replace it with your own custom logic.

Unfortunately, your business task can be performed using our base tools.



Best Regards,

Ivanna

Ivanna Yatsura,

Thanks. But not even by using "Record permissions"? 

In the picture below, doesn't it mean that each employee can delete the record that they created?

Kavian Abhari,

Yes, you are correct, you can use this.

And if you remove everything from the Record Permissions, by default all rights will be given to the person, who creates the record and System Administrator.

Also, you will need to create a business process to give read/edit rights to all other users as they will not be able to perform these actions using the logic above.

I'm sorry if I misunderstood you, I thought that you do not wish to use Permissions at all.

You can check this article for more information:



https://academy.creatio.com/docs/user/setup_and_administration/user_and…



Best Regards,

Ivanna

Bumping this

Hi Julius,

I recommend double-checking the following parameters: mainEntitySchemaName, mainColumnName, and relatedColumnName. They all are responsible for data storage.

Also, could you please provide a screenshot of the settings for the 'ChessContactInterest' object with added fields? This would help investigate the issue further.

Alexander Demidov,

Alexander Demidov,

I managed to solve it.

        getMultiChoiceEntitiesConfig: function () {
          const items = {
            ChessInterests: {
              mainEntitySchemaName: "ChessContactInterest",
              mainColumnName: "ChessContact",
              relatedEntitySchemaName: "ChessContactInterest",
              relatedColumnName: "ChessInterest"
            }
          };

Now my next issue is that I don't have a Displayed Value on my link-object (ChessContactInterestChess). I can't select one in the drop-down

Fixed it with another one. Last one was wrong

              mainEntitySchemaName: "ChessContactInterest",
              mainColumnName: "ChessContact",
              relatedEntitySchemaName: "ChessInterest",
              relatedColumnName: "ChessInterest"

Explanation as I understand it:

mainEntitySchemaName: "My Link Table",
mainColumnName: "Property in Link table matching current record Id (In my case ContactId)", 
relatedEntitySchemaName: "Object to select", 
relatedColumnName: "Objects column name in Link table"

Hi Julius,

It's great to hear that you resolved these issues! We will add your findings to the app description to help streamline the field setup.

Hi,

I get this problem too, that values are not being saved.

I checked the above elements and they are good!

What else can cause that issue?

I managed to solve it.

I deleted the name field that was automatically created when I create the object through the detail wizard. It's required and probably that couldn't be save missing that field.

Hello. I'm working with the Multiple choice field setup for Creatio (https://marketplace.creatio.com/app/multiple-choice-field-setup-creatio) add-on but I'm not getting it to save the selected values.

I've followed the guide here: https://marketplace.creatio.com/sites/marketplace/files/app-guide/Multi…

I get the values correctly on the page, and they are selectable. But nothing is saved to the database when i Save the record

Object: UsrContactLabels

Lookup: UsrLabels

Link-object: UsrContact

Hello Vincent,

Hope you're doing well.

To be able to add or modify relationships via business process please use the object Relationship. It contains a connection for both contacts and accounts and can be used for adding any possible relations between those objects.

Also, the links below can be useful for further working with relationships:

• https://academy.creatio.com/docs/node/1768?_ga=2.96795103.1776048178.16…
• https://community.creatio.com/questions/adding-new-relationship-connect…
• https://community.creatio.com/questions/setup-columns-view-relationships
• https://community.creatio.com/questions/relationship-detail

Best regards,

Roman

HI Kavian,

Yes, it's possible. Here are the steps;

1) Add a "Completeness" field into your section object. This one should be an integer.

2) Add a record about your section into the "Completeness" table. You can do it with the following SQL script:

INSERT INTO Completeness (Name, EntitySchemaName, ResultColumnName, Scale)
    VALUES ('Quotes', 'VistQuotes', 'VistCompleteness', '{"sectorsBounds":{"min":0,"middleFrom":50,"middleTo":80,"max":100}}')

You should specify Name, EntitySchemaName, ResultColumnName and Scale columns.

3) Create replacing client module for your page (for example VistQuotes1Page in my case).

4) Add dependencies on following schemas: "CompletenessIndicator", "CompletenessMixin", "css!CompletenessCSSV2", "TooltipUtilities".

5) Add two attributes into the "attributes" area:

CompletenessValue: {
    dataValueType: Terrasoft.DataValueType.INTEGER,
    value: 0
},
MissingParametersCollection: {
    dataValueType: Terrasoft.DataValueType.COLLECTION
}

6) Add two mixins (CompletenessMixin, TooltipUtilitiesMixin) into your schema.

mixins: {
    CompletenessMixin: "Terrasoft.CompletenessMixin",
    TooltipUtilitiesMixin: "Terrasoft.TooltipUtilities"
},

7) Add the following methods:

methods: {
    init: function() {
        this.set("MissingParametersCollection", this.Ext.create("Terrasoft.BaseViewModelCollection"));
        this.callParent(arguments);
    },
    onDetailChanged: function() {
        this.callParent(arguments);
        this.calculateCompleteness();
    },
    onEntityInitialized: function() {
        this.callParent(arguments);
        if (this.isEditMode()) {
            var collection = this.get("MissingParametersCollection");
            collection.clear();
            this.set("CompletenessValue", 0);
            this.calculateCompleteness();
        }
    },
    onSaved: function() {
        var callParentOnSaved = this.get("CallParentOnSaved");
        this.callParent(arguments);
        if (!callParentOnSaved && !this.isNewMode() && !this.get("IsProcessMode")) {
            this.calculateCompleteness();
        }
    },
    calculateCompleteness: function() {
        var config = {
            recordId: this.get("Id"),
            schemaName: this.entitySchemaName
        };
        this.mixins.CompletenessMixin.getCompleteness.call(this, config, this.calculateCompletenessResponce, this);
    },
    calculateCompletenessResponce: function(completenessResponce) {
        if (this.Ext.isEmpty(completenessResponce)) {
            return;
        }
        var missingParametersCollection = completenessResponce.missingParametersCollection;
        var completeness = completenessResponce.completenessValue;
        var scale = completenessResponce.scale;
        if (!this.Ext.isEmpty(missingParametersCollection)) {
            var collection = this.get("MissingParametersCollection");
            collection.clear();
            collection.loadAll(missingParametersCollection);
        }
        if (this.Ext.isObject(scale) && this.Ext.isArray(scale.sectorsBounds)) {
            this.set("CompletenessSectorsBounds", scale.sectorsBounds);
        }
        if (this.Ext.isNumber(completeness)) {
            this.set("CompletenessValue", completeness);
        }
    }
},

8) Insert completeness bar into your page with code like following:

diff: /**SCHEMA_DIFF*/[
    {
        "operation": "insert",
        "parentName": "MetricsContainer",
        "propertyName": "items",
        "name": "CompletenessContainer",
        "values": {
            "itemType": Terrasoft.ViewItemType.CONTAINER,
            "items": []
        }
    },
    {
        "operation": "insert",
        "parentName": "CompletenessContainer",
        "propertyName": "items",
        "name": "CompletenessValue",
        "values": {
            "generator": "ConfigurationRectProgressBarGenerator.generateProgressBar",
            "controlConfig": {
                "value": {
                    "bindTo": "CompletenessValue"
                },
                "menu": {
                    "items": {
                        "bindTo": "MissingParametersCollection"
                    }
                },
                "sectorsBounds": {
                    "bindTo": "CompletenessSectorsBounds"
                }
            },
            "tips": [],
            "layout": {
                "column": 0,
                "row": 0,
                "rowSpan": 1,
                "colSpan": 1
            }
        }
    },
    {
        "operation": "insert",
        "parentName": "CompletenessValue",
        "propertyName": "tips",
        "name": "CompletenessTip",
        "values": {
            "content": {"bindTo": "Resources.Strings.CompletenessHint"}
        }
    }
]/**SCHEMA_DIFF*/

A full example of code can be found below:

define("VistQuotes1Page", ["CompletenessIndicator", "CompletenessMixin", "css!CompletenessCSSV2", "TooltipUtilities"],
    function() {
    return {
        entitySchemaName: "VistQuotes",
        attributes: {
            CompletenessValue: {
                dataValueType: Terrasoft.DataValueType.INTEGER,
                value: 0
            },
            MissingParametersCollection: {
                dataValueType: Terrasoft.DataValueType.COLLECTION
            }
        },
        modules: /**SCHEMA_MODULES*/{}/**SCHEMA_MODULES*/,
        details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
        businessRules: /**SCHEMA_BUSINESS_RULES*/{}/**SCHEMA_BUSINESS_RULES*/,
        methods: {
            init: function() {
                this.set("MissingParametersCollection", this.Ext.create("Terrasoft.BaseViewModelCollection"));
                this.callParent(arguments);
            },
            onDetailChanged: function() {
                this.callParent(arguments);
                this.calculateCompleteness();
            },
            onEntityInitialized: function() {
                this.callParent(arguments);
                if (this.isEditMode()) {
                    var collection = this.get("MissingParametersCollection");
                    collection.clear();
                    this.set("CompletenessValue", 0);
                    this.calculateCompleteness();
                }
            },
            onSaved: function() {
                var callParentOnSaved = this.get("CallParentOnSaved");
                this.callParent(arguments);
                if (!callParentOnSaved && !this.isNewMode() && !this.get("IsProcessMode")) {
                    this.calculateCompleteness();
                }
            },
            calculateCompleteness: function() {
                var config = {
                    recordId: this.get("Id"),
                    schemaName: this.entitySchemaName
                };
                this.mixins.CompletenessMixin.getCompleteness.call(this, config, this.calculateCompletenessResponce, this);
            },
            calculateCompletenessResponce: function(completenessResponce) {
                if (this.Ext.isEmpty(completenessResponce)) {
                    return;
                }
                var missingParametersCollection = completenessResponce.missingParametersCollection;
                var completeness = completenessResponce.completenessValue;
                var scale = completenessResponce.scale;
                if (!this.Ext.isEmpty(missingParametersCollection)) {
                    var collection = this.get("MissingParametersCollection");
                    collection.clear();
                    collection.loadAll(missingParametersCollection);
                }
                if (this.Ext.isObject(scale) && this.Ext.isArray(scale.sectorsBounds)) {
                    this.set("CompletenessSectorsBounds", scale.sectorsBounds);
                }
                if (this.Ext.isNumber(completeness)) {
                    this.set("CompletenessValue", completeness);
                }
            }
        },
        mixins: {
            CompletenessMixin: "Terrasoft.CompletenessMixin",
            TooltipUtilitiesMixin: "Terrasoft.TooltipUtilities"
        },
        dataModels: /**SCHEMA_DATA_MODELS*/{}/**SCHEMA_DATA_MODELS*/,
        diff: /**SCHEMA_DIFF*/[
            {
                "operation": "insert",
                "parentName": "MetricsContainer",
                "propertyName": "items",
                "name": "CompletenessContainer",
                "values": {
                    "itemType": Terrasoft.ViewItemType.CONTAINER,
                    "items": []
                }
            },
            {
                "operation": "insert",
                "parentName": "CompletenessContainer",
                "propertyName": "items",
                "name": "CompletenessValue",
                "values": {
                    "generator": "ConfigurationRectProgressBarGenerator.generateProgressBar",
                    "controlConfig": {
                        "value": {
                            "bindTo": "CompletenessValue"
                        },
                        "menu": {
                            "items": {
                                "bindTo": "MissingParametersCollection"
                            }
                        },
                        "sectorsBounds": {
                            "bindTo": "CompletenessSectorsBounds"
                        }
                    },
                    "tips": [],
                    "layout": {
                        "column": 0,
                        "row": 0,
                        "rowSpan": 1,
                        "colSpan": 1
                    }
                }
            },
            {
                "operation": "insert",
                "parentName": "CompletenessValue",
                "propertyName": "tips",
                "name": "CompletenessTip",
                "values": {
                    "content": {"bindTo": "Resources.Strings.CompletenessHint"}
                }
            },
            {
                "operation": "insert",
                "name": "VistStatusa33f682a-dd58-4739-919d-cb84b9d2fc70",
                "values": {
                    "layout": {
                        "colSpan": 12,
                        "rowSpan": 1,
                        "column": 12,
                        "row": 10,
                        "layoutName": "Header"
                    },
                    "bindTo": "VistStatus",
                    "enabled": true
                },
                "parentName": "Header",
                "propertyName": "items",
                "index": 46
            }
        ]/**SCHEMA_DIFF*/
    };
});

Best regards,

Oscar

Oscar Dylan,

Thanks, is it possible to define negative values? For example, if Lead Contact unsubscribe from a Marketing Campaign, a boolean would be triggered and therefore it will reset the data entry compliance to 0.

Thanks,

Hi Kavian Abhari,

Please try to use this code.

onEntityInitialized: function() {

      var IsUnsubscribed = true;

        this.callParent(arguments);

        if (this.isEditMode()) {

            var collection = this.get("MissingParametersCollection");

            collection.clear();

          this.set("CompletenessValue", 0);

          if(this.get("IsUnsubscribed") == true){

          return;

          } else

          this.calculateCompleteness();

        }

    },





P.S. "IsUnsubscribed" - this is my example of your boolean variable that sets the unsubscribe logic.



Best Regards, 



Bogdan L.

Dear Mark,

For now, distribution group mailboxes are not supported on our platform. I will ask our developers to take into consideration your post and add this functionality in future releases. 

Best regards,

Angela

Angela Reyes,

Hi Angela

Firstly, thank you for your reply.

Are you able to provide guidance on the method to utilise an O365 non-user account as the email account used to send such notification mails? It is really annoying for a user to see so many 'system' mails in their Sent items, when this is something a service account should be configured to use. 

Obviously I would rather not pay for an O365 license just for this function.

Mark Roberts,

For now, we can only suggest using a shared mailbox for such emails or use an additional mailbox. 

Best regards,

Angela

Hi Julio,

This app only supports .docx printables, therefore the 'Convert to PDF' parameter must always be 'False'.

Here is how the correctly set up element should look like:

Thank you for your questions. We will mention that the app only supports .docx printables in its description.

Thanks Ivan, the image looks broken, could you upload again, please?

Ivan Leontiev,

Is also there any way to a new release that consider FastReport reports?