Quantum Ideas Portal
Welcome to the FIS Treasury and Risk Manager - Quantum Edition Aha! Ideas Portal.
By visiting this portal, you will be able to contribute towards the evolution of the Quantum solution through interactions with other Quantum users, FIS trusted partners and FIS staff from around the world. Each Portal User receives 5 votes. Each user is allowed 1 vote per idea. Votes are reset when an idea is in a final state i.e. Shipped (delivered in the product).
Users will receive weekly email updates that highlight new activity. Users will receive emails for their created ideas when:
Status changes
Comment changes
Be aware that when you post content, other community members will see your name. FIS is not responsible for content posted by other Aha! Ideas Portal Users.
From Eric Willems & Suz Cooke:
I suggested quite a few years ago to add a timestamp column to all tables that have a stamp column. The stamp column is used to deal with concurrent updates to the tables. This is a simple sequence number. If two users retrieve and save the same record, it will check and increase the stamp number and only the first user will be able to save successfully.
ES modules were already using timestamp on their tables for dealing with concurrency. Rather than checking that the stamp value is the same, it checks the timestamp. We have adopted this practice in workflow tables by automatically adding stamp and timestamp. On any create or update the timestamp is updated on workflow tables.
There was hesitation to do this for all tables with the technical guys, as comparing dates is slightly more expensive than comparing simple numbers. As you can have high volumes, this may impact performance slightly. It would also take up some more database storage.
Support were really excited about the idea of having a timestamp on all tables as it would be very easy to see what changed in the database when you did something in the system.
I still think it is worth exploring as the benefits are so high.
Nothing was logged into Aha! or Jira for this.
Thanks,
Eric
From: Cooke, Suzanne <Suzanne.Cooke@fisglobal.com>
Sent: Thursday, 26 January 2023 3:56 pm
To: Hitch, Chris Y <Chris.Hitch@fisglobal.com>; Willems, Eric J <Eric.Willems@fisglobal.com>
Subject: RE: AQT-61428 - MOD request to add timestamp column in EFT screen display - Siemens
Hi Chris,
That would require major work. Currently we record the value date. Not the time we generated the EFT.
A lot of our fields formatted like date/time actually don’t record a time at all. So even if we split it out you would have no values.
I can’t help but think we looked into this some time ago, not this particular scenario for EFT, but a time stamp in general; but I don’t think we ever progressed anything.
Maybe Eric has started re-thinking this on some of the workflows? Looking at our structure I doubt it, very few tables have a specific time stamp
advqueue
advqueue
ca_notice
chqreg
confochk
confochk
confocmt
confodat
data_translation
dealnote
dealnotei
newdeals
note_attachment
note_attachmenti
qtdeal
sysnotes
wavg_lnk
Kind regards
Suz