Skip to main content

From task to deployed change

What happens after you create a task: the technical design, approving and deploying it component by component, and what to check once the change is in Salesforce.

Written by Engineering Swantide

What happens after you create a task, and what to look at along the way. For how to set the task up in the first place, see Tips for working with AI Admin.

The technical design

Once the task is created, AI Admin writes a technical design covering the whole solution and each component it will create or update. Updates are changes to something that already exists. Creates are net new metadata. Nothing reaches Salesforce during this phase.

You can comment on the design and regenerate it from your comments, at the level of the whole solution or a single component. You can also review each component individually before approving it, so you can take the parts you are happy with and keep working on the rest.

Approve and deploy

Approve the components you are happy with and deploy. AI Admin writes the change to Salesforce and reports back per component, so you can watch each one land. Anything that fails comes back with the error Salesforce returned, and that component's details page holds the full history.

Once every component is through, the task moves to Done.

After it deploys

Check it in your org. Swantide updates the Data Dictionary automatically and documents whatever was created, so the catalog reflects the change without you doing anything.

Check the component list, not just the task badge. A task can report as complete while an individual component did not land the way you expected. The per-component status is the reliable one.

Did this answer your question?