Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Marta Anna Vitulano (MartaAnnaV)
Cornèr Banca SA

Cornèr Banca SA
CH
MartaAnnaV Member since 2017 2 posts
Cornèr Banca SA
Posted: Mar 16, 2018
Last activity: Mar 16, 2018
Posted: 16 Mar 2018 5:25 EDT
Last activity: 16 Mar 2018 11:55 EDT
Closed

Branches and circumstancing issue

Hi,

in our enterprise environment we have different projects that have been developed in parallel on the same application so we are using branches.

We noticed a "strange" behaviour with circumstanced rules:

Scenario 1

  1. we have to modify a circumstanced version of a rule so we save it in a branch
  2. we launch our application and everything is ok: it uses the base or circumstanced version of the rules according to the expected behaviour

Scenario 2

  1. we have to modify the base version of a circumstanced rule so we save it in a branch
  2. we launch our application and it uses only the base version (present in the branch) and never the circumstanced one. Our impression is that the circumstanced version of the rule it is not seen by PEGA anymore

The workaround we found to solve the issue of Scenario 2 is to save all circumstanced versions of the rules in the branch even if we have no modification.

According to your experience what is the correct approach to solve the problem?

Do you face a similar scenario? Is this a standard behaviour when you use branches and circumstances?

Thanks in advance.

Regards,

Marta

To see attachments, please log in.
Data Integration

Posted: 6 years ago
Posted: 16 Mar 2018 11:10 EDT
Mohammad Asif Hasan (Mohammad_Asif_Hasan)
EPAM Systems, Inc.
Mohammad Asif Hasan
EPAM Systems, Inc.
ES

Hi @MartaAnnaV,

Thanks for posting on PSC.

It's an expected behaviour as per my knowledge, branch rule-set to allow multiple teams to work in parallel without affecting other teams' work.

So to have more clarity, you're using "Projects" term above as working with the different team on same application? Correct me, If I am wrong.

As per my knowledge, it's correct and expected approach. In any application, there be "n" numbers of circumstanced versions for all the rules.

Hope it helps in your business requirement. Kindly notify by marking this post as answered/helpful for larger Pega audience and tracking purposes.

Regards,

Asif

To see attachments, please log in.
Posted: 6 years ago
Posted: 16 Mar 2018 11:55 EDT
Marta Anna Vitulano (MartaAnnaV)
Cornèr Banca SA

Cornèr Banca SA
CH

Thanks for your reply.

You read correctly the "Projects" term, but according to your response we still don't understand why we need to copy all circumstanced version of the rule only if we change the base rule and not if we change a circumstanced one (only in Scenario 2).

So do you confirm that resave circumstanced rules in the branch, even if no modification is needed, is the correct approach to solve the problem?

Thanks,

Marta

To see attachments, please log in.

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