Question

Incorrect Pega Unit Warnings

Issue:

Even though a test case is created for a rule (say a data page), the unit test case warning appears on the rule. This happens when branches are used.

Detailed explanation:

  • Created a data page and updated the rules with a report definition source in a branch ruleset (say XYZ_MYBranch:01-01-01.
  • Before checking, ran the data page and created the test case in the respective testing branch ruleset (say XYZAUT_MYBranch: 01-01-01.
  • After saving, the Pega unit warning does not go away.

Showing below that both data page and its test cases are in the same branch but in respective rulesets (see img1&2 in attachments).

Alternative:

  • Merge branch and then check out the data page and resave to remove the warning.

***Edited by Moderator: Pallavi to update platform capability tags***

Correct Answer
November 7, 2018 - 4:57pm

Hi Balaji,

I submitted a bug to our internal teams here to take a look at this. When I hear any feedback on it, I'll let you know via this post.

Thank you!

Comments

Keep up to date on this post and subscribe to comments

Pega
November 2, 2018 - 2:56am

Hi Balaji,

Guardrail warnings are calculated on save of the rule. Please save the data page which is in branch ruleset once after the creation of the test case. Then it will re-calculate the warnings and show it. If a pegaunit is available for the rule then it will not show pegaunit warning.

Thanks,

SubbaRao.

December 24, 2018 - 12:59pm
Response to TATIKONDA

Even after saving, this behavior is observed.

November 7, 2018 - 4:57pm

Hi Balaji,

I submitted a bug to our internal teams here to take a look at this. When I hear any feedback on it, I'll let you know via this post.

Thank you!

Marissa | Community Moderator | Pegasystems Inc.