Hi,
everybody loves ECO questions! People look at these questions and then they are happy that their own topics are much more trivial :).
I am familiar with the EHT. Are there any additional custom modifications? In your ECO, do you only change the "state" of an item or also the "production state"?
First I would unhide the "Affected Items" tab so you can see it in the ECO. Check if the affected_id items and new_item_id items are correctly assigned.
Hi Angelalp,
thanks for taking interest in this case, and yes ECO issues ara a special breed of problems :)
We can also change the production state in our ECO. Basically its the standart EHT version where we have defined our own production states and we have some additional state or validation function into the standard validation routines.
The functionality is working correctly on our live V12SP12 production environment, but the issue we see occurs both on our new test environment and our new production environment that is not yet gone live.
I unhided the affected items and the affected_id and new_item_id are correctly assigned.
Its almost like the browser gets confused which item it should show in the form accordian. The signoffs tab is still linked to the Express ECO and thus we are able to vote the ECO though is workflow, but everything in the main item toolbar is now connected to the part that is the affected item.
If we now close the ECO and open it again, it shows correctly the data.
Hi,
if its a breakthrough or not I`m not sure, but we found a connection between when the issue is generated and if the part that is the eco`s affected part is open in a tab.
By just cloing the part before going to the ECO and voting it to "In Work" we avoid the issue from being generated.
If we have a different part than included as a affected_item on the ECO it does not generate the issue, only if it is an afffected_item.
We also use custom production states, but I never found the patience to update the validation checks. Nevertheless, I have so far not seen this behavior at all.
Can you reproduce the error in a OOTB I31 instance with the original ECO?
As you mentioned 12SP12 I first thought the issue would be related to the "Inferno" grid changes. Aras introduced a faster grid engine back then around this version number (as far as I remember).
Your latest post indicates that the context item used for your affected part is invalid. Just like it would be if you execute a certain Method from an Item vs. the Method editor. "This" is something completely different depended from the context the Method is executed.
Have you asked Aras about this one?
We tried asking Aras support, but they want it to be handled as part of our upgrade process. I just don't understand how the "pre-" method in a life cycle transition can accidentally change what the context object is... in the frontend at that.
It's also confusing how it still manages to do the right thing as long as there's no tab open with an affected part.
