I have an existing version of Process tasks that updates certain set of ac!param

manisht over 8 years ago

I have an existing version of Process tasks that updates certain set of ac!parameters. when I try to add a new ac! to this node and update it my existing in-flight instances break with an exception "Could not find variable ac!XXXX".

I tried using a some conditions so that only new process instances try to load this component (Text field) and update it and existing in-flights don't load this, no matter whatever i configure in the rules whether it loads the component or not it still verifies for the ac!parameter to be available and thus in-flights fail.

what is the best way to update the ac! in existing nodes as in this case?

Discussion posts and replies are publicly visible

Parents

0 manisht over 8 years ago

Thanks Amit,

hope you are doing good :)
This is the probable solution that we will go ahead with, was just keen to know if there is something that can check if an ac parameter is configured in a node or not e.g isnull(ac!employee) and then we could modify the existing rule to either load the component for new instances or skip it for previous instances.

creating constants, and multiple UI nodes or creating new set of rules and mapping them to existing node are the possible ways but it will only make the water muddy. Imagine the number of rules created or nodes added down the line after having several enhancements/modifications similar to this.
In absence of any other option we will have to stick with one of these.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 manisht over 8 years ago

Thanks Amit,

hope you are doing good :)
This is the probable solution that we will go ahead with, was just keen to know if there is something that can check if an ac parameter is configured in a node or not e.g isnull(ac!employee) and then we could modify the existing rule to either load the component for new instances or skip it for previous instances.

creating constants, and multiple UI nodes or creating new set of rules and mapping them to existing node are the possible ways but it will only make the water muddy. Imagine the number of rules created or nodes added down the line after having several enhancements/modifications similar to this.
In absence of any other option we will have to stick with one of these.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data