Hello Fulgen,

This is an out-of-the-box behavior of the application and we've created a problem to our R&D team so they could fix it in one of future versions of the application. This is a very interesting problem and thank you for reporting it to us. Currently we assume that it cannot be changed sine it is a hard coded behavior of the application in base schemas and fix needs to be applied by our R&D team. Once this fix is applied - we will notify all our users in Academy release notes that can be accessed here.

Thank you for helping us to make our application better!

Best regards,

Oscar

Hi, you can do a business process. Reading the approval use a conditional flow when the approval is approve you modify with the modify item the stage field to "Checked" and when is "Rejected" to Something else.

I hope i can help you!

King regards!

It's possible to do via js development. I hope the development guide below will help you. ApprovalDashboardItemViewModel module contains approved/reject button.

https://academy.bpmonline.com/documents/technic-sdk/7-13/bpmonline-development-guide

Rather than override the click, maybe it would work to just wire up a change event on the property itself? See https://customerfx.com/article/triggering-an-event-when-a-field-is-changed-on-a-page-in-bpmonline/

Something like this:

attributes: {
  "StageChange": {
    dependencies: [{
      columns: ["Stage"]
      methodName: "onStageChange"
    }]
  }
},
 
//...
 
methods: {
  onStageChange: function() {
    // do something here or prompt user
    // if needed, revert back to previous value
  }
},

If you need to revert back to the previous value, what I would do is store the current Stage value in an attribute in the onEntityInitialized. Then you can use that to revert back if needed (and update the attribute if you do allow the change). 

The only thing that could cause issues with this approach is if there are processes or case steps that would have already fired before you revert the change. Anyway just an idea.

I didn't spend too much time looking at the Dcm mixin to override the logic there, but this approach would be easier so thought I would suggest it. Hope this helps.

Ryan

Click event of a workflow bar causes saving of a page. Before saving the page a validation happens. Please feel free to override the method asyncValidate to add a required functionality. For example: 

define("LeadPageV2", [],

    function() {

        return {

            entitySchemaName: "Lead",

            details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,

            attributes: {},

            methods: {

                asyncValidate: function(callback, scope){

                    this.callParent([function(resultObject){

                        resultObject.success = false;

                        resultObject.message = "Your message!";

                        callback.call(scope, resultObject);

                    }], scope);

                }

            },

            diff: /**SCHEMA_DIFF*/[

            

            ]/**SCHEMA_DIFF*/,

            rules: {},

            userCode: {}

        };

    });