hc1 is improving all the time. This page is an overview of the features and fixes in the latest release. Information about past releases is available in the pages below. 

If you aren’t seeing the latest improvements to hc1, you might need to clear your browser cache. For information on how to do this, go to Clearing Your Browser Cache in the System Requirements and Browser Information section.

If you ever have trouble logging into hc1, make sure that the URL you are using is in this format: https://yourhc1environmentname.hc1.com. Don’t bookmark the Sign In page; that is a different URL and may change from release to release.

January 22, 2019: hc1 CRM 7.5.6

In response to your feedback, we have delivered improvements related to organization and contact rules:

  • Rules can’t change parent-child organization relationships. Before, rules firing on organizations would sometimes remove an established parent-child organization relationship. We limited the organization rules code to only be able to update field values on parents and children and leave the relationship between the organizations alone.
  • Rules work on organizations and providers imported from hc1 ProviderView. Before, rules that included user-defined fields wouldn’t work on organizations and providers imported from hc1 ProviderView, which only included hc1 standard fields. We changed how records from hc1 ProviderView are created in the hc1 CRM in order to account for user-defined fields.

For more information about child organizations, field update rules, or hc1 ProviderView, check out these pages:

January 17, 2019: hc1 CRM 7.5.5

In response to your feedback, we have delivered improvements related to child organizations:

  • Organization rules fire as expected on child organizations. If you are a sales rep belonging to one sales territory, hc1 fills in your name and territory for you whenever you create an organization, including child organizations. Before, hc1 saved the organization, filled in the sales fields, and then resaved the organization—a process that interfered with rules that trigger from the Sales Territory field to update other organization fields. We changed this process to require only one save, which allows organization rules to run properly.
  • Custom lists display sales reps and territories for child organizations. Before, the Sales Rep and Sales Territory columns in custom lists were blank for child organizations, leading users to believe that these organizations lacked this information. We fixed the custom list code to display this information as expected.

For more information about child organizations and field update rules, check out these pages:

January 14, 2019: hc1 CRM 7.5.4

In response to your feedback, we have delivered a change for creating organizations:

  • When you create an organization and save it, the complete organization information is displayed on screen as expected. After we streamlined the organization creation process in December, a new organization record would go blank after you clicked Save, and you would have to search for the organization you just created to add activities or opportunities to it. This issue occurred because the organization ID wasn’t being passed through to the record display properly, which meant the displayed URL was incomplete as well. Now that we’ve fixed the issue, you no longer have to do any extra searching to complete your organization workflows. Also, the address bar now displays the correct link for the new organization after you click Save.

For more information about creating accounts or clients (otherwise known as organizations), check out this page:

January 9, 2019: hc1 CRM 7.5.3

This release delivers a fix for Quick Create tasks on contacts:

  • Users can create activities on contact records with Quick Create components without error. Before, users would sometimes see the “An error has occurred. Please contact the system administrator” message when they tried to, for example, log a call from a contact record. This error occurred when the contact was part of an audience for a campaign that the user didn’t have access to. We’ve changed the code to better handle campaign information when validating user permissions for Quick Create components, so users can now log calls, add running comments, or create other activities as expected.

For more information about using Quick Create components, check out these pages:


  • No labels