@Hugh Badian  - I suggest you add the tag 'CCR' to your question.

The %Studio.SourceControl.CCREventHandler.cls is included in the CCR Client Tools so you should be able to open that on any CCR Client system to look at the methods that you can extend to do things on ItemSet download or Refresh.  It has a lot of built-in documentation.

Is there a specific thing that you are looking to accomplish with a CCREventHandler?

@Vitaliy.Serdtsev  - you make a fair point about downloading the full Eval kit just for a few pieces of it ... unfortunately that is the only distribution mechanism that I know of currently available for non-supported customers.

Thank you for all the time you've spent over the years helping to find ways to make Caché more robust!!  It sounds like you've been able to identify quite a few areas of improvement.  There was significant effort put into streamlining things and solving known issues in the rebirth of Caché as InterSystems IRIS.  You might find it interesting to download the Community Edition (IRIS version of the SU kit but much more powerful with fewer restrictions) and see if the bugs you reported are still present there or not.  What do you think about that approach?

I got clarification that we still create an SU version of Caché which is available in the WRC because some of our large partners/APs rely on it for people to learn on (which makes sense).  Obviously we won't want new prospects playing with it, which is why it is no longer publicly available and instead we provide the InterSystems IRIS Community Edition.

@Vitaliy.Serdtsev - you could download the Community Edition of InterSystems IRIS from evaluation.InterSystems.com and just install Studio from that if you wish.  Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition (which is freely available to everyone)?  

@prashanth ponugoti - a couple of things to look at:

1) When you open the first link in /csp/healthshare does it open for you after authenticating?

2) Is your /csp/test web application definition set to work in the same namespace as /csp/healthshare?

3) Is a copy of your person.csp file moved to the web application root that you defined for /csp/test?

Hope that helps get you started on finding a solution.