Create a Module

Introduction

Modularization lets you break your org’s customizations into unlocked packages. Each package becomes the single source of truth for the metadata it contains, and you can update any environment—scratch org, sandbox, or production—by installing the latest version.

Whenever you change the package’s metadata, you simply create a new package version and install it wherever it’s needed.

---

Creating a Module

Follow these steps to create a module in AutoRABIT:

1. Open Modularization Hover over the SFDX tile and click Modularization.

   
2. Start a new module Click Create Module.

   
3. Name and source

   • Enter a Module Name.

   • Choose the Source Org that contains the metadata. Click Next.

   
4. Select metadata Choose the Metadata Types (and their members) to include. Use the Search Filter to locate items quickly.

   

   Important: Avoid adding metadata types that already belong to another module in the same branch.

5. Review selection Click Selected Members to view a summary of chosen metadata, then click OK.

   
6. Click Next to open the Validate and Push screen.

   
7. Validate dependencies Compare the Source Org with another Salesforce Org to ensure no dependent components are omitted.

   
8. Additional options

   • Ignore Missing Visibility Settings, If Package Contains Profiles Or PermissionSets – visible only when Profiles/PermissionSets are included; deploys delta changes.

   • Ignore Installed Components – skips managed-package components already present in the target org.

Note: Standard fields are not supported for Ignore Missing Visibility Settings.

1. Publish To – configure commit and package settings.

   • Repository / Branch – pick where to commit the metadata (use + to create a branch).

   • Development Hub (Dev Hub) – select the Dev Hub that will own the unlocked package.

   • Email Address – recipient of the module-creation email.

   • Include metadata dependencies – automatically pull in required dependent members.

   

Tip: To fetch dependency data, the Dependency API must be enabled. See Salesforce docs here.

1. Package Dependencies If the Dev Hub already owns related packages with at least one successful version, they appear here.

**Conditions:**  
* The dependent package was created in AutoRABIT **and**  
* It has at least one successful version.

1. Add / arrange dependencies

   • Select packages in Available Packages and use the / icons to add or remove them.
   • Use / to reorder; the top package deploys first.

   
2. Create the module Click Create Module. You’ll return to the Modularization home page, where you can monitor progress.

3. Module list columns

   • Module Name – name you assigned

   • Source Org – org where the module originated

   • Repository / Branch – VCS location for commits

   • Package URL – link for package installation (see Deployment via Unlocked Packages)

   • Validation Status – pre-validation result plus log

   • Status – creation progress (Success, Failed, or In Progress)

   

Sample email notification

---

Additional Features

1. Actions

   • Edit Module – update module details

   • Log Details – view execution logs

   • Delete Module – permanently remove a module (irreversible)

2. Info

   • Module Summary Info – see dependency details for selected metadata

   • Module Info – view timestamps and other metadata about the module