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

Hi Sanjay,
not sure if I was able to explain the issue properly or not. Let me try explaining it again.

Node T1 calls rule R1 where I am reading acp and pvs and passing them to R2 that renders the UI. I need to update an extra acp say ac!employee in Node T1, how can i achieve it in a way that already existing instances of the process are not impacted.

I don't want to run a process migration for a small change as adding a acp to a node, moreover I dont want the existing instances to read or update this. It should only imapct the new one.

One option that I see is creating a new set or rule R'1 and R'2 and reading the new acp in these and configure the process model to call R'1 instead of R1.

but I will end up having numerous redundant rules if I follow this, so checking what is the best way to do it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 manisht over 8 years ago

Hi Sanjay,
not sure if I was able to explain the issue properly or not. Let me try explaining it again.

Node T1 calls rule R1 where I am reading acp and pvs and passing them to R2 that renders the UI. I need to update an extra acp say ac!employee in Node T1, how can i achieve it in a way that already existing instances of the process are not impacted.

I don't want to run a process migration for a small change as adding a acp to a node, moreover I dont want the existing instances to read or update this. It should only imapct the new one.

One option that I see is creating a new set or rule R'1 and R'2 and reading the new acp in these and configure the process model to call R'1 instead of R1.

but I will end up having numerous redundant rules if I follow this, so checking what is the best way to do it.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data