Requesting Details about Hot Fixes available in our system
Hi,
Our application is on Pega 7.3.1 version and production date is near.
While analyzing the Hot fixes installed in our system, we realized that some Hot fixes were committed but we couldn't find any reference or team member who apply those.
Appreciate if anyone can provide the functionality details of below hot fixes and also pointed out parent - dependent relationship among them (since some hot fixes might be dependent jar files to a parent hot fix)
|
HotFix_ID |
Description |
|
HFIX-44984 |
Need DF thread hang fix ported to 7.3.1 |
|
HFIX-43363 |
MIDAS DM-Hot fix request (Get method support for Stream Dataset) |
|
HFIX-46535 |
Need the PegaAESRemote Client 07-31-02 patch for Pega 7.3.1 GA |
|
HFIX-44345 |
MIDAS DM: Realtime data flow goes into pause state intermittentl |
|
HFIX-45435 |
Need the PegaAESRemote Client Rules for Pega 7.3.1 GA |
Hi,
Our application is on Pega 7.3.1 version and production date is near.
While analyzing the Hot fixes installed in our system, we realized that some Hot fixes were committed but we couldn't find any reference or team member who apply those.
Appreciate if anyone can provide the functionality details of below hot fixes and also pointed out parent - dependent relationship among them (since some hot fixes might be dependent jar files to a parent hot fix)
|
HotFix_ID |
Description |
|
HFIX-44984 |
Need DF thread hang fix ported to 7.3.1 |
|
HFIX-43363 |
MIDAS DM-Hot fix request (Get method support for Stream Dataset) |
|
HFIX-46535 |
Need the PegaAESRemote Client 07-31-02 patch for Pega 7.3.1 GA |
|
HFIX-44345 |
MIDAS DM: Realtime data flow goes into pause state intermittentl |
|
HFIX-45435 |
Need the PegaAESRemote Client Rules for Pega 7.3.1 GA |
|
HFIX-42160 |
New Feature to enable movement of files from AWS to Cassandra |
|
HFIX-43278 |
Data Flow Exception Handling in Pega Marketing |
|
HFIX-44635 |
MIDAS DM: Real time data flow, Initialization failed |
|
HFIX-43753 |
Adding additional logging on the membership listener |
Thanks and Regards,
Prasith.
Pegasystems Inc.
GB
If you get the DL with one particular HF this can add some dependent HFs based on the change implemented. These dependent HFs can be installed if required and then will be shown as Committed while the commit operation was not selected. Once you roll back last HF that introduce such dependency you will see those shown as committed are also removed. So, this is false positive and and being addressed in higher Pega version.