search

ArasLabs / refresh-from-database

Adds a toolbar button to the item tearoff window which refreshes the item with information from the database.
MIT License
6 stars 4 forks source link

Behaviour of Method on superseded Items #3

Open AngelaIp opened 6 years ago

AngelaIp commented 6 years ago

Hi,

when I use Refresh-from-DB on a superseded Part, I will get the database content of the latest version of the part. According to the code, this seems to be indended behavour.

But from my point of view, this behaviour is sometimes a little bit confusing to the enduser. Main reason: We also use the non-current-overlay project. But the non-current-overlay will not update after pressing refresh from db from a superseded Part.

I expect you will now ask the following legitimate question: "Why should anyone press Refresh on a Superseded Part at all? Superseded Parts cannot be changed, so there is nothing to be updated." A good argument! But on the basis of my observations in a real productive environment, I can say: People just love refresh! Some of them refresh quite everything! I don´t have an explanation for this, but this is what I have seen. And they also refresh superseded items. And then they are confused that they see the latest version of the part but also the non-current overlay.

What is the best way to deal with this? I have made a SP11 pull request some minutes ago. I don´t think it´s a big task to change the Method for improved handling of superseded items. But the "show the latest" Part is also a quite useful feature. Maybe it would be a better idea to improve the handling of the non-current-overlay?

Best regards! Angela

AngelaIp commented 6 years ago

Hi,

I think my comment was a bit misleading. In my case, with 'superseded' Items I meant earlier revisions of an Item. I didn´t mean the classic 'superseded" Items created by a change process like the Express ECO.

I right now use the following customizations:

  1. I changed the behavior of the refresh from db button to stick to the current generation. This has pros&cons. Pro: No conflict with previous item revisions. No conflict with non-current overlay. Con: It eliminates the features ability to show the latest item version automatically.

I bypassed the disadvantages with the following customizations:

  1. I extended the 'PE_CreateNewRevision' Action to refresh the Form and tabs automatically.
  2. I use an extra CUI button for "Show me the latest version of this Item".

I wouldn´t say it´s the best way to face this issue. It´s one possible solution. But it´s suitable for customers that aren´t afraid of using a battery of refresh buttons.

Angela

AngelaIp commented 5 years ago

I think the conflict with the non-current-overlay project can be solved by using an onFormPopulated event instead of an onLoad event for the overlay Method. I am not able to test it, but maybe it´s of interest for others that use this combination.