Skip to main content
sunilz6150
sunilz6150
May 1, 2023
Solved

Advanced Start Event Timer condition with an expression

  • May 1, 2023
  • 2 replies
  • 1 view

Dear Practitioner's,

I have a process model with a Start Event Timer configured to run periodically. The scheduler must be enabled/disabled based on a feature flag which is nothing but an entry in a DB table that returns a true/false (via a rule XYZ_isFeatureEnabled(name: "<featureName>") ).

I tried to add a timer condition with expression in the Start Event but it does not fetch the latest value from this table and requires the process model to be re-published to get the latest value from DB. Is this a standard behaviour when it comes to Start Event Timer?

I had to fall back to the OG method of adding a XOR gate after the start event to check if the feature is enabled/disabled and simply route to an End Event when it's not enabled. This works but I was trying to avoid triggering an instance itself.

Any thoughts?

Best answer by gopalk2865

yes you are right, to update the expression with latest value you would need to republish the process model. I also had to go for alternatives. I guess that is the only solution but lets wait if someone has implemented this in a different way.

2 replies

gopalk2865
gopalk2865Answer
Participating Frequently
May 1, 2023

yes you are right, to update the expression with latest value you would need to republish the process model. I also had to go for alternatives. I guess that is the only solution but lets wait if someone has implemented this in a different way.

    stefanhelzle0001
    stefanhelzle0001
    Brainy
    May 1, 2023

    Using a XOR for more complex or dynamic scheduling is a well known design in Appian.

      Terms & ConditionsAccessibility statement