Skip to main content
Contact a Moderator

Question

2
Replies
644
Views
 Bob Reawaruw (BobReawaruw) Atos PEGA Senior Architect
Atos
NL
BobReawaruw Member since 2018 68 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
Closed

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
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 1 year ago
Posted: 3 Sep 2020 3:24 EDT
Marc Lasserre (MarcLasserre_GCS) PEGA Senior Principal Engineer, Technical Support
Pegasystems Inc.
FR

Hello, 

Is it specific issue with branches? I never had this problem. Do you have the same issue outside branches?
Posted: 1 year ago
Posted: 7 Sep 2020 13:21 EDT
Bob Reawaruw (BobReawaruw) Atos PEGA Senior Architect
Atos
NL

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.

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

Pega Collaboration Center 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