Question2Replies56Views×Close popoverBob Reawaruw (BobReawaruw) Atos PEGA Architect Atos NL View Profile BobReawaruw Member since 2018 51 posts Atos Posted: September 2, 2020Last activity: September 7, 2020Posted: 2 Sep 2020 4:47 EDTLast activity: 7 Sep 2020 13:21 EDT Solving skip new/create harness using BranchesAlso see: https://collaborate.pega.com/question/cannot-skip-new-harnessAfter 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 popoverFacebookTwitterLinkedinEmail Copy Link Copied! Posted: 4 months agoPosted: 3 Sep 2020 3:24 EDT×Close popoverMarc Lasserre (MarcLasserre_GCS) PEGA Principal Software Solutions Engineer PEG FR View ProfileMarcLasserre_GCS PEGA replied to BobReawaruwHello, Is it specific issue with branches? I never had this problem. Do you have the same issue outside branches? Posted: 4 months agoPosted: 7 Sep 2020 13:21 EDT×Close popoverBob Reawaruw (BobReawaruw) Atos PEGA Architect Atos NL View ProfileBobReawaruw Atos replied to MarcLasserre_GCSNo :)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.