Question
Cognizant
GB
Last activity: 6 Dec 2023 12:17 EST
SR-D26085/SR-D26231 : Flow Id Corruption prior to PEGA 8.4 while adding new flow via pydefault, is this now fixed ?
Hi,
We have been previously advised via SR-D26085 (unable to find on PDN anymore) the below while trying to add a new flow via pydefault rule. Can anyone please advise if this has now been fixed and its possible to update pydefault directly without using Case Designer.
PEGA’s Advice /Suggested Workaround
“It is not recommended to insert a new flow in between existing flows from the pyDefault case rule form which will mess up the generated Flow Ids.
Here is a work around to do so, follow steps below to add a new flow in between -
- Open case in case designer
- Add a new process to the stage to which you want to include new flow
- Re-order this flow to bring it to its correct order position, and save the case type. This will retain all the pxFlowID intact.
- Open pyDefault case rule form and use the place holder of the newly flow to add the actual flow.”
----------------------------------------------------------------------------------------------------------
‘Hi All
I had a series of discussions with case management engineering team and we have come to a conclusion that the issue is fixed in Pega 8.4 which is yet to release.
however as of now to deal with parallel development issues we have two approaches.
Hi,
We have been previously advised via SR-D26085 (unable to find on PDN anymore) the below while trying to add a new flow via pydefault rule. Can anyone please advise if this has now been fixed and its possible to update pydefault directly without using Case Designer.
PEGA’s Advice /Suggested Workaround
“It is not recommended to insert a new flow in between existing flows from the pyDefault case rule form which will mess up the generated Flow Ids.
Here is a work around to do so, follow steps below to add a new flow in between -
- Open case in case designer
- Add a new process to the stage to which you want to include new flow
- Re-order this flow to bring it to its correct order position, and save the case type. This will retain all the pxFlowID intact.
- Open pyDefault case rule form and use the place holder of the newly flow to add the actual flow.”
----------------------------------------------------------------------------------------------------------
‘Hi All
I had a series of discussions with case management engineering team and we have come to a conclusion that the issue is fixed in Pega 8.4 which is yet to release.
however as of now to deal with parallel development issues we have two approaches.
1. To create different applications. (procedure was communicated in my earlier mail)
or
2. As you are now aware of the pyDefault functionality, use it with precaution and make the necessary changes accordingly'
***Edited by Moderator Marije to add Support Case details***
Accepted Solution
Updated: 6 Dec 2023 12:17 EST
Pegasystems Inc.
GB
@Somak Banerjee I checked and SR-D26085 is not a valid support ticket ID so I cannot find any evidence that for the 7.4 any FDBK or BUG was officially logged.
.
I did find INC-A26849 in which you are involved. It was closed with the following:
------------------------------------------------------------
Ticket Analysis/Summary:
- In Pega, changes are made through BUG or Feedback items. Sometimes, functionality might be changed with new releases as well. - The referenced cases do not have any such items connected, so we cannot confirm or deny if any changes were made. - As the issue was raised for Pega 7.4 and currently used version is Pega 8.8, it's possible that the behavior was changed in some upgrade in the meantime. - Somak and Jamielee will create an example use case to check if the behavior matches their expectations. - If needed, we will create appropriate items to change the behavior.
Next Steps:
-
Somak/Jemielee to create a example case and check current behavior, and update if they would like to request official product changes
------------------------------------------------------------------------
@Somak Banerjee I checked and SR-D26085 is not a valid support ticket ID so I cannot find any evidence that for the 7.4 any FDBK or BUG was officially logged.
.
I did find INC-A26849 in which you are involved. It was closed with the following:
------------------------------------------------------------
Ticket Analysis/Summary:
- In Pega, changes are made through BUG or Feedback items. Sometimes, functionality might be changed with new releases as well. - The referenced cases do not have any such items connected, so we cannot confirm or deny if any changes were made. - As the issue was raised for Pega 7.4 and currently used version is Pega 8.8, it's possible that the behavior was changed in some upgrade in the meantime. - Somak and Jamielee will create an example use case to check if the behavior matches their expectations. - If needed, we will create appropriate items to change the behavior.
Next Steps:
-
Somak/Jemielee to create a example case and check current behavior, and update if they would like to request official product changes
------------------------------------------------------------------------
BUG-359540 (pxFlowID not updated properly when inserting new flow in process) was closed with no action with the following SME analysis:
"we have an option to reorder in Case Designer and we do not want to do any major change in case type rule form to handle this kind of scenario".
Accepted Solution
Updated: 6 Dec 2023 12:17 EST
Pegasystems Inc.
GB
@Somak Banerjee I checked and SR-D26085 is not a valid support ticket ID so I cannot find any evidence that for the 7.4 any FDBK or BUG was officially logged.
.
I did find INC-A26849 in which you are involved. It was closed with the following:
------------------------------------------------------------
Ticket Analysis/Summary:
- In Pega, changes are made through BUG or Feedback items. Sometimes, functionality might be changed with new releases as well. - The referenced cases do not have any such items connected, so we cannot confirm or deny if any changes were made. - As the issue was raised for Pega 7.4 and currently used version is Pega 8.8, it's possible that the behavior was changed in some upgrade in the meantime. - Somak and Jamielee will create an example use case to check if the behavior matches their expectations. - If needed, we will create appropriate items to change the behavior.
Next Steps:
-
Somak/Jemielee to create a example case and check current behavior, and update if they would like to request official product changes
------------------------------------------------------------------------
@Somak Banerjee I checked and SR-D26085 is not a valid support ticket ID so I cannot find any evidence that for the 7.4 any FDBK or BUG was officially logged.
.
I did find INC-A26849 in which you are involved. It was closed with the following:
------------------------------------------------------------
Ticket Analysis/Summary:
- In Pega, changes are made through BUG or Feedback items. Sometimes, functionality might be changed with new releases as well. - The referenced cases do not have any such items connected, so we cannot confirm or deny if any changes were made. - As the issue was raised for Pega 7.4 and currently used version is Pega 8.8, it's possible that the behavior was changed in some upgrade in the meantime. - Somak and Jamielee will create an example use case to check if the behavior matches their expectations. - If needed, we will create appropriate items to change the behavior.
Next Steps:
-
Somak/Jemielee to create a example case and check current behavior, and update if they would like to request official product changes
------------------------------------------------------------------------
BUG-359540 (pxFlowID not updated properly when inserting new flow in process) was closed with no action with the following SME analysis:
"we have an option to reorder in Case Designer and we do not want to do any major change in case type rule form to handle this kind of scenario".