Skip to main content

Event cascading

Comments

4 comments

  • Official comment
    Oscar

    the event function does not support configuration for sequential execution. As you mentioned, certain event actions need to be executed within the event of Field B.

     

     


     

  • Alexander

    Thank you for your response. I did so (i.e. I repeated the rules of the “backwards” event), however now I have some sort of glitch in the rules. It turns out there are contradictions somewhere, which, for some reason, violate seemingly logical actions.

    For example, when saving changes, the event rules are not saved. 

    https://www.loom.com/share/2e9ff209dc3c468687700437725e7452?sid=3031b7c0-8b2d-43dc-90dc-9300b84c73bb

    When the value is “Bridge”, the “Yield Type” field is hidden, everything is correct. But, as soon as I try to manipulate and bring it to the same “Bridge” value again, then eventually, the “Yield Type” field is not hidden when saving the change in the card... How can I customize it to get it right? In the event settings - there are a lot of options there, literally in every field you can customize the event for a completely different field. I do not know where to set the settings for the current field. Or should I use business rules for this?

    0
  • Oscar

    I apologize, but it's difficult to pinpoint the issue solely through text and video. If possible, could you export the application and upload it so we can review the specific configuration? Alternatively, you may reach out to your consultant for assistance.


     

    0
  • Alexander

    Thanks for your reply, I assumed there would be little understanding from the video and description, since I have extensive event settings, it's hard for me to explain the problem in a nutshell. I will try some more experimenting with the settings and “crossing” them with each other.

    0

Please sign in to leave a comment.