Disclaimer: Swantide is a generative AI platform, therefore it may be inaccurate, incomplete, or not applicable. The output from Swantide is based on the inputs provided by the user, and any content generated by Swantide must be thoroughly reviewed and verified by you prior to use. Do not implement, rely on, or act on AI-generated output without first confirming its accuracy and suitability for your specific needs.
Build
Configure / Code / Unit Tests
The Swantide AI Admin is the best way to generate technical design documents and make updates to Salesforce metadata. The process is described below:
Create Task (Client). Create a task name (for reference purposes only), and write a task description, which will be the prompt handed to the AI Admin
Generate Technical Design (Swantide). Swantide will generate an overall solution design document, as well as list each component to be created/updated, with technical designs of the component as well
Review + Approve TDD (Client). Review the design documents generated by Swantide. You can make inline edits or prompt Swantide to re-generate, both at the solution and component level. You can also view prior versions of the solution design if you are not happy with the updates Swantide makes)
Deploy to Salesforce (Swantide). Once you have approved the design of each metadata component, simply click Deploy, and Swantide will deploy the updated metadata into your Salesforce environment. If there are any errors, Swantide will return the error message provided by the Salesforce API
Validate in Salesforce (Client). Once the change has been deployed, view the deployed metadata components in the org and validate that they were deployed correctly. Swantide will automatically update the data dictionary and write documentation for the newly created components.
See this video for a tutorial of how you can use the AI Admin to make updates in Salesforce. Note that this feature is currently in beta - we have gotten good feedback on the solution design element, and are working on providing more stability in the creation of metadata components as we get ready for the product to be GA.
Notes & Best Practices
Because the AI Admin is in beta, if you are looking to write code (e.g. Apex, validation rules, formula fields), we suggest using the AI Assistant to generate the code, and copy/pasting into the Salesforce environment you are working in.
AI Admin tasks are visible at the org level, meaning all users can view all AI Admin tasks. You can only edit your own tasks - all other tasks are read-only.
The more specific you can be in the prompt, the better. Swantide should be able to handle more general tasks (e.g. take all of the fields in the More Information section on the Lead layout, create them as fields on the opportunity, and update the field mappings), but depending on the volume of fields, you may need to specify the names of the fields you want to create.
Deploy
The Swantide AI Assistant is a chat-interface that takes text as input and provides text as output. The Swantide AI Admin will create or update Salesforce metadata. See the previous Build Section for more information on how the AI Admin works.
Today, Swantide is not a replacement for whatever DevOps processes you use to promote metadata between environments. Think of the Swantide AI Admin as a way to automate the solution design and hands-on-keyboard time in the environment where you build or update new components.
You can however use the Swantide AI Assistant to help you build a deployment plan, see the prompt below for details:
Pre-Deployment
‘I want to take updates to the Organization - Before Save - Update flow and the Funding Award After Save flows and deploy them to production. Can you write a pre-deployment checklist for me? I want to make sure I can account for all dependencies, that I can roll back any changes if I need to, and that the production org is ready for the changes I’m about to make’
Potential Follow Ups
Document changes (ask Swantide to write an overview of specific sections of the flow. You can ask Swantide what changed in the flow)
Example: Help me document what updates were made. In the Funding Award After Save Flow, can you describe in detail how the Signatory Assignment Logic works, and how the email notifications work?
Prepare for Rollback: Ask Swantide how you should approach preparing for rollback
Example: “Can you describe in more detail how I should prepare for rollback as part of the pre-deployment checklist? What exactly should I be doing?” This will provide more information about this section of the pre-deployment checklist, which is designed to be ~ 1 page on the initial prompt.
Post-Deployment
“I want to take updates to the Organization - Before Save - Update flow and the Funding Award After Save flows and deploy them to production. Can you write a post-deployment checklist for me? I want to make sure that all of my users are prepared for the new changes that were made to these flows.”
Note that this prompt has a clear ask and gives parameters of things that the post-deployment checklist should highlight. Describing your intention and priorities in this way is best practice for getting higher quality output.
Potential Follow Ups
Flow Activation: Make sure you’ve done everything needed to have the process working as intended
Example: Is there anything else I should do when validating the flows are active to ensure this process is working correctly?