PEM Community Manager v6.2.3.1 Release Notes

New Features/Enhancements: ​

  • Assignment of Multiple Know Host Keys
    Multiple known host keys can be selected for the SFTP Hub to Partner and Hub to Application setups.
  •  File Transfer Correlation Advanced Search
    PEM Community Manager now offers an advanced search capability for analyzing file transfer transactions within monitored network traffic. This enhancement enables users to efficiently search through file transfer data, specifically focusing on correlation data, with the ability to handle correlation data of up to 1MB in size.
  • Reprocess in PCM regardless of data being purged in B2Bi

    Customers can now reprocess the files from PCM, even after the source executed business process instance is purged in B2Bi.

    The below business process is included as part of this feature

    Business Process NameChange Description
    CM_restAPI_ReprocessNew BP Included; Invoked from PCM for Archive Reprocess feature and sends the response back.
    CM_API_ReprocessNew BP Included; Decodes the File Contents and Process data elements and sends it to Core Process.
    CM_Database_LogInfo

    Enabled process to invoke the CM_ProcessData_Encode and loads the Encoded Process Data values into

    Transfer Info Tables.

    CM_ProcessData_EncodeNew BP Included; Invokes the CM_ProcessData_Extract and encodes the XML to base64.
    CM_ProcessData_ExtractNew XSLT Included; Creates the XML Process Data with the required data.

     

    Note: The source file archive rule in the data flow is mandatory for this feature to work.

  • Perform Connectivity Test

    Customers can now test the connectivity after the Partner/Application is created from the Actions -> Test option. This functionality is applicable only for S/FTP/S Hub to Partner, AS2, Connect:Direct and AWS-S3 Protocols. We have a default timeout set for the API response from connectivity test to maximum wait time as 60 seconds beyond which we will be able to see an exceeding connection timeout error message The below Business Process are modified.

    Business Process NameChange Description
    CM_PEM_restAPI_ConnectivityTestSends BP Instance ID and Status as Response, Respond Service invoked using the HTTP Transport Instance and Session ID, Releases the Primary Documents.
    CM_PEM_ConnectivityTestIncluded S3 Protocol Choice, Application Profiles are added, Assign Service included to combine separate Assigns.
    CM_TestNowAS2New BP included, is copy of Predefined TestNowAS2 BP, where additional logic is included to send status back to PCM and exit.
    CM_TestNowHTTPNew BP included, is copy of Predefined TestNowHTTP BP, where additional logic is included to send status back to PCM and exit.
    CM_TestNowProfileLookupNew BP included, is copy of Predefined TestNowProfileLookup BP, where additional logic is included to send status back to PCM and exit.
 
  • Improvements on Onboarding multiple Partner/Application Names (Accounts) under the same Partner ID

    Customers can now create multiple AS2 Profiles by creating and adding additional accounts under the same.

    All other Protocols onboarding is also enhanced using the Create and Add button in the UI where different Partner Names (Accounts) can be setup for the same Partner

  • Improvements on Managing of multiple Partner/Applications Names (Accounts) under the same Partner ID

    Customers can now use Edit All to view/edit all the Partner Names (Accounts) belonging to the same Partner ID. Also, the Delete Panel can be used to remove any specific Partner Name (Account) which does not need to be modified.

    Protocol Change Enabled for Edit Option on specific Partner.

    Note: Protocol Change is not applicable in Edit All Option.

  • Polling Interval Validation

    Customers can now only create unique polling interval names in the Settings menu of PCM.

  • Audit of Rules

    The Rules are now audited, and the changes performed on the Rules can be viewed through Actions -> View Audit Info.

  • View File Size Configuration

    Customers can now configure the size allowed in application.yml file, for viewing the file in File Transfers menu. Any files more than the specified size would give a pop-up to download it and cannot be viewed directly.

    Note: The files need to be archived using source/destination file archive rules for this feature to work.

  • Configurable Application Title

    Customers will now be able to view the application name configured in application.yml in the browser tab title/header.

  • PEM Community Manager accepts \ or / for Directories

    Customers can now provide either backward slash or forward slash directories in Hub Connected to Partner/Application scenarios for B2Bi- SFTP, B2Bi-FTP, B2BiFTPS and S3, FILESYSTEM, HTTP, HTTPS Protocols.

  • AS2 Protocol Partner and Application DeleteInSI checkbox
    Customers can now delete the AS2 profile in SI by checking the DeleteInSI checkbox while deleting the partner/application and when unchecked will delete the profile only in PCM.
  • PCM Partner/Application module will not accept space for AS2 protocol for the name.
    PEM CM will not allow spaces for Partner Name/ Application Name to match with the validation of B2Bi.
  • TLS v1.3 Support for DB2 and MSSQL:Enabling TLS v1.3 in both DB2 and MSSQL ensuring a higher level of security by reducing the attack surface and strengthening defenses against known vulnerabilities and streamlining the handshake process, resulting in faster connection establishment times and reduced latency, enhances overall application performance and responsiveness.
  • Trading Partner/Application Advanced Search:
    Customers can now search for partners/applications using Advanced Search where it is no longer mandatory to provide protocol. Partners/Applications can be searched using combinations as well of different protocols or of the same protocol enabling customer for a wider criterion.
  • Improved Bulk Reprocessing of files:Customer can now perform bulk reprocessing for a maximum of 25 transactions and can view the report in the pop-up, which provides the status of the reprocess request.

    Note: The actual status of the reprocessed file is not available in the report. It can be tracked in the File Transfers -> Search.

  • Receipt Timeout for As2 Protocol Customer can now provide Receipt TimeOut in case of MDN type set to ‘Yes’ from PEM CM UI in Partner/ Application modules for As2 Protocol.

    Note: When MDN type is set to ‘Yes’ and receipt timeout is not provided, the response time value will be assumed for receipt time out as well.

  • Business Process Improvements – Below Predefined Business Process are modified
