[Pansophy] EBW Request System Traveler Instantiation

[Matthew Menia]

Hi Adam,

>From what you describe below it does sound like an issue with the counter. I have a couple of questions to help resolve this.


  1.  What sequence numbers were duplicated?
  2.  By cross referenced do you mean the data was split when entered and added to both travelers sharing the same sequence number?

The close and update buttons do require an open traveler. I may be reading the email wrong but the update does not automatically create an instantiation.

I will keep you updated on the findings,
Matt

From: Adam O'Brien <aobrien at jlab.org>
Sent: Thursday, July 10, 2025 3:09 PM
To: Matthew Menia <menia at jlab.org>
Cc: pansophy <pansophy at jlab.org>
Subject: EBW Request System Traveler Instantiation

Wasn't sure how to report this since it's across the request system and the traveler system.  Using the traveler instantiation system, the following happened:

-Went to the EBW SR Admin, located GiGi's request (#5), and clicked "Open Traveler".  Window said action was completed successfully but did not auto-direct to the traveler or provide a popup.
-Went to SRFRD-EBW-COMP and the new traveler entry was instantiated, filled in remaining fields and updated.
-Returned to the SR admin page to instantiate second traveler for that request, however request was automatically moved to the "complete" section (Until we complete the weld-breakout part of the project, I think requests should stay open until we select "Complete Request").  Did NOT instantiate a new traveler from the admin page at this time.
-Returned to SRFRD-EBW-COMP and opened a new traveler, entered fields and instantiated.  I noticed after comparing the first traveler (generated from the request system) and the second (generated "normally"), all the data fields were cross-referenced.  From the drop-down, it looks like the entry from the SR and the "normal" one are sharing the traveler sequence number.
-Instantiation of another traveler from the SRFRD page used the next appropriate sequence number.

-I returned to the EBW SR system, and repeated the above steps, with the same result (Instantiation from the EBW SR system followed by an instantiation directly in the traveler results in the two entries sharing a sequence number).

I'm guessing there's a difference between how the two requests are processed and one of them isn't stepping the counter properly.

After the above, checking functionality of other buttons, both "Close Traveler" and "Update Traveler" result in an error - I did not test this before instantiating two travelers from that one request, not sure if it's related to that or something else.

Thank you,
Adam O'Brien
Staff Engineer II, SRF Operations
600 Kelvin Drive
Suite 8, Mailstop 55-H
Newport News, VA 23606-4323
Office: (757)269-7279
Cell: (513)290-3210
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/pansophy/attachments/20250710/df8b65cb/attachment-0001.htm>