Rejection Errors at Top of Running Screen – Waste of Space and Time!

• 03/11/2024 at 9:13 AM #229573
  GraHal

  Rejection Errors with the yellow triangle showing at the top of the screen (see attached) is, in my opinion and experience, a recently introduced feature which does not work and is a frustrating time-waster!

  I have never liked it and here is why …

  1.  As soon as I click the yellow triangle, that System then goes down to the Not Running section.
  2. I like to know why a System has been Rejected and I enter the reason in the Comments column.
  3. Due to 1. above … 2. above is now a tiresome / time comsuming process as I have to go hunting for the System in the Not Running section … that’s if I have made a note / can remember which system just got flipped from the yellow triangle section to the Not Running section!
  4. I know I can acknowledge all the yellow triangle Systems in one go … but why would anyone want to do that as then we not know why Systems were Rejected??

  5.    The old way was fine where the yellow triangle Rejected Systems appeared in the not running section and then – while I was on the same line / row I could click on the yellow         triangle and enter the reason ON THE SAME ROW as I just clicked the yellow triangle.

  The above frustration came to a head today  due to having 16 Systems Rejected overnight!!  I could not face tracing 16 Systems back to the not running section (from the yellow triangle Rejected section) as tiresome and very time consuming and so I now have no record (in the Comments column) for these 16 Rejected Systems!

  

  GraHal

  Participant

  Topics: 204

  Replies: 8401

  Been thanked: 2042 times
  03/11/2024 at 9:26 AM #229580
  PeterSt

  Yes, the solution -announced somewhat differently – is half-cooked.

  It it NOT so that the old way was fine (and you know it) because that would not even allow to find back stopped systems in the first place.
  Anyway, it still is so that some at ProRealTime must for once try to use their own package.

  What happens when you only confirm the entry via the check box ? Same thing and can’t be found back in the not-running systems ?

  What happens when you’d tag each entry in advance with some sequence number or other ID in that text, and that may allow you to more easily find back the entry ?

  

  PeterSt

  Participant

  Topics: 70

  Replies: 2287

  Been thanked: 695 times
  03/11/2024 at 9:29 AM #229581
  PeterSt

  PS:

  Previously I had the idea to let those stopped systems be and that upper part, until I did something about them. What’s part of that is that you would know by means elsewhere what the reason of throw-out was.

  Anyway, yesterday I was thinking : why add this feature as a solution to the mess in the bottom part, while that mess could be solved just the same ? … and I got annoyed once again …

  Let’s keep in mind : they G-D asked me (see the special topic for it). 🙁 🙁

  

  PeterSt

  Participant

  Topics: 70

  Replies: 2287

  Been thanked: 695 times
  03/11/2024 at 10:01 AM #229584
  GraHal

  The ideal solution would be …

  1.   Not flip the System to Not Running section after clicking on yellow triangle, but for another flag to appear (green triangle maybe?).
  2.     We could then easily enter reason for Rejection in the Comments column one by one for each System after clicking on yellow triangle and while the System is stil in the top section.

  3.    Then after all the yelow triangles turn to green triangles, we can – if we want – acknowledge all the green triangles                and so all Systems then flip back to Not Running Section.  Or flip to the Running Section as a user Option.

  4.    3.   above would allow us to easily identify and make changes to the code of green triangle Systems (on code editor)

  5.  I would also like to be able to expand the top section with yellow triangles so I can see ALL the Rejected Systems (not             just 3 at a time).

  Any better ideas anybody while still retaining the top section for Rejects … which does have merit but is ‘frustratingly not usable or useful’ in it’s current form.

   

  

  GraHal

  Participant

  Topics: 204

  Replies: 8401

  Been thanked: 2042 times
• Author
  Posts