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.
Hello Piotr,
Apologies for the delay in replying. And thank you for clarifying the audit requirement on QNTM-I-1534.
Access to audit history via a particular static data record, in your case the counterparty bank account is definitely something we should look into in the future.
I have changed the status to future consideration – thinking it should be a concept for all static data and not just counterparty bank accounts.
I am also investigating with my colleagues if this is something we could handle using a Workflow Report under our Enterprise Workflow Framework, just for counterparty bank accounts.
Counterparty Delivery Instructions is part of static audit recording who, when and what was changed. It would be impossible to include this in the audit history for a deal that is associated with the particular account.
Changes to Counterparty Delivery Instructions can be managed by module security permissions as well as single or dual approval.