IBM Data Platform Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Hi, please refer to Case: TS022677066
We are on IBM FTM 3.2.4 FixPack15.
Currently, FTM-MER applies a four-eyes control for payment processing.
Person1 - to manual construct an Message at Data Entry (DE) queue.
Person2 - to approve the message in Authorisation1 (AU1) queue.
Person1 or Person3 - to approve the message in Authorisation2 (AU2) queue.
Note: These MER queues defined as -attr Purpose -val DblAuthorize
Moving forward, we would like to have Six-Eyes Authorisation Control, meaning:
Person1 - to manual construct an Message at Data Entry (DE) queue.
Person2 - to approve the message in Authorisation1 (AU1) queue.
Person3 - to approve the message in Authorisation2 (AU2) queue.
Each stage must performed by different user, i.e the same user should not be allowed to perform more than one role for the same message.
Kindly advise the configuration changes if any.
regards
Ms Alice Choong
Public Bank Berhad
Please find below a couple of samples for reference;
Functional view for single Auth - https://www.ibm.com/docs/en/ftmfss/3.2.4?topic=facility-example-mer-business-workflow
Single Auth Routing - https://www.ibm.com/docs/en/ftmfss/3.2.4?topic=flows-fin-scenario-1
Double Auth Routing - https://www.ibm.com/docs/en/ftmfss/3.2.4?topic=flows-fin-scenario-2
FTM for SWIFT provides the capability to configure workflows that achieve six-eyes control through double authorization and appropriate user-routing rules, but the product does not automatically mandate that every transaction follows a three-user Maker/Authorizer1/Authorizer2 process. The actual behaviour depends on how the MER queue workflow is configured.