Changelog
This release is jam packed with all kinds of Bookbuilder reporting goodies.
- We've added lots of new metric options to the Reps listing. You'll be able to see more information at a glance about how reps are engaging with their target book accounts and any assigned off book accounts. To access the new metrics, simply click on the new Manage Fields link and add what you need to the listing.
- You can now click on one of the bars in the Accounts per Rep chart and be taken directly to that user's Rep Report.
- We added an indicator to all Rep Coverage reports if data is being displayed for a deactivated User.
- We added the ability to refresh an existing market coverage report from the listing or when viewing the report.
- We'll now send emails upon report processing completion. We'll send an email to any users you have configured in the Recipients section in Settings or to the user who generated the report. You can opt out from Settings at any time.
- We also added in the ability to specify a custom date range for the coverage report.
- We made a slight change to the listing and added a Report Status column.
- Finally, we cleaned up a couple of rough edges in the market coverage report itself. Some of our tooltips were not displaying the correct information so we fixed it and cleaned up the look and feel of a couple of the other report components.
- We no longer include deactivated users in any of the target book report calculations or listings.
Had a quick fix to our Market Coverage report to address some users getting errors when trying to use certain fields for Fit or Timing.
🚨 EMERGENCY RELEASE 🚨
We had a regression on our Automation Builder Kit that prevented the UI from displaying any options when trying to access object fields.
MAJOR LAUNCH****
❗
❗
Today’s release is another big milestone in our efforts to help sales teams accelerate revenue with dynamic books. We are excited to announce Account Coverage - a new suite of tools that equips sales leaders with the intelligence they need to keep reps focused on their best accounts while also identifying and closing market coverage gaps.
Account Coverage includes:
- Rep Coverage - reports to help sales managers understand how their reps cover their accounts and identify coaching opportunities to better engage target accounts
- Market Coverage - reports to help sales leaders assess overall engagement with accounts in target segments and spot opportunities to drive more pipeline with better coverage of in-segment accounts
Account Coverage helps sales leaders see opportunities for more efficient use of rep efforts on higher potential accounts and dynamic books (and Bookbuilder) makes it easy to adapt reps books, distribute these accounts, and get them worked to generate pipeline.
We look forward to doing more in the future to make it easier for sales leaders to spot opportunities for better account coverage & then quickly take action to deploy their team to realize these opportunities.
🚨 EMERGENCY RELEASE 🚨
Emergency release to address Distributions/Retrievals listings not always showing Past Distributions or Retrievals.
Another small Bookbuilder release this week with a couple of bug fixes.
We fixed a bug in the Rep Listing where the Contact Reached (Avg) column displayed an incorrect value. This is now working as expected and apologies for any confusion this may have caused.
We discovered and fixed a batch process issue that would throw a 'Too many DML statements' error when processing a large number of usage events. This is now fixed and our apologies for not catching this sooner.
Small Bookbuilder release this week with a few improvements we couldn't wait to share.
You can now change the date range you're viewing data for just like in the Reps Working Activity Report.
We discovered we were not always calculating the number of owned accounts for each segment for a rep correctly. It's all fixed now though and we're sorry for any confusion this might have caused
We removed the ability to select User lookup fields as Enrollment Criteria. We saw some cases of customers adding pool user ownership as enrollment criteria which can mess up things like target book ownership reporting. Specifying that kind of criteria should really be done on the Distribution or Retrieval form.
This release is all about Bookbuilder Working Activities and Rep reports.
We've added the ability to create Working Activities for Events as well as Tasks. As you might expect, the Rep reports also now include any relevant Event data in them if you have Event Working Activities configured.
We re-labeled some columns and added some new metrics:
- "Accounts Engaged (%)" - The percent of total owned accounts that have at least 1 completed working activity associated to it
- "Contacts Reached (Avg)" - The average number of unique Contacts reached for worked accounts
This report got a lot of love this release.
- We added the same new metrics to the summary section of this report that we added to the Reps listing.
- This one is really exciting. You can now change the date range you're viewing data for.
- It's also now possible to sort the Account Summary Engaged and Unengaged lists by any configured column.
We also made it easier to add RecordTypeId conditions when configuring criteria in BookBuilder. When you select "RecordTypeId" from the list of fields, we'll show you the configured Record Type record options for that Object type.
New year, new release! Just a small Bookbuilder performance improvement this week, but we couldn't hold it back any longer.
We found a pretty degenerate case where having hundreds of fields on certain objects (like Account) could cause the Target Book and Enrolled Accounts Criteria editors to take a long time to load (sometimes causing Page Unresponsive errors). Thankfully, our crack team of performance engineers were able to track down the cause and quickly get a fix in place.
Tis the season for giving and you're on the nice list so you're getting all kinds of Bookbuilder gifts in this holiday special double release!
Previously we showed you "All" or "Templates" for Distributions and Retrievals. Now you'll see that we've replaced "All" with "Upcoming" and "Past" options. You'll find all your "Processing", "Scheduled", and "Recurring" Distributions and Retrievals under "Upcoming". The "Past" menu option will display all your successfully completed Distributions and Retrievals as well as any that were unsuccessful.
Following the separation of "Past" and "Upcoming" Distributions and Retrievals in the main listings, we've also updated the Overview to now show an abbreviated list of Distributions and Retrievals in these categories.
Now when you click on "Distributions" or "Retrievals" from the navigation menu, you'll be greeted with a flyout menu offering you the choice to start a new Distribution or Retrieval from scratch or from a template. You'll also find these helpful flyout menus anywhere you encounter a "New Distribution" or "New Retrieval" button.
We gave Distribution and Retrieval Templates one heck of a makeover. Here's the highlights:
- We have updated how you can interact and use Templates so that well....they work more like Templates. Rather than using a Template to run a Distribution or Retrieval with, anytime you use one now, we'll create a separate copy so that any changes you make to your Templates do not affect any upcoming Distributions or Retrievals. Templates should be your starting point.
- You can now Delete Templates! But don't worry any Distributions or Retrievals that were created using the deleted Template won't be impacted in any way. If the deleted Template is configured to be used in our Retrieval action it will also still run without issue.
You can now more easily pause, cancel, and restart recurring or scheduled Distributions and Retrievals. We made these options easier to access from the Overview or the new listings row actions. We also gave the form a little bit of an update and added the ability to create a Template before Pausing or Canceling.
- We fixed an annoying little bug when trying to type in date literals to condition criteria anywhere in Bookbuilder where we wouldn't let you type more than 1 digit (i.e. - LAST_N_DAYS:1). We've fixed that and we're very sorry.
- We've also now added the ability to select TextArea fields as condition criteria in Bookbuilder.
- We've also fixed an issue in our asynchronous Distributions where we would sometimes stop processing the Distribution pre-maturely.
🚨 EMERGENCY RELEASE 🚨
Emergency release to fix an issue when trying to display more than 20 Reps in the Reps listing within Bookbuilder.
This week we've got some bug fixes and interaction updates. Nothing too heavy, we're all still recovering from Thanksgiving.
We found a bug in how our Send Slack Message action displayed Task objects, so we've got a fix for that. We also fixed an embarassing misalignment of the help icons.
We've added the ability to search for reps in the Reps listing report as well as our new Working Activities report.
We've got a couple UI updates in this release:
- Enrolled Accounts now lives under Settings instead of having its own side navigation item
- The Target Book report now has a new header style (to match our fancy rep reports)
We got another chonky one this week. We had to go big so we could make so much more room for activities!
You asked and we delivered! To help you gain deeper insights into how much your reps are working their accounts, we created a Working Activity object where you can add the conditions unique to your org's SLAs. Simply navigate to Bookbuilder > Settings and click on 'Configure Working Activities' to get started.
We added the new option 'Reps' to the side navigation menu. Here you will find useful information about the accounts your reps are working. Once you configured working activities, clicking on a rep will take you to the Rep Working Activity Report where you will see all new metrics and data giving you deeper insight into your reps' worked (and unworked) accounts.
Fixed a bug where we skipped over queues with only 1 user in them. Also, we were displaying a 'no routing target' message as an error when in actuality, it's more of a notification, so we fixed that too.
There were some issues querying for records when a target book segment did not have at least one condition, so now at least one segment condition is required.
🚨 EMERGENCY RELEASE 🚨
Busy day squashing bugs, we got a second release for you today. We found a bug where an assignment would fail due to the absence of a queue item. We apologize if this caused you any trouble.
🚨 EMERGENCY RELEASE 🚨
This release is an emergency release to fix an issue causing some async distributions and retrievals to fail. We discovered that we were not correctly accounting for large number formatting in our SOQL queries. Salesforce returns sufficiently big enough numbers using exponential notation which can cause query errors. We have fixed this and we're very sorry if you were impacted.
We got a big 'un this week. From settings to email alerts to scheduled Distributions and Retrievals, there's something for everybody in this one.
The first time we detect that a Distribution or Retrieval you're trying to run is over the configured Async Threshold, we'll let you know so you have a chance to go update your settings before you run the Distribution or Retrieval if you want to.
Additionally, whenever we detect a synchronous Distribution or Retrieval has failed to run, we'll show you your async settings then and there so you can update them immediately and try again.
We have a new Setup option for you now, Settings!. Everybody loves settings. You'll be able to easily manage your Batch Size and Async Threshold values here as well as configure which of our new alerts you'd like to receive and who should get them.
We have added two new email alerts for asynchronous Distributions and Retrievals. One for when an asynchronous Distribution or Retrieval complete and one for if they fail. By default we will send these emails to users with the Gradient Works Bookbuilder Admin permission set assigned but this is configurable from Settings within the Bookbuilder app.
You can now schedule Distributions and Retrievals. When setting up a new Distribution or Retrieval, we've added a new step before preview generation for you to configure a schedule if you want. You can choose to schedule the Distribution or Retrieval to run once in the future or set up a recurring schedule. You'll also be able to modify the schedule at any time and pause or cancel it if you need to.
In non-Bookbuilder news, we had a bug pop up with our stop words list used in the Matching actions. We've fixed it and we're very sorry if this caused you any trouble.
You guessed it, more improvements to Bookbuilder this release, including the ability to run Distributions and Retrievals asynchronously.
Before Distributions and Retrievals had sub items of "Completed" and "Templates". Now this has been simplified and reordered as "Templates" and "All".
We have added the ability to run Distributions and Retrievals asynchronously. If we detect that a Distribution or Retrieval is going to assign more accounts than the configured threshold, we'll automatically run it asynchronously. You'll be able to check on the status of these async Distributions or Retrievals from the "All" listings. The batch size and threshold are configurable in Gradient Works Settings found in Setup > Custom Settings. We default the batch size to 20 records and the threshold to 200 records.
We continue to improve the Bookbuilder experience but we also took some time this release to revisit some of our oldest and dearest Flow actions.
The Assign Single Item and Schedule And Assign Single Item Action Flow actions now have brand new editors that should make configuration easier than ever. Rather than having to always type in the Queue name, you can now just choose from a list. Additionally, these new action editors should make it less confusing to provide capacity (and meeting location for the scheduling action) values when trying to decide if you should specify a value or a field for us to look at.
If you skipped the Bookbuilder onboarding tutorial because you were excited (we totally get it), it was sometimes difficult to understand what features required onboarding completion. We've added in some messaging to make it easier for y'all going forward.
You can now sort by any column when viewing a Distribution Preview or Retrieval Preview. Quick note on the Distribution Preview segment column - the column is sorted by the first segment added to the Target Book.
When configuring criteria throughout Bookbuilder, you can now more easily specify a dynamic date range using the new "Custom" option (think LAST_N_DAYS:33 and LAST_N_WEEKS:27) in the options dropdown. This should allow you to better tailor which accounts get distributed and/or retrieved through dynamic books.
Got another packed release this week. Full of new stuffs and fixed stuffs, we hope you enjoy.
We took some time to polish the Bookbuilder layout to better fit varying screen sizes. No more misaligned corners, yay!
Whenever you view the Account Ownership Report for a Rep for a Target Book, you'll now see a "Manage Fields" link that will allow you to customize the Account information displayed for that Target Book.
You now have the option to edit a Distribution or Retrieval Template and execute it without permanently saving those changes. Very helpful if you need to run a one-off Distribution or Retrieval.
The new "Bookbuilder Admin" permission set will let non-System Administrator Users edit Gradient Works Bookbuilder objects. With great power, comes great retrievals. Please distribute responsibly.
We had some ugly tooltips in our New Distribution form. But no more * asterisks * or ~ squiggly lines ~ for us! We hope you enjoy our freshly formatted tooltips.
Normally, we like to keep our releases to every two weeks, but we've got a couple of really nice features that we're too excited about to wait. Also, we may have found a bug or two that we wanted to get out ASAP because someone was a bit embarrassed about them (and rightfully so, in this humble changelog's opinion).
The account ownership breakdown report now has a new rep switcher in the upper right corner. Now, you can quickly switch between reps and see the account breakdown for each rep with a given target book. It gives you a quick way to see the state of your reps' worlds (well, their accounts, anyway).
From the target book breakdown report you can now quickly access the target book configuration. Just click on the Configure link next to the target book name and you'll be taken straight to the target book configuration. We've also added a shortcut to edit the reps for the target book you're viewing - just click on the Edit Reps link.
We goofed and kept the size of the account ownership table too small so you had to scroll and scroll and scroll to see all your reps (it now grows to accomodate the number of reps with that target book). We've also added some additional logging (available in Log Entries) in the event of a distribution or retrieval failure to help track down the cause of the problem (previously, the log was only available via the developer console, which, ew).
Today’s release is a big milestone. We are excited to announce Bookbuilder, a new tool to help revenue teams adopt and implement dynamic book management.
Bookbuilder allows you to implement best practices from dynamic books to keep your reps well-fed, balanced, and constantly working the highest potential accounts. In our pre-release testing, we’ve seen that adopting dynamic books with Bookbuilder can significantly improve rep attainment and overall sales performance.
Our initial release allows revenue teams and their ops partners to:
- Set up target books to define the right type and amount of accounts their reps should work
- Distribute high potential accounts to their reps according to their target books
- Retrieve unworked accounts from Reps to be distributed to others
- Analyze reps books to understand what accounts they need to be on target
We’ve built Bookbuilder to be intuitive and easy to use for any revops and sales leader – no SFDC admin expertise required.
We’re excited to finally make Bookbuilder available and look forward to the many improvements and additional capabilities we will add in the upcoming months.
We have a couple of small updates this release and a lot more work for the dynamic book management pre-release solution. I hope you're getting as excited about it as we are!
We discovered that if you had your Condition Requirements dropdown set to "Any Condition is Met (OR)" in the Filters section of a matching action and no actual conditions were specified, it would cause no matches to be returned. Now if a matching action is configured this way, we will correctly return matches rather than excluding everything for no good reason.
This one includes a new pre-release solution to help outbound focused sales teams manage dynamic books. Even more on this soon!
The team is still hard at work on a new feature but we didn't want to wait to give y'all a new Matching action and some updates to Capacity Meters.
In addition to our Lead matching actions, we now have an action to let you match Accounts to other Accounts. See Match Account to Account for more info.
We discovered that we were not correctly allowing users to check if an Id field was set or not as part of the Conditions for a Capacity Meter. We're sorry about that and have fixed it.
You can now use a String variable as the input for Capacity Meter in Get Used Capacity. This is helpful if you need to dynamically set the Capacity Meter to use in the action.
We're currently hard at work on a new super-secret set of functionality but in the meantime we've got a small enhancement for y'all.
The default Salesforce callout timeout is 10 seconds, which can be a bit too short at times. We've increased it to 30 seconds to cover the vast majority of cases.
This week's release is all about improvements to some of our existing actions and record detail pages.
We updated the information we display for individual Log Entry records to reduce the noise and only show what really matters.
Previously the matching actions may have found an exact match when using fuzzy matching in the matching criteria but would not always return it as the bestMatch. We've fixed this so that now if you're using fuzzy matching in your matching actions, we'll always return any exact match meeting all the criteria as the bestMatch.
You can now add an Execution Delay when configuring this action and we'll schedule the specified Flow to be run at a later time. This will be useful for things like waiting for another service to update a Record before running a Flow or scheduling Flow actions that the standard Scheduled Paths can't execute (like converting a Lead in a Record-Triggered Flow).
It took us a little longer than usual to get this release out but we really think it was worth the wait.
You can now see all in one place what happened when one of your Automations ran. You'll be able to see information about the Records and Users involved and the steps taken (or not taken). Check out Automation Executions for more details.
We've got something new and exciting for you this release! Read on for more.
We've made it easier to manage your Queue membership all in one spot and allow users to manage their own availability. Please see Users for more details.
Small release this week but don't you worry, the team is working on something really exciting. More details soon.
We've made some updates to how we display and search for some input options in some of our editors. You'll notice in the Send Slack Message, Add Person to Sales Engagement Cadence, Check Person Enrollment in Cadence and Get Used Capacity actions that we've added better searching capabilties for the Channel, Cadence and Capacity Meter dropdowns. This will be especially useful for users with lots and lots and lots of options to choose from in those dropdowns.
We've made a small update to the upgrade button to hopefully make it easier to upgrade your Gradient Works package. You should no longer have to re-login to upgrade or worry about having to update the link if you're in a sandbox site.
A new Flow action and another round of refinements coming out hot and fresh just for you.
As you know from previous release notes, we recently added Capacity Meters. The new Get Used Capacity action will let you use a Capacity Meter in a Flow to calculate the current used capacity for a user. You'll then be able to use the calculation result in the Flow to help determine if a user should get assigned an item or not.
- We added the ability to assign more than one item at a time. Useful if you need to re-assign several items (Accounts, Contacts, etc.) at once to the same user.
- You can now also assign items to a standard Salesforce Queue. Previously this action would only accept a User Id to assign items to but now you'll be able to provide us with a User or a Salesforce Queue.
The Send Slack Message action was pretty cool before but now it's even cooler thanks to some added flexibility.
Before, you could only specify one record to include information on in the Slack message sent from our action. With the latest updates you'll be able to choose fields to show from any record available in the Flow and link to as many records as you would like (as long as they are available in the Flow).
We've added lookup fields to our Assignment History object for Account, Lead, Opportunity and Contact to enable easier and better Report building. With these new fields it should be much easier to generate a single Report about the assignment that occurred and the item that was assigned.
This week's release is all about refinement. We've got a variety of updates to some of our latest features, check out the details below.
Various updates to the look and feel of this feature this week but no major functionality changes.
We've added in the ability to specify what should happen if we cannot find a user with calendar availability at the requested meeting time. The current behavior is that we will double book the user who was least recently assigned. While this will still be the default behavior, we've added in a "ifNoneAvailable" input and if you specify "doNotAssign" as the input value, we will no longer double book users. Instead we will return an error in the action output and not perform any scheduling or assignment. You should then be able to use the new outputs to decide what to do next in your Flow in the event of an unsuccessful scheduling.
We have also tweaked the behavior of the action when there is an API error during scheduling. We used to log the error message and still try to perform the assignment without scheduling the meeting but we've modified this to now raise the error and stop all action processing. To account for this in your Flow, you can add a Fault Path for this action.
Lastly, we've enabled reporting for the Gradient Works Calendar Event object so you can now create reports to see the meetings scheduled using the Schedule And Assign Single Item Action action.
Formerly known as the "Send Chat Message" action, we've decided to get more specific with the name.
We also made sure that the channels listing in the custom editor will now display private channels in addition to public channels.
We had a few other updates as well. They include:
- No longer displaying the "Queue Slots" listing for Queues using the Schedule First Available routing policy. That policy type does not utilize Queue Slots and it was just confusing to have it display.
- Fixed the permission error when trying to create Assignment Histories. Previously we would log an error anytime someone tried to perform an assignment and didn't have access to create a Gradient Works Assignment History. We've fixed this and we're sorry for the noise.
Last week the entire Gradient Works team got to spend some time together at a company offsite. While we learned a ton and had a great time, that didn't stop us from working hard and getting out another killer release this week.
We've added the ability to easily configure and track capacity values for users. Please wish your spreadsheets and reports a happy retirement from us. See Capacity Meters for all the details.
Those of you who have been around for a while have probably noticed that a lot of our tabs in the Gradient Works app say "Gradient Works" in them. We thought that was getting a bit redundant so we've cleaned that up.
Coming in hot with another new integration this release! SLACK IS HERE! I REPEAT, SLACK IS HERE!
You can now use the Send Slack Message action to notify a Channel or DM a user as a next step in your routing process. You'll be able to easily customize the message and mentions you send. Additionally, if you want to include some details about a Salesforce record, you can choose the record fields to include in the Slack message and we'll automatically include a link to the Salesforce record for you.
We got some good stuff this week! In addition to some improvements to our automation templates and Add Person to Sales Engagement Cadence, we've added Microsoft 365 to our ever growing list of integrations!
You can now use Schedule And Assign Single Item Action with Microsoft 365! Just go to our Settings tab and authenticate with Microsoft 365 and you can start using this action in your automations.
We've added the ability to select a User to assign the person to in your sales engagement platform. You can set this via the "Assign To" field in the action editor. In Outreach, we will update the Owner of the sequence prospect with the selected user and in Salesloft, we will update the Assignee of the cadence person with the selected user.
In addition to this update, we will now set the Owner of the Person to the Owner of the Salesforce record in Salesloft.
Please note that should the Lead or Contact already exist in Salesloft or Outreach, we will not override any existing ownership or assignees.
Now that we've gotten a few implementations under our belt, we've started to see some common patterns in the automations our users need. We've built some new templates based on these to make it easier and faster to get users up and running.
We've added templates for matching Leads and assigning Opportunites and we've improved the existing create Lead template.
Check out the
New button in the Automations tab to take advantage of these new templates!Small release this week but keep an eye on this changelog for some exciting features coming soon.
We have removed the requirement for Leads or Contacts to have phone numbers before adding them to a cadence.
The entire team hopes you had a good New Years! Our first release of the year is packed with refinements to our current Next Steps initiative.
Create Task got a huge face lift. We updated most inputs to allow you more flexibility. Specifics below.
- 1.Subject now accepts resources as inputs rather than only letting you type in a Subject.
- 2.Assigned To, Related to and Person will now accept an Id in addition to a Record.
- 3.Due Date now accepts a typed in Date as well as a formula.
- 4.Comments got a makeover in the editor and now allows you to add resources to the input.
Previously Add Person to Campaign would not perform any updates to existing Campaign Members if one was found. We've changed things a bit so that if any field updates are defined in the "Additional Details" section of the editor and the existing Campaign Member doesn't have a value for the specific field, we'll go ahead and update it.
Existing Campaign Members and newly created Campaign Members return more details in the action result now to hopefully eliminate the need to re-fetch the record.
Lastly, we also fixed an issue in the editor where we were showing more than just Active Campaigns. Apologies if this tripped anyone up!
You can now reference a Person by a Record, Id or Email.
Things are slowing down a little bit as the team takes some well-deserved time off, but we just had to get one more release out the door before the new year.
Happy holidays from our team to yours. See ya next year!
We've added Outreach support to our sales engagement cadence actions.
If you've been holding off on using our Add Person to Sales Engagement Cadence or Check Person Enrollment in Cadence actions because your organization uses Outreach instead of SalesLoft, well now you can! Simply go to your Settings tab and Authenticate with Outreach and you can start using these actions in your automations.
We've also added the ability to reference a sales engagement cadence in your action by name, Id, or variable. Before, you had to hard-code the cadence in your action by selecting the cadence from a dropdown - now you can programatically define which cadence you wish you reference in your action.
There were a couple of places where we missed some UI details (like sorting the list of cadence names). We've cleaned them up and made things a little more consistent.
We continue our Next Steps initiative in this release. We're really excited to share that we've added an integration with Salesloft and some actions to help with sales engagmenet cadence enrollment.
But that's not all the team has been up to, check out the details below.
We updated the former "Calender Integrations" module in the Settings tab. Now it looks a little nicer, has a way for y'all to contact us if you have an integration you think we need and allows authentication with Salesloft.
The Add Person to Sales Engagement Cadence action will allow you to add prospects to a Sales Engagement Cadence in Salesloft. Just select the Cadence to use from the dropdown and provide the Lead or Contact information you want to enroll. Please note this action is asynchronous and requires authentication with Gradient Works Cloud and Salesloft.
The Check Person Enrollment in Cadence action will allow you to check if a prospect is already enrolled in a Sales Engagement Cadence in Salesloft right from your automation. Just select the Cadence to use from the dropdown and provide the Lead or Contact information to check enrollment for. We'll let you know if they are enrolled or not. This action requires authentication with Gradient Works Cloud and Salesloft.
We're always looking for ways to help our users understand what happens when they use a Gradient Works action. Now that we have Create Task and Add Person to Campaign, we want to be able to tell you which Tasks and CampaignMembers were created from those actions.
When you include our Start action in your automation, we will include on any Task or CampaignMember the automation information that triggered the creation. To see this information you can add Flow Name, Flow Version and Flow Version View Durable Id to your Task and CampaignMember layouts.
It was brought to our attention that we were making users do more clicks than necessary to delete a Queue User. Now you'll be able to delete them right from the Queue Users module when looking at a Gradient Works Queue detail page.
We noticed that we could have handled some input options better in the Add Person to Campaign action editor. We've fixed that and we're very sorry if it caused any inconvenience.
This release is all about our Next Steps initiative. We're building out more actions for you to take after we've done our routing or matching magic, such as adding a prospect to a Campaign or creating a new Task for a rep to follow up with.
As a side note, this changelog has a lot to be thankful for this year. It's rare enough to work with an amazing team but when that team is also your family, well - sometimes all you can do is be grateful.
The Add Person to Campaign action is a great way to add prospects to campaigns as part of your automations. Select the prospect (or provide a record) and the campaign (name or record) you want to add them to, and our action does the rest. Additionally, you can update additional fields on the newly created Campaign Member object using the 'Addtional Campaign Member Details' section.
The new Create Task action creates and assigns a Task to a rep. It's great for creating follow-up tasks after routing and assigning Contacts or Leads. Much like the Add Person to Campaign action, you can update additional Task fields using the 'Additional Task Details' section.
This week we are happy to report that los Gradientes are vaccinated! It's been a long time coming and this changelog is very very happy. They were very brave and strong while getting their shots.
This changelog, not quite so much.
We've found a less-intrusive way to handle user deactivation that doesn't have the same risks that the initial implementation had. We're very sorry that we missed this the first time and apologize for any inconveience this may have caused. Thankfully, we're now aware of the flaw of this pattern and will avoid it in the future.
If you need to change the Google account associated with our Scheduling component, it's now much easier to do so. Once authenticated, you can simply click the "Disconnect" button and it will disconnect the old account. Then, you can click the "Authenticate" button and it will take you back through the Google authentication process.
🚨 EMERGENCY RELEASE 🚨
This release is an emergency release to fix a bug that was introduced via our Deactivated user support. We found that our implementation has the potential to conflict with customer User triggers, so we've disabled the feature for now. We're sorry for the inconvenience. Stay tuned for a permanent fix in our next release.
The weather outside is gorgeous today and ITS A BONES DAY! I suggest you treat yourself with a nice tall glass of water and our LATEST RELEASE :)
When you include our Start action in your record-triggered automation, we now log the record that initiated the automation. We also include it in the logging context of that automation and plan to expand on this in the future. Stay tuned.
We missed an edge case with our flow action editor which caused the editor to not pick up the selected record. We're sorry if this caused you any issues - the team has been throughly chastised and they promise they'll never ever do it ever ever again. Ever.
With spooky season in full swing, the Gradient Works kids (los Gradientitos?) got together last night for a pumpkin carving contest/celebration. The changelog was hurtfully not invited.
An organization will often want to influence its matching or assignment rules based on domain information (the domain of an email address, website domain, or some other field provided by an enrichment platform). To help, we've added a Domain Denylist and an accompanying Evaluate Domain against Denylist action - add the domains that you'd like to filter against to the Denylist and the action will show you if the extracted domain you provided matches any of the domains in the list.
We've added a new Settings module to display additional information about your installed version of Gradient Works (such as links to the documentation and release notes) as well as the most recent version.
We're a day late on our release and for that, this Changelog is truly sorry. It's been a long few weeks over here in Gradientland but even with that, our intrepid Gradients (Gradienters? Gradient Workers of the world unite?) have got another good release in the bag this week.
They're very, very good.
With this release, any deactivated users automatically and immediately become unavailable across all Gradient Works queues. This should lighten the load a bit for anyone responsible for maintaining Gradient Works queues and assignment rules.
Last week, we added a couple of flow-related fields to the Assignment History layout. As we reflected on that change, we saw an opportunity to add a little more detail and color to the flow information, so this week we've added a new Flow Details component module to both the Log Entries and Assignment History layouts. It pulls the flow information out and to the side (when applicable) and really makes it easer to see and understand which flow was responsible for the assignment or log entry you're looking at.
We're not talking about how this season of Ted Lasso is almost over so don't bring it up. Instead, we'd rather talk about all the niceties in this release (work is a good distraction).
We've got some nice flow action editor fixes in this release. We know they've been bothering y'all, because they bother us too and, frankly, we couldn't take it anymore. So, we've got:
- dropping that dang trailing period! When you select something from our dropdown, sometimes you'd get this trailing period after it that you'd have to clean up yourself. Well NO MORE! NO MORE I SAY!
- Speaking of dropdowns, let's get some better labels in there! Objects and properties now show their labels (when applicable) making it easier to find what you're looking for (also now they're alphabetized 🤭).
Increasing visibility into your revenue operations is what we're all about - to that end, you can now see which flow (and version!) triggered a given Assignment! You'll need two things to make this happen:
- 1.
- 2.Update your Assignment History layout to the latest version so that the new fields are included and visible
For record-triggered and platform event-triggered automations, we've added the triggering record type to our Automation listing. Now it'll be easier to see at a glance which records trigger which automations, not to mention searching and filtering by record type.
- Complete separation of our background purge jobs to keep them fully isolated - we never want them to affect the running of any other jobs
- Permission updates - some classes had outdated permissions which may have led to certain users having reduced visibility or access
Spooky season is officially upon us! The weather is getting a little ghoul and breezy down here in Austin and we're starting to put out the Halloween decorations. Don't be afraid - this release is solid and we won't need to pumpkin patch anything 🤣
As more customers use our Scheduling component, we're seeing how important it is to give automation builders the ability to override certain parts of the scheduled calendar event. With this release, you'll be able to override the event location field (either manually or from a field lookup) on a per-user basis. If your users have individual meeting links (Zoom, etc), now we can use those specific links when scheduling events.
Big news this week - our engineering team grew 50%!!! AND this changelog is proud to report that our new team member has contributed significantly to this release and that's just dandy.
We just can't get enough settings modules. There's a NEW one this week, this time for information regarding the Gradient Works managed package. Right now, it's only got the currently installed version but keep an eye out for more info coming soon.
Our crackerjack engineering team was on 🔥 this week, tackling a bunch of little UI tweaks and corner cases:
- Logging settings module full-screen layout is now more responsive
- Calendar authentication settings module now displays a spinner during the authentication process
- Scheduled automation save notification cleanups
- Log purging schedule increase to keep ahead of potential overflowing logs
I dunno about y'all, but this changelog is very happy that the Yankees are back playing on the east coast. I'm not saying those west coast games starting at 9 PM Central were impacting releases but I'm not not saying that.
Listen, we get it. Y'all love settings. We do too! That's why we've added another settings module, this time to view the status of Gradient Works' background jobs. Additionally, if for any reason one of the jobs stops running, you'll be able to re-activate the job straight from the job settings module.
We cleaned up a spammy log message that, just between you and me, wasn't really doing anyone any favors. RIP to 'ApiToken is not active'. We'll mourn ya til we join ya.
We apologize for getting this release out a day late but we really wanted to fit everything in and someone needed an extra day. We won't say who, but his name rhymes with mongo.
We now support adding your own custom stop words list for use in our Fuzzy match types. This means that you can now add words that you do NOT want to be considered when applying Fuzzy matching (in, say, our Lead to Account, Lead to Contact, or Lead to Lead actions). Like the Nintendo Power Glove, the power is now in YOUR hands.
It's now much easier to view and update your Gradient Works logging settings (such as the log level and how many days logs stick around). Head over to the Settings tab and you'll see the new Logging module at the bottom.
We found a small issue with the way that we were processing our usage events - at times, certain types of events wouldn't be sent. This showed up as a specific error in your logs ('You have uncommited work...'). We've split up the processing of usage events to keep this from happening. Many thanks to the customers that reported this - we're better together.
We're deep in the dog days of summer down here in Austin. It's hot and gross outside, so we're staying inside and watching Ted Lasso and doing our best to stay cool. We hope our friends around the country are staying dry and safe - we're thinking about y'all.
We've done some significant work to our Flows: Start, Flows: Finish, and Flows: Failed actions in this release. You should see much clearer log messages and additional debugging context info from these actions.
Hot on the heels of our big Scheduling release last week we, of course, found something we missed! As we started seeing folks use the Scheduling flows we noticed that we kept wanting access to the calendar event once it was created, so we, you know, did that.
This is a little inside baseball but we're deprecating the AssignQueueItemsScheduledJob. Part of putting the product in front of more and more customers is realizing that sometimes our initial ideas and abstractions aren't always correct. This change shouldn't be visible to anyone other than us, but in the event this was your favorite scheduled job, I'm sorry you had to find out this way.
Honestly, we have no idea what's been going on out there in the real world. We've been heads down trying to get our new scheduling component just perfect for y'all, and GUESS WHAT?
It's finally here! With this release, we're including the Schedule and Assign Single Item Action - the first action to take advantage of our scheduling component! This action will assign a single item to a rep (from a queue) and schedule a meeting between that rep and the prospect associated with the item - no more checking calendars to see who's free and when. We do that work for you. You're welcome, we're happy to help :).
You can also see the calendar event on the queue item's display page, because we're fancy like that.
We're in the final stages of summer over here and the kids are trying to soak it all up before school starts next week. We're all a little stressed out about this year, so if you wouldn't mind sending us some good thoughts and positive vibes, we'd be much obliged. We're doing the same for y'all.
Several customers pointed out how difficult it was to search through our assignemnt log messages. We've heard you loud and clear and now it is SO much easier. It's already making our lives better, so thank you for the feedback.
We found a potential issue with some very large bulk assignments. While we haven't seen it be an issue in the wild, we went ahead and fixed it because, hey, doing the right thing is never the wrong thing.
Now this one was on us - when the Automation tab loads we display a spinning icon to show that it's loading data. Unfortunately we got some wires crossed and the spinner would complete without always showing the fully loaded data. So we fixed that.
We can't get enough Ted Lasso in our lives right now. We've watched all the season 2 episodes about 10 times so we decided to take a break and get some work done. Don't call us Friday morning because we'll be watching those lovable footballers shining their good good light down on us.
We found and fixed a bug that would cause an error when assigning a record whose previous owner was not a User. It was edge-casey, but we found it and squashed it but good.
We're making excellent progress towards our calendar scheduling functionality and this is the first BIG chunk - we now have a new Queue assignment policy that will assign an item to the first available user in a queue AND SCHEDULE A MEETING with the interested parties. We've still got a ways to go, but this is a giant leap down that path.
We wanted to get this release out last week but Salesforce had other plans. Now that they've solved their deployment issues, we're ready to send this one out. It's only a couple of bug fixes, but it's important to us that we deploy new versions on a regular basis so our apologies for not getting this one out sooner.
We found some edge cases where attempting to match a Lead with special characters in the email address would cause our Matching flow actions to error. We believe in character equality here at Gradient Works and this release fixes these errors. We apologize to the special character community and promise that we will do our best to keep this from happening in the future.
Some of our background jobs and processes generate objects that don't need to live around forever so we periodically clean them up. We recently found a couple of these cleanup areas where we weren't guarding against potential DML limits, so we've added checks to keep us from hitting those limits.
We're still recovering from the F9 release but we did manage to get some work done. An astute reader will note that it's been a minute since our last release - today you find out why.
We've standardized logging throughout the installed package. Consistent logging levels across all of our features will make it easier to filter and debug things like flow actions. We've also moved most of our internal logging to a lower log level (FINE, fo those that are curious) which is going to help reduce some log noise that isn't necessary for day-to-day logs.
We've got a small batch size update in our bulk lead conversion action to help reduce potential DML errors (VERY large bulk updates would trigger DML limits).
We're cooking up some really cool calendaring integrations. Even though they're not completely done, we're putting out the initial setup and authentiation components out so that everyone can be ready to go for the next release.
I never thought this day would come. I mean, I'd hoped and hoped but sometimes it can feel like hope as abandoned these lands, but it's here - F9 is OUT TODAY! HAN'S BACK! AND MAYBE SEAN!
Oh and we had a pretty great release this week too :)
Converting muliple leads at once is now easier and more efficient. Handling them in bulk allows us to avoid hitting built-in Salesforce limits and makes them execute faster.
You can now schedule active autolaunch flows to run on a schedule! Head over to the Automations tab and check out the details menu on the right of the Gradient Works Flows table - from there you can manage the schedules for your individual automations.
No release last week - it was too hot for us to package anything up. Well, joke's on us because this week was even hotter. We somehow managed to stay cool enough to make some really good progress with Flows and a new surprise Tab!
We did A LOT of work with Flows this release:
- New Flows from Templates - check out the
Newbutton in the Automations tab for a drop-down of flow templates that you can now use to create a new Flow from! Keep an eye on that list for new flow templates coming soon. - Enhancements to our custom property editors
Surprise! It's Settings!
We've removed the Admin tab and replaced it with Settings. It's a bit empty at the moment, but we'll be adding things directly.
This has been a fun week! As more and more customers use our software, we learn more and more about how we can best provide value. Also, we learn about where we may have made some mistakes in our initial implementation (not me I'm just a
Changelog) so this week we've spent our focus on smoothing over some rough edges.We've made a small tweak to the Automations table where the label now links to the Active version of the flow (or latest version if the flow isn't active) instead of the flow detail screen which no one wants to see.
We also fixed a couple of small issues with our
Convert Lead action that were causing some headaches, mostly around some edge case behavior. If you've had problems with the Convert Lead action in past please give it another shot.LAST WEEK OF SCHOOL! LAST WEEK OF SCHOOL! I know this isn't at all related to the product but I'm really proud of all the Gradient Works kids and how they've managed the last year and a half. It's been hard for me personally and I'm just a Changelog.
Way to go, kiddos. We're all super proud and rooting for you and we're always in your corner. Stay cool and have a great summer!
That's right! Our Assignments table on the Dashboard now has infinite power I mean scrolling.
What's that? This just in - I'm being told that it's not technically infinite by our attorneys. But between you and me, it's pretty close. When you get to the bottom of the table keep scrolling to quickly load up the next set of Assignments (and keep scrolling!).
We've improved our ability to see and visualize the effects of automations within your org and we're using that information to monitor more effectively as well as better understand how we can best provide value.
It's been a rainy week in Austin, but we've got a lot of happy kiddos ready for the school year to be over and some slightly anxious parents who are nevertheless excited for summer.
We've got a brand new heckin' spiffy website and it just wouldn't be right if our docs didn't get the same UI love. Our documentation is like manners - a way of showing other people we care about them.
Building on top of the dashboard work across the past few releases, we added some addtional detail to the Assignment History detail page. You can expect to see continuous incremental improvements to the dashboard as we focus on ways to better capture and display Assignment information.
This was another one of those behind-the-scenes releases, but we did have one quick fix that couldn't wait to get out.
We hit a permission snag with the last release of our new Dashboard which has been resolved with this issue. Our thanks go out to those that pointed out the issue and helped us test the fix.
We're really excited about this release. The behind-the-scenes work is fun, but what we really love is getting stuff out in front of people and getting feedback on what's working, what's not working, and what we can do to help YOU.
This is the big one, friends. It's like the Millenium Falcon you always hoped to find under the Christmas tree, only it's actually here!
Currently, we're focusing on Assignments (as you can see) but expect to see this area grow in future releases. Observability is important to us and we want to make it really easy to see what Gradient Works is doing for you.
We've customized the Flows: Start, Flows: Resume, Flows: Finish, and Flows: Failed action editors. They're smarter and require less upfront configuration, making it easier to incorporate them into your flows.
Our existing flow actions got a little bit of love in this release. They've all been updated to take advantage of the framework that powers Flows: Start, Flows: Resume, Flows: Finish, and Flows: Failed, so moving forward things like logging and basic behavior should be a little more standard.
We're working hard towards additional flow and reporting functionality, but it wasn't quite to our liking yet so it's not making it in this release. Instead, we've got a small bug fix that limits how many Gradient Works Log Entries we try to purge at once.
We were slightly distracted by the new F9: The Fast Saga trailer this week but we managed to pull it together familia-style and ship some more monitoring and observability building blocks.
When a Flow contains a Screen Flow action, the Flow transaction can change making it difficult to track the full Flow execution. Adding a Resume action directly after any Screen Flow action ensures that the transaction change is tracked properly and the full Flow execution is tracked from start to finish.
Faults in a Flow can also make it difficult to see the full execution from the start of the Flow all the way to the failure point. Adding a Failed action in fault paths preserves the full Flow execution even in the event of an error.
Our Failed action also gives us the ability to send an email notification when a Flow fails. To enable Flow error notifications, set the
Error Email Address (Gradient Works Settings under Custom Settings) field to whatever email address you wish notified and add a Failed action in your Flow fault path.Much like with assignment notifications, you'll want to use an org-wide email address to ensure that your error notification emails conform to your organization's email policies.
This one has a lot going on behind the scenes, but not so much... in front of (?) the scenes.
So what are these mysterious goings-on? I'm glad you asked.
One of the things we care about a lot is what we call "monitoring and observability". Basically, it's the whether or not you can figure out why an automation did what it did. That's where we've been focusing our time.
Since you've no doubt been following this changelog like a hawk, you'll recall that last week we added a new Automation section. This week we're building on that with some new functionality to help you track your Flows from start to finish (or failure, if something goes wrong). We call this the "Flow Lifecycle".
To get started, we've added two new actions: Start and Finish. If you add these to your Flows at the start and the finish (see what we did there), we'll be able trace the Flows and keep a record about each execution. This release lets us start keeping track of this stuff behind the scenes. A release in the very near future will make it visible to you.
Stay tuned.