Swantide continues to provide best in class workflows to help as you customize and manage your Salesforce. We have some new and some previous Workflows that we would like to highlight!
If you are using Swantide’s Onboarding Cycle custom object, you’d want to read about this Validation Rule. If you want to know more about the Onboarding Cycle object and process you can read about it here and if you want to enable it reach out to your CSM!
The workflow "Start Onboarding Cycle Records in the First Stage" allows for more thorough reporting on progression through the stages of your post sales pipeline by requiring all Onboarding Stage Records to be created in the first stage of your Onboarding process. In doing so, this workflow ensures that all of your Onboarding Cycle Records are created in the first stage of your onboarding cycle and cannot skip important entry points.
Using this Workflow, you will need to enter the first stage in where your Onboarding Cycle records start. Therefore, if using Swantide's default stages, this will be "Requirements Gathering"
https://help.swantide.com/en/articles/8386887-start-onboarding-cycle-records-in-the-first-stage
Seeking to refresh your Lead Pick-List Values when they become obsolete due to a lack of outreach? This workflow is tailored for you! The Swantide Workflow, "Update Lead Pick-List Value after X Days of Inactivity," operates on a daily scheduled basis. It scans for associated Tasks or Events on the Lead object and checks if there has been a specified period of inactivity (i.e., X Days).
For instance, assume there are Leads with the Contact Status “Working,” but these leads have not had a Task or Event in 60 days. In such cases, this Workflow enables you to automatically reset them to “Nurturing,” given the absence of recent engagement.
https://help.swantide.com/en/articles/8411687-update-lead-pick-list-value-after-x-days-of-inactivity
With this Swantide Workflow, any update applied to an Account Pick-List Field or Fields will automatically reflect in a Pick-List Field on the related Contacts.
For example, suppose there is a field named 'Type' on an Account. When this field is updated to 'Customer,' the flow can be configured to update the 'Type' field to 'Customer' for all Contacts related to that Account. This ensures seamless alignment of your data between Contacts and Accounts
If you have further questions, be sure to view our help articles or reach out to your CSM. Stay tuned for more workflow announcements.
