Question 2 Replies 159 Views × Close popover Bob Reawaruw (BobReawaruw) Atos PEGA Architect Atos NL View Profile Send Message BobReawaruw Member since 2018 54 posts Atos Posted: September 2, 2020 Last activity: September 7, 2020 Posted: 2 Sep 2020 4:47 EDT Last activity: 7 Sep 2020 13:21 EDT Solving skip new/create harness using Branches Also see: https://collaborate.pega.com/question/cannot-skip-new-harness After creating a new Case Type, check "Skip new harness" in the Case Type settings. However, new harness keeps showing up when creating a new case. Do a save as, of the "pyStartCase" of a Case Type with the check "Skip new harness" already enabled. And save this rule to your new Case Type class. ***Edited by Moderator: Pallavi to update platform capability tags*** Pega Platform 8.4.1 Case Management × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Posted: 7 months ago Posted: 3 Sep 2020 3:24 EDT × Close popover Marc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. FR View Profile Send Message MarcLasserre_GCS PEGA replied to BobReawaruw Hello, Is it specific issue with branches? I never had this problem. Do you have the same issue outside branches? Posted: 7 months ago Posted: 7 Sep 2020 13:21 EDT × Close popover Bob Reawaruw (BobReawaruw) Atos PEGA Architect Atos NL View Profile Send Message BobReawaruw Atos replied to MarcLasserre_GCS No :) When you edit your casetype settings via the case designer, the rule will be saved in a pre-defined application specific ruleset. Outside of your branches. Thus, when merging your branche, the new version of pyStartCase will not be merged.