Business ProcessChange Description
CM_SFGPARTNERTOHUB_GET

Delete After Collection logic is enabled in

CM_SFGPARTNERTOHUB_GET Business

Process for Mailbox Protocols.

CM_ErrorHandler

XSLT: CM_BuildNotification

Error Handler Business Process modified to trim to 300 characters for the Error Details.
CM_SrcFileArchiveSource File Archive Business Process is modified to fix On Fault Issue and to get the File Size in KB.
CM_MailBox_PUTMailbox PUT Business Process enhanced to enabled User Token.
CM_Database_LogInfo

Enabled 24-hour format for File Processing view in PCM File Transfers through

Database Loginfo Business Process.

L3 Reported issues/Fixes:

  • PEM-26499:

    Mailbox Routing rules are not deleted when the Partners are deactivated

    Fix Details:

    Routing rules will be deleted for the trading partner/applications when deactivated.

  • L3REQ-57256

    MS/MQ Queue Name exceeds 50-character Limit in PEM CM

    Fix Details:

    The User Interface is updated to accept up to 255 characters for Queue Name and Queue Manager in MQ partner/application setup.

  • L3REQ-57804

    Issue in Reprocessing Multiple Files where User IDs are getting changed Fix Details:

    The User Interface is updated to handle multiple files for reprocessing and provide results for each of the files. Also, a validation is enforced to not allow more than 25 files to be used for bulk reprocessing.

  • L3REQ-57682  

    AS2 API failure after upgrading to 623 hotfix

    Fix Details:

    We have added the NONE option for MDN Encryption field in the AS2 Protocol setup APIs for both CREATE/UPDATE, Partner/Application.

  • L3REQ-52586

    Path Traversal Vulnerability Allowing Unauthorized Access to Server Files in Community Manager

    Fix Details:

    Implemented strict validation for all input parameters to ensure only expected values are processed. Restriction to special characters repeating to secure the (/pcm/reports/download-file) download API from path traversal attacks, ensuring the provided parameter cannot contain the .. patterns as such.

  • L3REQ-52642

    Creation of Mailboxes from PCM overriding latest Mailbox created through B2Bi

    Fix Details:

    The Creation of Mailboxes from Community Manager’s Partner and Application

    Menu for B2BiFTP, B2Bi-FTPS, B2Bi-SFTP Partner to Hub Connection, Mailbox Protocols overwriting the existing B2Bi mailboxes in MSSQL, DB2 has been fixed.

  • L3REQ-52823

    View Activity Shows unrelated rule data in File transfer Search

    Fix Details:

    The View Activity in File Transfers gets data relevant to the specific BP ID and Reprocess functionality also follows the same process.

  • L3REQ-53026

    Low Privilege User Could Delete Other Users

  • L3REQ-52589

    Low Privilege User Could Unlock and Activate Other Users in Community Manager Fix Details:

    We have added additional validations to the File Processor role for API level restriction the above reported APIs.

  • L3REQ-52580

    Restart workflow from PEMCM file transfer search not working

    Fix Details:

    The Activity Issue was resolved causing the SQL exception after successful reprocessing of the file.

  • L3REQ-55390

    Not able to create S3 partner in Community Manager logged in through username with more than 15 characters

    Fix Details:

    The AWS-S3 Partner/Application creation is modified to accept creation from the users whose username can be up to 30 characters.

  • L3REQ-56571

    Destination File greater than 2 MB is not opening in PCM File Transfers

    Fix Details:

    Customers can now configure the size allowed in application.yml file, for viewing the file in File Transfers menu. Any files more than the specified size would give a pop-up to download it and cannot be viewed directly.

    Note: The files need to be archived using source/destination file archive rules for this feature to work.

  • L3REQ-44730

    Adding timeout property to the PCM route in values.yaml

    Fix Details:

    Customers can now configure the time out as per their requirement in milli seconds in the application.yml file. All the API execution would use this parameter and time out if no response is received within the time limit.

  • L3REQ-56783

    PCM UI in PEM Standard 6.2.3 requires a password when merging partners.

    Fix Details:

    Partner/Application Connecting to Hub can use existing B2Bi username without password and select the Merge User check box.

  • L3REQ-56686

    Customer using PCM is unable to search the correlation values, DB2 SQL Error:

    SQLCODE=-433, SQLSTATE=22001

    Fix Details:

    The correlation search issue from DB2 database set up has been resolved and our File Transfer Search engine can fetch the desired result set without facing any SQL error with up to 1MB correlation data in CLOB columns.

  • PEM Standard Predefined Onboarding Activity Modifying
    The Partner Status change API was modified to not impact the protocol information. Note: The PEM Activity doesn’t have any changes.
  • L3REQ-55045:
     PEM Community Manager Polling Interval Fix The character limit in the Polling Intervals for Protocols has been increased to 50 characters. You can now create Polling Intervals Names up to a maximum of 50 characters and assign them for the Protocols. Protocols: Mailbox, B2Bi-ConnectDirect, AWS-S3, B2Bi-FTP, B2Bi-FTPS, B2Bi-SFTP, File System, HTTP/S.
    File Transfer Search Fix

     

    The File Transfers Search result was not providing accurate results, there was difference in the timestamps.

    Fix Details:

    The time zone used by B2Bi can be provided in the application.yml file of PCM, which enables time zone to be in sync and provides accurate results.

  • L3 Issue: L3REQ-52580, L3REQ-52639

    Multiple Reprocess of Files in Community Manager is logging out the user. Fix Details: 

    The issue was fixed, and we enforced a validation to not allow more than 25 files for bulk reprocessing.

  • L3REQ-58141

    PEM Username column is inconsistent in PEM Community Manager

    Fix Details:

    The column lengths for Last Updated By and Created By are updated and made consistent across protocols to match the allowed user’s username length in PEM CM application.

Known Issues:

  • PCM does not support creating AS2 Partners with 192-bit AES CBC PKCS5 Padding encryption algorithm as B2B APIs do not support 192-bit AES CBC PKCS5 Padding encryption algorithm, despite having a value for it in the SI Dashboard UI.
  • OnArrival polling interval option is provided but is not a valid one to use for Partners/Applications apart from Mailbox and Partner Connecting to Hub protocol types. PCM doesn’t support creating MQ Protocol Partner/Application modules with SSL. Note: Customers can manually provide the SSL details in SI dashboard/Business     Process for MQ to work with SSL.