This request is something my teams & users have asked for countless times since we started using Text Blaze.
After triggering a snippet, when a new page is loaded as a result of a snippet action, I want the ability to access site content in that new page via Autopilot using Regex and Selectors, so I can continue with process-vital functions via the snippe that was triggered, thereby saving the user from having to run additional snippets.
Use case: After a new case is created in Salesforce, the case is opened in a new Salesforce tab. It is at that point where I need to click on the Change Owner button, as well as access information on the tab that is only available after the case is created.
This is going to be an exellent feature. https://www.automa.site/ does very much similar thing already. Would love to see some of the Automa's features in TextBlaze as well.
I took a look at that product this morning and wow that's right on the money! The UI is great as well. I would also love to see those features in TB! I'd prefer not to introduce another product to all my users/teams at this time so I am in high-hopes that TB adopts this functionality in the foreseeable future!
Thanks Brad and Pratik for the feedback. We'll look into the "chaining snippets" idea and keep this thread posted with updates Feel free to continue the discussion with additional suggestions/demos related to this feature request.
Unfortunately, on the Automa page in Google Store, "This extension may soon no longer be supported because it doesn't follow best practices for Chrome extensions."
Speaking for my Org only, the need for "chaining" has only grown over time. However, we are in progress of a massive team and workflow restructuring that is combining a number of teams along with streamlining scores of processes. We immediately find that because of how Salesforce handles creating new cases and/or tasks, users now need to run at least 2, maybe even 3 snippets just to complete a process. When this is needed, I have to program the first snippet's last steps to put the case in Edit mode by pressing the E key via Autopilot then inserting the text "TYPE (2nd snippet short here) NOW!!!". Then, when the user inserts the 2nd snippet, its first step is to delete that instructional text before inserting the rest of it's output.
Basically, a "Chaining" solution, is what I am calling a Mission Critical request. Glad to set a meeting to discuss this further if you'd like.
Thanks for this feedback! Could you tell me a bit more about why the different snippets are needed? Would it be possible to use the {wait} command to let Salesforce do it's thing between the snippets?
The reason a {wait} command will not work is because the data needed does not exist at the time the first snippet is run. Salesforce pulls in the data automatically the instant the new case is created (saved) and presented to the user. Only then is the needed data available in the {site:text}.
Is an alternative to strictly linking snippets one after another, would it be useful to "suggest" a snippet? So you use your snippet, and then some sort of UI element pops up asking if you want to use this other snippet (or one of several snippets)?
Not really. The intent is to have the process as automated as possible so as to mitigate user errors. We need a snippet to either be able to access new info after a page loads, or have a subsequent snippet automatically trigger.
AWESOME! Thank you, @scott! Yeah - this would be the mother of all enhancements. "Game changer" is the understatement of the century. Glad to avail myself and my team for any assistance needed to move this toward production & deployement. -Brad