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

 Prasanna Kumar (PrasannaK8545)

IN
PrasannaK8545 Member since 2015 15 posts
Posted: Aug 18, 2015
Last activity: Aug 18, 2015
Posted: 18 Aug 2015 0:16 EDT
Last activity: 18 Aug 2015 9:56 EDT
Closed
Solved

Check Out, Branching and Circumstancing

Hi Guys,

According to my understanding both checkout and branching functionalities along with circumstancing are used for same purpose alone. Which are for coordinated and collaborative work environment between different operators working on an application. My question is how each of those differ or what is the need for three various categories for same purpose?

Thanks in advance

Prasan

To see attachments, please log in.
Low-Code App Development
Case Management
Updates
Installation and Deployment
Data Integration
User Experience
Security
System Administration
Reporting

Accepted Solution

Posted: 9 years ago
Posted: 18 Aug 2015 2:18 EDT
Rajiv Nistala (nistr) Senior Manager - Engineering
Pegasystems
IN
  1. Checkout - When your changes need to be isolated just for yourself and not shared with other users.
  2. Branching (or checkout to branch) - When your changes need to be isolated but can be shared with other specific users and also moved around from Pega environment to another.
  3. Circumstancing -When the runtime data or value of one or more properties determines which rule should be picked up for execution. Example: In report definition, the SQL function is dependent on the underlying database vendor and is therefore circumstanced based on that.
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