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.
We have added the ability to select a default Peer Review Document for a System. To select it, open the CCR Systems page, and pick the desired Document from the dropdown.
Starting today, we have release the new CCR view page to beta users!
As the view page contains a lot of functionality, we are giving users the ability to toggle their session between the new UI and the classic UI view pages. Your sessions will default to the classic UI for now, but beta users will see a "View in New UI" button in the nav bar for Tier 0 and 1 CCRs:
Similarly, the new UI page will have a "View in Classic UI" button at the top:
CCR Beta Users will now be directed to the Angular Transition CCR page for markENVComplete and passPeerReview transitions. Other CCR transitions will go into beta soon.
Please raise any issues or feedback here or in your regular support channels.
As of today, the Angular Clone CCR page is now live for CCR Beta Users. Beta testers will be sent to the Angular clone page from anywhere you would normally clone a CCR. No existing functionality will be lost.
Any issues or feedback can be reported here or in your regular support channels.
Many thanks to our CCR UI beta testers! If you would like to join the beta tester program, you can enable the checkbox on your CCR user page here.
Last year we introduced our new angular-based View page for CCR as part of the UI refresh for the application. This has been used very effectively by close to 1000 users around the world as the default UI for viewing CCR, and as a result we're getting ready to completely disable the "classic" View page.
CCR Client ItemSets now have a "stale" cut-off time. When a client-bound ItemSet is created in CCR, a user has 24 hours to deploy it to any environments. After 24 hours, this ItemSet is no longer deployable or downloadable. The deploy links will be disabled and instead the user will notice a "Refresh ItemSet" option which will create a new ItemSet. Users can then use this fresh ItemSet to deploy their changes, see below:
Now users can filter the CCR table by multiple conditions for the CCR tables displayed on the home page and the CCR tab of the System Details page.
Previously users were only able to filter the rows by one condition at a time. This made it cumbersome for users to quickly find CCRs that they knew met multiple conditions, as they would have to choose the condition that would produce the least number of results for them to then manually filter through.
By views
.png)
.png)
.png)
