Question2Replies151Views Fedotochkin Ilya Member since 2011 21 posts Lanit Posted: 5 years agoLast activity: 5 years 4 months ago Closed Solved Changes in PartyNewSetup activityWe've updated PRPC 7.1.7 to 7.1.8 and now we can see changes in activity PartyNewSetup - precondition on step 3.In previous version it was pxRequestor.pxUserIdentifier != "" -> Continue Whens, else -> Exit iteration, now it is @(Pega-RULES:Default).isBatchRequestor(tools) -> Exit iteration.We have an agent that creates a case. While creation case was filling with work parties. In 7.1.7 it works good, in 7.1.8 it doesn't work because of when condition.Now we've resaved this activity and reverse changes in this precondition. What problems we can face because of these changes?***Updated by moderator: Marissa to close post***This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post. Case Management Low-Code App Development Upgrades ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! 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. Accepted Solution Posted: 5 years agoMARIK PEGA replied to Fedotochkin IlyaHello Ilya,The intention of that precondition is to say, "If the party is only specified as Visible On Entry but it is not Required, then if we are in an agent don't create it because 'visible' has no meaning."If you want your agents to create cases with parties, simply check "required" in the workparty rule as well. Posted: 5 years agoFedotochkin Ilya Lanit replied to MARIKHi Ken,Thanks for your reply, it works fine now with "required" checkbox.