Question

Bulk Checkin to Withdraw Fails Due to Warnings

Some of our developers want to bulk checkin rules that they are withdrawing - cleaning up old code no longer in use. However, a lot of these rules have warnings on them that require fixing before checking in. Example: the warning about filling out the usage field under the History tab of the rule.

If the developer manually withdraws the rules one at a time they are allowed to withdraw without fixing the warnings. Bulk checkin, however, does not seem to ignore these warnings for withdrawn rules. I understand fixing these warnings if the rule is being checked in as Available. However for withdrawn rules it would be nice to ignore these warnings on bulk checkins.

We are running Pega 7.4. From the Pega perspective do people think this is how bulk checkin is supposed to work or not? Thanks in advance for the help.

***Edited by Moderator: Lochan to tag SR to post***

Group Tags

Correct Answer
December 30, 2019 - 12:15pm

As it turned out this was entirely custom code.  The activity PreCheckInDialog runs when you check in a single rule to show the dialog box for the checkin comment.  The activity PreCheckIn does very similar things, but runs for bulk checkin.  These are normally out of the box activities but we customized them to check for things that we want to add custom warnings for, such as if a rule does not have any text for the Description/Usage on the history tab.

The solution to my problem here was that we needed to check the property pyRuleAvailable == "yes" on the rule we are validating.  That way if the developer withdrew the rule, we do not validate these warnings.  We were checking this in PreCheckInDialog but not in PreCheckIn.  Due to this we were able to check in the rules one at a time withdrawn, but not with bulk checkin.

Comments

Keep up to date on this post and subscribe to comments

December 13, 2019 - 10:04am

I created SR-D69046 for this.

December 27, 2019 - 6:12am

Hi @DaytonP5

From the SR notes I read that the root cause of the issue was found out and the issue was resolved. Glad to know its fixed.

If you could share the resolution with the community, it would help community users who might come across the same question.

Thanks.

Vidyaranjan | Community Moderator | Pegasystems Inc.

December 30, 2019 - 12:15pm
Response to Vidyaranjan

As it turned out this was entirely custom code.  The activity PreCheckInDialog runs when you check in a single rule to show the dialog box for the checkin comment.  The activity PreCheckIn does very similar things, but runs for bulk checkin.  These are normally out of the box activities but we customized them to check for things that we want to add custom warnings for, such as if a rule does not have any text for the Description/Usage on the history tab.

The solution to my problem here was that we needed to check the property pyRuleAvailable == "yes" on the rule we are validating.  That way if the developer withdrew the rule, we do not validate these warnings.  We were checking this in PreCheckInDialog but not in PreCheckIn.  Due to this we were able to check in the rules one at a time withdrawn, but not with bulk checkin.