FTM documentation in Knowledge Center spread over several versions
Documentation for FTM is spread over multiple versions in the FTM knowledge center.For example, the Knowledge center for FTM for z/OS 3.0.1 has only information about FTM CPS, RIsk Management and Services and PFS, and misses a wide variety of info...
almost 4 years ago
in Documentation
0
Future consideration
OAC pages should show creation timestamp on errors
On the details page of any FTM object (PT, batch, transaction, svc_participant...) the errors tab shows a list of errors. The errors attribute include the following, but not the creation date and time IDApplication IDTypeComponent TypeComponent Na...
Provide scripts for role-based access to FTM database
FTM for z/OS ships a database script 'FTMXGR01' which grants database permissions to the PUBLIC database role. This is unacceptable in a production environment.FTM for Multiplatforms provides no script to restrict database access. Scripts should b...
almost 4 years ago
in Security
0
Future consideration
OAC login and authorization by means of TAI that populates WSSubject with user and groups
My customer is using a Trust Association Interceptor (TAI) which provides the end user authentication and authorization. The TAI is setting up the Principal (username) and his Groups in the WSSubject. Their federated repository that is configured ...
almost 4 years ago
in Security
1
Planned for future release
Pain001V5 to ISF Mapper, request for Core Mapper with support for Post-Body Mapper to harvest ABN-specific Supplementary Data
In response to the requested Pain.001V5 to ISF mapper, please find attached the final specs (see file "FTM_Mapping_PAIN001.001.05 to ISF v0.3_Final for RFE.xlsx") In short, we would require 1. a Core Mapper based on XSD Pain.001V5, 2. with support...
If a source system sends a malformed XML message to FTM V3.0.0.7, the FTM OAC "Raw Data" tab cannot display the message. Instead, it displays the following error message:Error: TypeError: Argument 1 of XSLTProcessor.transformToDocument is not an o...
Physical Transmission created time should reflect the time when the PT is created, not the time of the in mapper completion
The creation timestamp for physical transmission currently reflects the time when the inbound mapper has completed execution, rather than the time when the message was received
almost 4 years ago
in Other
0
Future consideration