Question
Pegasystems Inc.
US
Last activity: 13 Oct 2016 11:53 EDT
Grid Repeat Layout with Master-Detail, how to discern between user clicking Save or Discard in post-action activity
Client is on Pega 7.1.9.
We have implemented a Grid Repeat Layout with Master-Detail row editing in expandable rows. We have configured a post-action activity to run in the flow action that is configured in the row operation. In running the tracer, we see that the post-action activity is being run when the user clicks the Save button, when the user clicks the Discard button, and when the user expands a different row. Also in the tracer, I see that there isn't anything in the parameter page that would indicate the action the user took.
I then looked at the sample in the UI Gallery. It does not have a post-action activity configured, so I did a private checkout of the flow action and added a call to an activity. I see the same behavior; the activity seems to be invoked on the same 3 triggers: Save button, Discard button, expand a different row.
Is there a way to determine what action the user took, or do I need to open an SR for a product fix?
Accepted Solution
Pegasystems Inc.
US
We found that the javascript sends a parameter named "Navigation", which contains the value "SUBMIT" when the user clicks the update button, and "JUMP" when the user clicks the cancel button.
This did allow us to skip our post-processing logic based on that parameter value. The next problem was that when a row is expanded and another row is then expanded, an "UPDATE" was being sent for the already open row, which was undesireable. To prevent that, we class-specialized the pyGridRowDetials section, and updated the button id for the update button to something other than the default. This only worked for us because we also didn't have any desire for the buttons to be disabled initially. If you change the button id, and leave the buttons disabled, the javascript won't be able to find the button to enable it when a user changes values for that row.
Using any other button type didn't provide any solution. The javascript function that is called by pzModalButton is "Grids.getActiveGridDetails(event).submitModal(event)", which we could not seem to reproduce using an OOTB button.
Areteans Technologies
AU
You can disable the flowaction default button and create custom button in your section and configure the activity in submit button alone.
Blue Rose Technologies GmbH
DE
You can replace the pzModalButton with a OOTB button and add a run script action to submit the modal dialog. Please configure as below,
Run Script -> doModalAction
parameters
name -> submitModalDlgParam value -> script:pega.u.d.submitModalDlgPar
name-> event value-> script:event
Blue Rose Technologies GmbH
DE
Ideally "Discard" action wouldn't invoke the post processing activity of the flow action.
We submit the flowaction data in case of Save (or) when user navigates between rows. This is to keep the UI and the clipboard upto date. Can you please let me know your exact requirement ?
Accepted Solution
Pegasystems Inc.
US
We found that the javascript sends a parameter named "Navigation", which contains the value "SUBMIT" when the user clicks the update button, and "JUMP" when the user clicks the cancel button.
This did allow us to skip our post-processing logic based on that parameter value. The next problem was that when a row is expanded and another row is then expanded, an "UPDATE" was being sent for the already open row, which was undesireable. To prevent that, we class-specialized the pyGridRowDetials section, and updated the button id for the update button to something other than the default. This only worked for us because we also didn't have any desire for the buttons to be disabled initially. If you change the button id, and leave the buttons disabled, the javascript won't be able to find the button to enable it when a user changes values for that row.
Using any other button type didn't provide any solution. The javascript function that is called by pzModalButton is "Grids.getActiveGridDetails(event).submitModal(event)", which we could not seem to reproduce using an OOTB button.