Forum Discussion

BerntOve's avatar
BerntOve
Ideator I
9 months ago

ECO Item in Browser changes after voting it from Planning and to In Work

Hi all,

Currently setting up a new production environment with V31 and have gotten a very special error on our ECO item.

The ECO is slightly modified, but uses the EHT module from Minerva for dynamical assignment.

Everything is going as planned until the ECO is voted to In Work. When the ECO refreshes it has changed its keyed_name to the affected_part keyed_name, and has gotten a new item ID. When trying  to seach in the database after the ECO with the new item ID it does not exists.

It seems that the ECO is now trying to be the afffected part, but the signoff tab still works, and we are able to finish the voting and release of the ECO and its affected parts.

If we close the ECO tab and open it again its back to its normal state.

It seems like its a client/browser issue, but I*m now at a miss to where troubleshoot. I have excluded server and client methods, but the issue is still present.

We are using Edge (Version 131.0.2903.112 (Official build) (64-bit))

Any tips and help is greatly appreciated!

Affected Items
ECOs

10 Replies

  • BerntOve's avatar
    BerntOve
    Ideator I
    9 months ago

    Update on the issue.

    If I close down my broser after creating the ECO and before voting the ECO to "In Work", the issue is not observed. Why this has an impact I have no clue at.

    Bernt Ove

    • AngelaIp's avatar
      AngelaIp
      Ideator I
      9 months ago

      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. 

      • BerntOve's avatar
        BerntOve
        Ideator I
        9 months ago

        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.