Hello Federico, 

We performed some tests in order to achieve your requirement, but it seems like such implementation is not possible for now. The only one business rule will be active in this case. We already informed our Core R&D team and we will work to add such functionality in our next releases. Thank you for understanding!

Best Regards, 

Bogdan L.

Hello,

You need to create a separate module and then add it to the mobile application manifest (PagesExtensions property of the object model) as described here or here. In this community post, I've provided an example of a business rule that activates a field based on conditions.

Best regards,

Oscar

Thanks Oscar,

I have got it working.

Hello,

I also applied same business rule for a string which needs to be permanently read-only in Order section. So, I have put in the condition column Total amount as negative which will never be true. But, this is not working in mobile.

I have attached that business rule below. I have added this module in the page extensions of Order section also.

Terrasoft.sdk.Model.addBusinessRule("Order", {

    ruleType: Terrasoft.RuleTypes.Activation,

    events: [Terrasoft.BusinessRuleEvents.Load, Terrasoft.BusinessRuleEvents.ValueChanged],

    triggeredByColumns: ["JFLOrderOneOffTotal" ],

    conditionalColumns: [

       

      {name: "JFLOrderOneOffTotal", value: "-1.00"} 

    ],

    dependentColumnNames: ["JFLPaymentMandateLink"]

});

I want to make "JFLPaymentMandateLink" field read only.

Hoping for an early reply.

malay garg,

Hello,

You need to install the emulator to debug the logic (can be found here). You need to check which value if passed for the JFLOrderOneOffTotal column and if the rule is triggered. Also you will need to recycle the application pool after creating a new rule and adding it to the page extensions in the manifest.

Best regards,

Oscar

Oscar Dylan,

Thanks for the information.

I am looking for a logic to make a Date, String, Integer field read only in mobile.

The column JFLOrderOneOffTotal was chosen because it can never be negative in my implementation, so the affected field would be always read only. 

But, as this is not working , can you please suggest me proper logic to make these fields read only always.

Hoping for an early reply.

Regards,

Malay.

Malay,

You are welcome!

Yes, you can do it! See the example of my business rule below:

Terrasoft.sdk.Model.addBusinessRule("Account", {
    ruleType: Terrasoft.RuleTypes.Activation,
    events: [Terrasoft.BusinessRuleEvents.Load, Terrasoft.BusinessRuleEvents.ValueChanged],
    triggeredByColumns: ["UsrInteger"],
    conditionalColumns: [
        {name: "UsrInteger", value: 1}
    ],
    dependentColumnNames: ["UsrWaranty","UsrDate","UsrDelivery"]
});

Please note that the business rule name should be the same as the object for which the rule is created (not the module name, but the rule name ("Account" in my case, one of the arguments for the Terrasoft.sdk.Model.addBusinessRule method)). The module itself can have any name you want (in my case it is "UsrAccountReadOnly" that was then added to the manifest:

).

As a result all three columns became read-only: UsrWaranty - integer column, "UsrDate" - date column and "UsrDelivery" - string column:

The condition is that columns become unlocked when the UsrInteger column value is 1. Once this rule was created and the application pool restarted and relogin to the mobile app executed the rule started to work as expected. So you need to double-check your rule.

Best regards,

Oscar

Dear Amritha,

For such a task, you may create a business rule for each field and each stage - then when the stage is changed new set of rules will start working. Otherwise, you can add business rules to the source code for each field: https://academy.creatio.com/docs/developer/front-end_development/creati…

Best regards,

Angela

Dear Angela,

While creating the fields have given only read access to all the fields. Later in the business rule for a stage, where the fields needs to be edited have given editable option via business rule. But there is no option that for other fields to give  uneditable option in business rule, we havent given that instead provided read only option.

But still, in the initial stage based on the rule few fields are editable and when the stage changes. When we create a new detail then that stage business rules gets applied but to already created detail the business rule for that stage is not getting applied, that is our concern

Amritha Mayan Gorky,

So you mean when detail is moved to another stage old records are still read-only and new records are edible while in fact, all records should be editable? 

 Dear Julio,



Unfortunately, it is not possible to implement this logic through Business rules as we cannot create business rule for contacts in accounts.



The solution here will be to build the described filter using EntitySchemaQuery.

Here is the article - https://academy.creatio.com/docs/developer/back-end_development/working…



Best Regards,

Ivanna

Thanks Ivanna

Dear Heather,

To set up validation for email you can use Email address mask system setting - feel free to adjust the RegExp upon your needs.

Best regards,

Angela

