The InterSystems Change Control Record (CCR) application is used to help manage changes to deployed applications, both within InterSystems as well as at healthcare end-user sites (i.e. TrakCare and HealthShare customers). It is a tool that helps to document changes, enforce best practice workflow, and automate source control integration and change promotion between different environments.
The CCR tag on the InterSystems Developer Community is intended to allow CCR users around the world to connect with each other to ask how-to questions, share best practices, and engage with InterSystems developers who maintain the application and tools. NOTE - usage of CCR is limited to sites implemented by or hosted by InterSystems (it is not available to all customers of InterSystems products).
When posting a CCR related Question or Article to the Developer Community, please select the Group based on your product (HealthShare or TrakCare) and then select "CCR" as one of the tags.
CCR users can now take advantage of an enhanced syntax for substituting pre-defined tokens with live URL links within phase-related text fields. In addition to the existing <env> token which automatically updates to reflect the Environment of the relevant CCR Record, CCR now introduces three new keywords: <smp> , <smpPrefix> , and <homepage>.
We're excited to announce the first-ever UI update for CCR Client Tools. The Client Tools UI has been upgraded to match the modern CCR UI, aiming to create a more seamless experience across both applications. The color scheme, fonts, and style elements have all been updated accordingly in the new UI:
to handle empty tags in output xml file from %Persistent. But this parameter only applies to %String property. What if a class has other types of properties, like %Stream (for holding large chunk of data). What is the recommended handle if we cannot use XMLIGNORENULL here?
What is the best way to develop Angular applications while working with CCR?
CCR peer reviewers require submitting Angular source files, so that a peer reviewer has something readable to review. However, CCR environments require that you deploy compiled Angular applications to them.
CCR now includes an AI-powered 'CCR Assistant', available to beta testers. The CCR Assistant helps you quickly get answers about common CCR workflows, terminology, or best practices. Every response includes references to relevant ICC Training courses, making it easy to dive deeper into any topic. As a future improvement, the links will point directly to the specific page of the ICC Training PDF that was used to generate the response.
As part of improvements regarding CCR usage and usability, certain transitions are now blocked when a CCR Record has undeployed ItemSets for required Environments.
At READY 2025 we will have a CCR User Group Breakfast for HealthShare and TrakCare customers on Wednesday at 7:30am (presentation starts at 7:45am). Topics will include:
Review of Self Service Best Practice Dashboard
Recent CCR New Features and Enhancements
Active CCR Feature Beta Programs
Summer and Fall Roadmap
Q&A
We will meet in the Jackson meeting room. Visit the Meeting Counter to have it added to your schedule or comment below to request an invite.
Over the last year, the CCR development team has prioritized changes to the CCR application to better expose and encourage best practices for using CCR. This article will highlight some of the areas that we've focused on:
Organization Dashboard
System Alerts
Branch Hygiene
In each of these areas, we have increased the visibility of potential CCR usage issues and given users tools to proactively address them.
Organization Dashboard
We have continued to build out the available information on the Organization details page
Year
.png)