Skip to Main Content
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.


Status Shipped
Created by Mark Zumbraegel
Created on Oct 19, 2020

Dual approval for Module Security

Changes to module security should optionally be subject to approval.

Work in
QNTM-E-2424 Dual approval for Module Security
  • Attach files
  • Admin
    Mark Zumbraegel
    Reply
    |
    Jul 1, 2022

    Unfortunately, there isn't a good solution for this.

    The reason the product is like this is that in v5 there were three separate applications: one for users and groups, one for menu/module security, and one for resource security. Only this first app had approval capabilities. The other two apps are now tabs on the first one and that gives the impression that they also should have approval capabilities, but they don't.

    Adding this capability to module and resource security is significant.

    This has been raised many times before, and the 15-minute window of security changes was a result of that. It's not ideal, but it at least gives module security control over who can turn this on. It should be configured so that users cannot turn this on for themselves.

    Workflow tables do support n-level approval, but we currently don't have any workflow actions to perform approval, nor do we have workflow actions to update module or resource security. I also don't think we want those due to similar security considerations.