Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Additional connector comes out of breadcrumb on screenflow

SA-45721

Summary



The application is configured so as to skip assignment conditionally. When Fork decision shape is used for this, extra connector link is observed in the screen flow.


Error Messages



Not Applicable


Steps to Reproduce

  1. Configure a screen flow Start > Assignment 1 > Assignment 2 > Decision of type Fork with When configured > one way of decision(Assignment 3) > other way of decision(Utility ) > End.
  2. Enable Navigation link is selected on Assignment 1,2,3.
  3. Enable Navigation link is disabled at Decision and Utility.
  4. Include When rule that has a property evaluation say .pxRequestor.pxOrganization = “Test”
  5. At runtime, Assignment 1, 2 are shown , after this the connector as well is shown, but not Assignment 3.
  6. Notice Assignment3 is generated in Document Object Model (DOM) and is hidden.




Root Cause



A defect in Pegasystems’ code or rules: Raised a bug internally.

Resolution



Perform the following local-change steps:

Scenario 1: When condition to False:
When the flow is run & if the When condition is evaluated to False, the Else path is taken which brings the below breadcrumb which is valid:





Scenario 2: When condition to True:
When the flow is run & if the When condition is evaluated to True, the normal path is taken which brings the below breadcrumb which has an additional connector after Assignment 2:




Add the below lines of code in UserWorkForm in order not to display the additional connector:
Note that the local-change is given for this flow scenario only.

<script>
$(document).ready(function(){
var screenFlows = $("#ScreenFlowTabs").find("ul li");
if (screenFlows.length > 0) {
var lastHidden = screenFlows.last().hasClass("hidden");
if (lastHidden) {
$(screenFlows[screenFlows.length-2]).css('border-top', 'none');
}
}
});
</script>


After the change, the breadcrumb looks like:



At runtime, when the When condition is evaluated to False after Step 1 which takes the Else path, the below breadcrumb gets generated automatically:


Suggest Edit

Published April 12, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us