Guest users: A new feature for consultancies (SIs and PDO partners) and teams working with them
A typical Salesforce implementation project often proceeds as follows:
A company hires a consultancy, which assigns experts to the project.
After configuring the org, the consultancy hands it over to the client's in-house team.
During this process, trained Consultants and Developers may use specific tools to facilitate a proper development lifecycle.
This approach can exclude customer-side Admins from the configuration process or create issues due to an unsynchronized release cycle of metadata changes.
🤝
In response to this challenge, we've developed a licensing model that benefits both consultancies and their customers. We've also expanded the identity and access management capabilities of our product accordingly. Now, customers on the “Professional” and “Enterprise” plans can invite their consultancy team members to use Hutte without incurring additional license costs.
With these improvements, Hutte offers an attractive way for SI and PDO partners to collaborate with their customers on their Salesforce implementation or their ISV product.
This feature is particularly beneficial during the implementation phase when a large number of Consultants and Developers may need access to the customer's environment.
It streamlines and enhances the development lifecycle efficiency.
After the org is transferred, customers can continue the development lifecycle without disruptions.
Improved refresh Pool Org functionality
In December, we introduced a new functionality that refreshes metadata in Pool Scratch Orgs. We enhanced the usability by incorporating a toggle directly into the "Take from pool" dialogue. This toggle only appears when a Pool Org's metadata is behind the tip of the Git branch from which it was created.
Refresh a Sandbox from another Sandbox
Did you know that you can create or refresh a Sandbox not only from Production, but also from a Sandbox of the same license?
This process has the benefit of copying over metadata – and unlike refreshing from Production – it also includes data. This feature can be useful for seeding your Developer Sandboxes with data and transitioning away from long-living Developer Sandboxes.
Our customers frequently use this feature when using Sandbox Pooling. In this case, the Org from which Pool Orgs are periodically refreshed can be set in the pool settings. Moreover, we have now implemented the option to select a “Source Org” from which to refresh any Sandbox. This option is available in the dialogue when refreshing an individual Sandbox in Hutte.
Other value-added enhancements we’ve made
Organizational and project setup/onboarding: Streamlined and design improvements.
Enhanced user experience for setting up and refreshing Hutte’s integration with Bitbucket Server.
Bug fix: Applied branch name template when taking a Scratch Organization from the Pool.
Bug fix: Displayed the correct package build version.
Improved various error messages throughout the application.
hutte.yml: The DevHub authentication token is now available to push script.
Kickstart your 2024
Immerse yourself in the Hutte experience by signing in, creating an account, orrequesting a demo!
Harald is the Co-Founder of Hutte, bringing his vision of no-code DevOps to life. His passion enables teams and individuals to focus on what matters most – bringing value to the users they build for.
