Skip to main content
T
thanosm587
April 2, 2021
Question

Appian 19.4 Node Timer Exception with Rule Expression

  • April 2, 2021
  • 8 replies
  • 0 views

Hello all,

Is it not possible to use a Rule Expression as the expression that defines the configuration of a Timer Event?

We have an issue with setting up a timer based Exception Flow on a User Input task where the timer is defined as "Skip this node at the date and time specified by this expression" and the logic is implemented as a Rule Expression instead of writing it directly within the Timer event configuration. The issue that users see when the Task is loaded is "This task may have been deleted or completed by another assignee".

However, when we copy the logic from the Rule Expression and paste it directly into the timer event configuration, then there is no such issue.

    8 replies

    csteward
    csteward
    April 2, 2021

    We utilize rules to determine exception flows in many locations without issues.  Are you able to share your rule definition? 

    T
    thanosm587Author
    April 4, 2021

    Hello Chris,

    Thank you for your response.

    The Rule Expression, named "LWS_timerStep10" has a single rule input "entryDate" of type Date and Time.

    Its definition is the following simple expression: caladddays(ri!entryDate, 5)

    Then, the rule expression "LWS_timerStep10" is used inside the exception timer definition of the User Task, which is enabled through Activity Chaining, meaning the user clicks on an Action and the process leads to this User Task through activity chaining.

    That is when we (as users) see the error described in my original note. Just to rule any possible security issues, the same error is thrown for both Basic Users and System Administrators.

    As I mentioned in my original note, if we use the definition of the Rule Expression directly in the exception timer then everything works just fine.

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    April 4, 2021

    Do you see any errors in process instance details? Is the task skipped in task history?

    Terms & ConditionsAccessibility statement