Hi Vanessa,
did you check the transitions ass well?
I had a same error in Evolve a few weeks ago and finally I discovered ther was a double transition line between the same objects. Don't know how that happened. But had a an (crash) error before in Evolve and looks like it got partly corrupted then. Discovered it when trying to change the connections of the transistion and saw there was a second one. After removing the transistions and creating a new one the problem was solved.
------------------------------
Jan van Asseldonk | Consultant
CTAC | +31629078169
------------------------------
Original Message:
Sent: 04-01-2022 16:56
From: Vanessa Kutasi
Subject: Foundation 12.1 Workflow Error: Object reference not set to an instance of an object
Hey Friends,
I am receiving an error during the rejection process of a child workflow. I've checked all the table dropdowns to make sure connections are properly set. I've checked the transitions and those appear to be properly set. I've googled what this error means in general as I didn't find anything within support documentation. I'm stumped! Has anyone else run into this?
The reject button does have custom rules which set triggers for the workflow. Those custom rules do include the "reject" action. I have done this same process with other workflows without any issue.
Approving works fine and the workflow moves forward. It's just when rejecting that this error occurs.
Thank you!
------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------