AllAi Doc - Frequently Asked Questions

AI-powered tool, that automatically creates Salesforce project documentation, saving time and reducing errors for consultants, admins, architects and developers, by giving to the user the complete picture of how a Salesforce org has been configured.

AllAi Doc is available for Salesforce Core and Commerce Cloud.

Share your experience, bugs and improvement suggestions in the community.

You have tones of possibilities

• Take the course

• Check documentation

• Ask in the community

AllAi Doc is pretty good! And it’s features are constantly getting better and faster, but it doesn’t write perfect documentation always, so it will never replace any Solution Architect/ Sf Consultant. Remember to check the documentation returned.

AllAi Doc can be used for projects that lack documentation, but also for projects with outdated documentation.

Utilize the AllAi Doc capabilities to obtain the most up-to-date documentation for your project and to update any outdated documentation.

• Lightning Web Components

• Lightning Components (Aura)

• Flows

• Objects

  • Standard Objects with customizations

  • Custom Objects

  • Custom Metadata Types

  • Custom Settings

• Apex Classes

• Flexipages (Lightning Pages)

• Permission Sets

• Sites

• Services

• Jobs

• Custom objects

• Custom attributes

• Controllers

• Page designer

• Cartridge path

• Payments

• Shipping

• Inventory

• Price books

We use AI to generate several sections in the documentation. Sometimes, the AI is unable to generate a description so it outputs “invalid completion” instead. Generally you should not see many of these and ideally there should be none, so report them if you see them.

Your documentation might fail for several reasons, the most common of which is the structure of your zip code is not in the format we expect.

Please report this on the #osf-allai channel, and include the name of your documentation and version number.

Anything you upload in the zip file will never be shared with any third parties. We do however save the zip file on our OSF owned, IT monitored and encrypted AWS S3 bucket.

Once your codebase and metadata are uploaded, they will be stored in a secure and encrypted S3 bucket, we then parse all the components that we need and send small sections of them to OpenAI for AI generation.

Our contract with OpenAI prevents them from saving your data or using it for training their AI models.