Hello Ricardo, 



As for now there is no possibility to apply multiple operators for the one filter condition when editing the business rule. 



We have this idea registered for our R&D team and I will notify them about this question so to increase the importance of implementing this functionality.



Kind regards,

Roman 

Roman Brown,

Dear Roman, this feature was posted in R&D several years ago, there no new regarding when will be considered?

Hi Community, Any idea on this?



Thank you so much

Dear Fulgen,

It is possible to check a mode of a page using the “phantom” property of the “record” object https://prnt.sc/qkxh4q

If the value of the property is equal to “true” it is mean that the page is in the add mode and vice versa. Please see an example of the code below:

Terrasoft.sdk.Model.addBusinessRule("Case", {

            ruleType: Terrasoft.RuleTypes.Custom,

            position : 2,

            triggeredByColumns: ["UsrIncidentType"],

            events: [Terrasoft.BusinessRuleEvents.ValueChanged],

            executeFn : function(record, rule, column, customData, callbackConfig){

                        if(record.phantom)

                        {

                                    // true, when adding a new record (add mode)

                                    alert("New record");

                        }

                        else

                        {

                                    // edit mode   

                                    alert("Old record");

                        }

                        Ext.callback(callbackConfig.success, callbackConfig.scope, [true]);

            }

});

Please find more information about a custom business rules in the article by the link below:

https://academy.creatio.com/documents/technic-sdkmob/7-15/custom-business-rules-mobile-application

Best regards,

Norton

Try to check if the module with the code appears on the client end. Please debug the code for this. 

https://academy.bpmonline.com/documents/technic-sdkmob/7-12/mobile-application-debugging

Additionally, please check if the manifest is correct. More information in my posts. 

https://community.bpmonline.com/articles/adding-custom-css-mobile-application

https://community.bpmonline.com/articles/adding-custom-user-action-mobile-application

Then check if the rule is correct. 

https://academy.bpmonline.com/documents/technic-sdkmob/7-12/business-rules-mobile-application

https://academy.bpmonline.com/documents/technic-sdkmob/7-12/custom-business-rules-mobile-application

Eugene Podkovka,

Hi Eugene, Thanks for your reply

Module appears on the client end, manifest is also correct.

Using below code without conditionalColumns rule is working fine:

Terrasoft.sdk.Model.addBusinessRule("Case", {

    ruleType: Terrasoft.RuleTypes.Requirement,

    requireType : Terrasoft.RequirementTypes.Simple,

    events: [Terrasoft.BusinessRuleEvents.Save],

    triggeredByColumns: ["UsrComments"],

    columnNames: ["UsrComments"]

});

But the above code will not serve our purpose, we only require "UsrComments" to be mandatory if "UsrIsClosed" field is true.

That's why I created below code:

Terrasoft.sdk.Model.addBusinessRule("Case", {

    ruleType: Terrasoft.RuleTypes.Requirement,

    requireType : Terrasoft.RequirementTypes.Simple,

    events: [Terrasoft.BusinessRuleEvents.Save],

    triggeredByColumns: ["UsrIsClosed"],

    conditionalColumns: [

        {name: "UsrIsClosed", value: true}

    ],

    dependentColumnNames: ["UsrComments"]

});

Please suggest, how I can use "conditionalColumns" attribute for rule type requirement.

Fulgen Ninofranco,

The code seems like correct. Try to restart the application pool and synchronize the mobile application again. 

http://prntscr.com/oyo0vz

Eugene Podkovka,

Thanks Eugene.

We already did the restart and synchronize but still not working. I also noticed one thing in the documentation. "conditionalColumns" is not discussed here as part of the attributes of rule type requirements but from other rule type it is included. Please suggest how we can achieve our condition if "conditionalColumns" will not work.  

https://academy.bpmonline.com/documents/technic-sdkmob/7-12/business-rules-mobile-application

Eugene Podkovka,

Hi Eugene, any update on this. Thank you

Fulgen Ninofranco,

Try to debug the mobile application, find how business rules work and find how to adjust them according to your needs.

https://academy.bpmonline.com/documents/technic-sdkmob/7-12/mobile-application-debugging

Start from the executeApplicableRules method in the BusinessRulesManager module.

Hi, did you find a resolution to your issue? I am facing the same thing.

If you want to disable the existing mobile business rule, you can do it by calling the removeBusinessRule function. The function accepts two parameters - the name of the model and the name of the rule. For example:

 Terrasoft.sdk.Model.removeBusinessRule("Case", "CaseContactAccountRequirementRule");