Announcement

Collapse
No announcement yet.

[Bug?] Task, if you click "Complete" you can bypass the rules..

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [Bug?] Task, if you click "Complete" you can bypass the rules..

    Hi!
    So if the user clicks "Complete" on a task, it overrides any rule for required fields, but if you click the edit button, and then update the stage, it works fine.
    Any workaround?

    Thanks

    Video of the problem: https://public-lbc.s3.us-west-2.amaz...5.23.43+PM.mov

  • #2
    Not a bug, buttons are completely separate from dynamic logic. Unfortunately, currently there's no way to remove button w/o code changing.

    Comment


    • #3
      As a workaround, consider a before-save script that will revert 'status' to a fetched value if some condition is met.

      Comment


      • #4
        >Not a bug, buttons are completely separate from dynamic logic

        This probably makes total sense on the backend, but 0 on the operations
        Will check workarounds

        Thank you

        Comment


        • #5
          It makes sense from the tool design point of view. Dynamic logic operates fields, not buttons in the UI. Such tool by design are impossible to be done w/o any side effects. What we can do is to add the ability to remove such buttons for the admin. Or receive $? investment to develop something that will solve this issue. When (if) we implement some backend validations for dynamic logic it will partly solve the issue too. But I'm sure how some people will negatively react on any backend validation we add.
          Last edited by yuri; 03-11-2023, 07:56 AM.

          Comment


          • rabii
            rabii commented
            Editing a comment
            > What we can do is to add the ability to remove such buttons for the admin.

            Do you mean add ability for admin to control visibility of the buttons ? if yes then will it be applied via roles/permissions ?

        • #6
          Originally posted by yuri View Post
          It makes sense from the tool design point of view. Dynamic logic operates fields, not buttons in the UI. Such tool by design are impossible to be done w/o any side effects. What we can do is to add the ability to remove such buttons for the admin. Or receive $? investment to develop something that will solve this issue. When (if) we implement some backend validations for dynamic logic it will partly solve the issue too. But I'm sure how some people will negatively react on any backend validation we add.
          Totally understand, thanks

          Comment

          Working...
          X