Related Action

Certified Senior Developer
Hi All,

When user accidentally double clicks on a related action shortcut , two instance is getting generated. Is there any way to avoid this ?

Thanks in advance

OriginalPostID-265571

  Discussion posts and replies are publicly visible

  • Hi Bestlinl,You can configure user start page in your related action,So whenever users submit the form,then only process instances will be triggered.Bu this way u can avoid unnecessary process instances.
  • Hi bestlinl, There are 2 ways you can go with:
    1. Disabling the Related Action - Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Build another expression rule for the visibility of the Related Action which returns true if there is no active instance otherwise false. This will disable the related action if there is an active instance for that process model. Configure this expression rule at the Visibility for the related action.
    2. Handling in Process Model - Keep the Related Action always visible. Build a Process Report with the context of the Target Process Model, in such a way that it captures every process instance detail. Build an Expression Rule with a!queryAnalytics() function through which you will be able to capture the process instance details as a data subset. Inside the process model add an XOR gateway at the very beginning in order to verify whether there is any active instance for the process model at that moment (call the expression rule to fetch the process instance details). If there is any, end up the flow otherwise let the execution follow the normal flow.

    If there are more number of users for whom the related action is available, you might need to add some more factor/factors (like the user/group context) to find more accurate details about the process instances.
    Hope this helps!!
  • 0
    Certified Senior Developer
    Thanks for your suggestion
  • 0
    Certified Lead Developer
    Hi Bestlinl,

    Do you mind confirming what Appian version/hotfix you're on? The behavior you're describing sounds like the bug referenced in the release notes of hotfix 17.1 A, AN-81012. If you're on 17.1 and haven't applied the latest hotfix, then this could be what is causing the behavior you're seeing.

    See: docs.appian.com/.../Hotfixes.html
  • That really helps. Thanks @darbyk. I would like to know, if this hotfix has been available for 16.x version as well?
  • 0
    Certified Senior Developer
    Hi darbyk,

    Thanks for pointing it out.
    We are currently on 16.2. Is there any hot fix on 16.2 ?