Ron - Thursday, April 23, 2009 9:22 AM:
The superseding items on ECR are not floating to the latest generation. This issue has just been rasied, it was working a few weeks ago, but now it is not and I am not sure what changed to cause this issue.
Any help would be a great help.
Thanks
Ron
RobMcAveney - Thursday, April 23, 2009 10:10 AM:
Hi Ron -
There's a hotfix for the Affected Item Floating issue posted here: http://www.aras.com/communityprojects/?projectid=7323D24FB8D444679F64F1604A02F8DC.
Rob
Ron - Thursday, April 23, 2009 10:20 AM:
Hi Rob
I think that this is what broke our Innovator, I had installed the patch on March 18. From what we can tell this is when the problems started, now I just need to find out how to go back in time and undo this patch.
Ron
RobMcAveney - Thursday, April 23, 2009 1:20 PM:
Hi Ron -
We haven't had any other reports of this hot fix causing problems. It may be something specific to your environment, but we'd have to dig in to find out. If you really want to disable the patch, you should set the Item Behavior on the new_item_id property back to Fixed and disable the PE_AffectedItemFloat Server Events on Part and Document.
Rob
Ron - Thursday, April 23, 2009 1:48 PM:
Rob
Changing the new_item_id back to Float has corrected this issue. Now the question is can I leave the PE_AffecteditemFloat server event still active and will it work as designed? or do I need to remove it?
Thanks for all your help.
Ron
RobMcAveney - Thursday, April 23, 2009 1:56 PM:
Ron -
I would definitely disable (set the event to blank) or delete the Server Events. It should theoretically work with them still active, but it is completely untested so I wouldn't suggest it.
Rob
Ron - Thursday, April 23, 2009 2:09 PM:
Thanks, I will disable it.
The reason we implement this fix was to correct the ECN reports. When looking back at some older ECN we noticed the revisions were not correct for the items at the time the ECN was released.
My thinking on a way to correct this was simple set the lifecycle map Released State to Fixed, thus when ever a ECN was released the ECN would be Fixed and should show the correct information. Would you agree that this would work?
Thanks for your help.
Ron
