@salesforce/afv-skills 1.24.0 → 1.25.0

package/skills/dx-org-manage/examples/scratch-orgs/success_snapshot.json

@@ -0,0 +1,27 @@
+{
+  "status": 0,
+  "result": {
+    "username": "test-snap9012@example.com",
+    "orgId": "00D5g00000aDEF3EAM",
+    "scratchOrgInfo": {
+      "Id": "2SR5g000000EfGhIJK",
+      "Edition": "Developer",
+      "Status": "Active",
+      "SignupUsername": "test-snap9012@example.com",
+      "AdminEmail": "dev@example.com",
+      "Namespace": null,
+      "OrgName": "Company",
+      "ScratchOrg": "00D5g00000aDEF3EAM",
+      "SnapshotName": "MySnapshot",
+      "CreatedDate": "2026-06-12T15:20:00.000+0000",
+      "ExpirationDate": "2026-06-19"
+    },
+    "authFields": {
+      "accessToken": "00D5g...",
+      "instanceUrl": "https://...-dev-ed.develop.my.salesforce.com",
+      "username": "test-snap9012@example.com",
+      "orgId": "00D5g00000aDEF3EAM"
+    },
+    "warnings": []
+  }
+}

package/skills/dx-org-manage/examples/snapshots/error_output.json

@@ -0,0 +1,9 @@
+{
+  "status": 1,
+  "name": "NOT_FOUND",
+  "message": "Org snapshots are not enabled in this org. Contact Salesforce to enable org snapshots.",
+  "exitCode": 1,
+  "commandName": "SnapshotCreate",
+  "stack": "NOT_FOUND: Org snapshots are not enabled in this org...",
+  "warnings": []
+}

package/skills/dx-org-manage/examples/snapshots/success_output.json

@@ -0,0 +1,15 @@
+{
+  "status": 0,
+  "result": {
+    "Id": "0Oo5g00000001ABCAA",
+    "Status": "Pending",
+    "SourceOrg": "00D5g00000001XyEAI",
+    "SnapshotName": "MySnapshot",
+    "Description": "Baseline configuration with Package v1.2.0",
+    "Content": "metadatadata",
+    "CreatedDate": "2026-06-04T20:00:00.000+0000",
+    "CreatedBy": "0055g00000001UserEAA",
+    "LastModifiedDate": "2026-06-04T20:00:00.000+0000",
+    "LastModifiedBy": "0055g00000001UserEAA"
+  }
+}

package/skills/dx-org-manage/references/cli_flags.md

@@ -0,0 +1,67 @@
+# CLI Flags Reference
+
+Complete reference for `sf org create snapshot` command flags.
+
+## Required Flags
+
+| Flag | Alias | Description | Example |
+|------|-------|-------------|---------|
+| `--source-org` | `-o` | ID or authenticated username/alias of scratch org to snapshot | `--source-org my-scratch` |
+| `--name` | `-n` | Unique name for the snapshot | `--name MySnapshot` |
+| `--target-dev-hub` | `-v` | Dev Hub org username or alias (required unless default is set) | `--target-dev-hub DevHub` |
+
+## Optional Flags
+
+| Flag | Alias | Description | Example |
+|------|-------|-------------|---------|
+| `--description` | `-d` | Description of snapshot contents | `--description "Package v1.2.0"` |
+| `--api-version` | | Override the API version used for API requests | `--api-version 66.0` |
+
+## Global Flags
+
+| Flag | Description |
+|------|-------------|
+| `--json` | Format output as JSON (ALWAYS use this) |
+
+## Usage Patterns
+
+### Basic Snapshot Creation
+
+```bash
+sf org create snapshot --source-org my-scratch --name MySnapshot --json
+```
+
+### With Description
+
+```bash
+sf org create snapshot \
+  --source-org my-scratch \
+  --name MySnapshot \
+  --description "Baseline with Package v1.2.0" \
+  --json
+```
+
+### Using Org ID Instead of Alias
+
+```bash
+sf org create snapshot \
+  --source-org 00D5g00000001XyEAI \
+  --name MySnapshot \
+  --json
+```
+
+### Specify Dev Hub Explicitly
+
+```bash
+sf org create snapshot \
+  --source-org my-scratch \
+  --name MySnapshot \
+  --target-dev-hub MyDevHub \
+  --json
+```
+
+## Important Notes
+
+- **Source org auto-resolution**: Accepts org ID (starts with 00D) or username/alias — aliases are automatically resolved to org IDs
+- **Description best practice**: Include version control reference (git tag, commit SHA) to track snapshot contents
+- **Asynchronous creation**: Snapshot creation happens asynchronously — use `sf org get snapshot` to check status

package/skills/dx-org-manage/references/creating-scratch-org.md

@@ -0,0 +1,164 @@
+# Creating Scratch Orgs
+
+Detailed workflow for creating Salesforce scratch orgs using `sf org create scratch`. Supports four creation methods: definition file, edition flag, snapshot, and org shape.
+
+---
+
+## Required Inputs
+
+Gather or infer before proceeding:
+
+- **Dev Hub org**: Username or alias of authenticated Dev Hub (or use default from `target-dev-hub` config)
+- **Creation method**: Which approach to use (see Workflow step 1)
+- **Alias**: Optional but recommended for easy reference
+
+Optional but commonly used:
+- **Duration**: Days before org expires (default: 7, max: 30)
+- **Set as default**: Whether to make this the default org
+- **Source tracking**: Whether to enable (default: yes, disable for CI/CD performance)
+
+---
+
+## Workflow
+
+### 1. Identify creation method
+
+Determine which approach based on user request:
+
+| Method | When to use | Required flags |
+|--------|-------------|----------------|
+| Definition file | User provides config file or needs org features/settings | `--definition-file <path>` |
+| Edition only | Quick simple org, no special config needed | `--edition <edition>` |
+| Snapshot | Clone from existing snapshot | `--snapshot <name>` |
+| Org shape | Mimic another org's structure | `--source-org <id>` |
+
+**Mutually exclusive**: `--edition`, `--snapshot`, and `--source-org` cannot be combined.
+
+### 2. Verify Dev Hub authentication
+
+Check if Dev Hub is authenticated:
+- If `--target-dev-hub` not provided, check `sf config get target-dev-hub`
+- If no Dev Hub configured, prompt user to authenticate: `sf org login web --set-default-dev-hub`
+
+### 3. Build the command
+
+Construct based on creation method:
+
+**Definition file approach:**
+```bash
+sf org create scratch --definition-file <path> --target-dev-hub <alias> --alias <name> --json
+```
+
+**Edition-only approach:**
+```bash
+sf org create scratch --edition developer --target-dev-hub <alias> --alias <name> --json
+```
+
+**Snapshot approach:**
+```bash
+sf org create scratch --snapshot <name> --target-dev-hub <alias> --alias <name> --json
+```
+
+**Org shape approach:**
+```bash
+sf org create scratch --source-org <id> --target-dev-hub <alias> --alias <name> --json
+```
+
+**Common optional flags:**
+- `--duration-days <days>` — Set expiration (default 7, max 30)
+- `--set-default` — Make this the default org
+- `--no-track-source` — Disable source tracking for CI/CD performance
+- `--wait <minutes>` — Wait for completion (default 5 minutes, min 2)
+- `--async` — Return immediately, don't wait for completion
+
+**⚠️ CRITICAL: This is a BLOCKING command**
+- The command **WAITS** until the scratch org is fully created (or times out)
+- When the command returns success, the org is **READY TO USE** — do NOT poll with `sf org list` waiting for it to become ready
+- The JSON response with `username` and `orgId` means creation is **COMPLETE**
+- Only use `--async` if you want to check status later with `sf org resume scratch`
+- **Note**: SKILL.md Step 4 requires running `sf org list --json` once after creation for artifact collection (not for polling status)
+
+**Before executing, verify:**
+- [ ] `--json` flag is present in the command
+- [ ] At least ONE of `--edition`, `--snapshot`, `--source-org`, or `--definition-file` is specified (flags can override definition file values)
+- [ ] `--snapshot` and `--source-org` are not combined (mutually exclusive)
+- [ ] `--target-dev-hub` is resolved (either in command or from config)
+
+### 4. Handle async creation
+
+If `--async` or `--wait` timeout occurs:
+- CLI displays: "The scratch org did not complete within your wait time."
+- CLI automatically shows the resume command with Request ID
+- Timeout exits with code 69
+- User can resume with the displayed command: `sf org resume scratch --job-id <request-id> --json`
+
+### 5. Report result
+
+When the command returns, check JSON response. If it contains `username` and `orgId`, the org is **COMPLETE and READY**. Do NOT run additional commands to verify completion.
+
+Successful creation returns:
+```json
+{
+   "username": "test-...@example.com",
+   "orgId": "00D...",
+   "scratchOrgInfo": {
+      "Id": "2SR...",
+      "ScratchOrg": "00D...",
+      "SignupUsername": "test-...@example.com"
+   }
+}
+```
+
+This JSON response means: org is created, authenticated, and ready for `sf org open`, `sf project deploy`, or any other commands.
+
+---
+
+## Rules / Constraints
+
+| Constraint | Rationale |
+|-----------|-----------|
+| Always include `--json` flag | Returns structured output for parsing success/failure |
+| **Command blocks until completion — do NOT poll for status** | The command waits until the org is created (or times out). When it returns with `username` and `orgId` in JSON, the org is ready. Do NOT poll repeatedly with `sf org list` waiting for it to become ready — the command already waited for you. Only exception: if using `--async` flag or command timed out (exit code 69), then use `sf org resume scratch` to check status. **Note**: SKILL.md Step 4 requires a single `sf org list --json` call after creation for artifact collection (not polling) |
+| Dev Hub must be authenticated | Scratch org creation requires Dev Hub access |
+| `--edition`, `--snapshot`, `--source-org` are mutually exclusive | Only one creation source allowed per command |
+| Definition file overrides can use flags | Flags like `--edition`, `--name`, `--username`, `--release`, `--admin-email` override definition file values |
+| Snapshot requires same Dev Hub | Snapshot must be created in the same Dev Hub you're using |
+| Duration max is 30 days | Platform limit for scratch org expiration |
+| Source tracking enabled by default | Disable with `--no-track-source` only for CI/CD or performance needs |
+
+---
+
+## Troubleshooting
+
+| Issue | Resolution |
+|-------|------------|
+| `No default Dev Hub org found` | Authenticate Dev Hub with `sf org login web --set-default-dev-hub` or specify `--target-dev-hub` |
+| `NamedOrgNotFoundError` on Dev Hub | Dev Hub org is not authenticated — run `sf org login web` |
+| `edition value must be one of` | Invalid edition specified — use developer, enterprise, group, professional, or partner variants |
+| `Snapshot not found` | Snapshot doesn't exist in this Dev Hub — run `sf org list snapshot` to see available |
+| `sourceOrg value must be 15 or 18 characters` | Org shape ID format incorrect — use output from `sf org list shape` |
+| `The org could not be created` | Generic creation failure — check Dev Hub limits, licensing, or try again |
+| Timeout during creation (exit code 69) | Command timed out waiting for org. CLI displays the resume command with Request ID. User can run the displayed command or increase `--wait` time (min 2 minutes) for next attempt |
+| `Definition file not found` | Path to definition file is incorrect — verify file exists |
+| Partner editions unavailable | Partner editions only work if Dev Hub is a Partner Business Org |
+
+---
+
+## Output Expectations
+
+Deliverables:
+- **Created scratch org**: Authenticated and ready to use
+- **JSON response**: Contains `username`, `orgId`, `scratchOrgInfo` with Request ID
+- **Local auth info**: Stored in `.sf/` directory for future CLI commands
+
+If `--async` used or timeout occurs:
+- **Request ID**: Returned in `scratchOrgInfo.Id` (format: `2SR...`)
+- **Resume command**: `sf org resume scratch --job-id <request-id> --json`
+- **Timeout exit code**: 69
+
+---
+
+## Additional Resources
+
+- See `definition_file_options.md` for org features, settings, and configuration templates
+- See `edition_types.md` for available edition types and when to use each

package/skills/dx-org-manage/references/creating-snapshot.md

@@ -0,0 +1,103 @@
+# Creating Snapshots
+
+Creates a point-in-time snapshot of a scratch org using `sf org create snapshot`. Snapshots preserve scratch org state and configuration for reuse in scratch org definition files.
+
+---
+
+## Required Inputs
+
+Infer from the user's request:
+
+- **Source org**: Scratch org ID (starts with 00D) or username/alias to snapshot
+- **Snapshot name**: Unique name for the snapshot (required)
+- **Dev Hub**: Dev Hub org alias/username (uses default if not specified)
+- **Description** (optional): Document snapshot contents, version control reference
+
+---
+
+## Workflow
+
+1. **Gather inputs** — get source org, snapshot name, and optional description
+2. **Build command** — construct `sf org create snapshot` with appropriate flags
+3. **Execute via Bash tool** — run command with `--json` flag
+4. **Return result** — report snapshot ID and status
+
+### Command Patterns
+
+| User intent | Execute via Bash tool |
+|-------------|---------|
+| Create snapshot with name only | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --json` |
+| Create snapshot with description | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --description "<desc>" --json` |
+| Specify Dev Hub explicitly | `sf org create snapshot --source-org <orgId or alias> --name <SnapshotName> --target-dev-hub <devHubAlias> --json` |
+
+---
+
+## Rules / Constraints
+
+| Constraint | Rationale |
+|-----------|-----------|
+| Always use `--json` flag | Provides structured output for reliable parsing and error handling |
+| Snapshot names must be unique in the Dev Hub | Duplicate names cause creation to fail |
+| Source org must be a scratch org | Snapshots only work with scratch orgs, not sandboxes or production orgs |
+| Dev Hub must have snapshot feature enabled | "NOT_FOUND" error means Dev Hub doesn't support snapshots |
+| Source org accepts ID or username/alias | Command auto-resolves aliases to org IDs; org IDs start with 00D |
+| Include description for tracking | Best practice: reference version control tag or commit ID in description |
+
+---
+
+## Troubleshooting
+
+| Issue | Resolution |
+|-------|------------|
+| "NOT_FOUND" error when creating snapshot | Dev Hub doesn't have snapshot feature enabled — contact admin to enable in Dev Hub settings |
+| "No org found for <alias>" error | Source org alias doesn't exist or isn't authenticated — verify with `sf org list` |
+| Snapshot name already exists | Use a different unique name — snapshot names must be unique per Dev Hub |
+| "An error while created the org snapshot" | Generic error — check that source org is a scratch org and still active |
+| Long-running snapshot creation | Use `sf org get snapshot --snapshot <name>` to check status — snapshot creation is asynchronous |
+
+---
+
+## Output Expectations
+
+The command returns JSON output with the created snapshot details.
+
+See `examples/snapshots/success_output.json` and `examples/snapshots/error_output.json` for complete response structures.
+
+Example success response:
+```json
+{
+  "result": {
+    "SnapshotId": "0Ym...",
+    "SnapshotName": "MySnapshot",
+    "Status": "Active",
+    "SourceOrg": "00D..."
+  }
+}
+```
+
+---
+
+## Using Snapshots
+
+After creating a snapshot, use it to create scratch orgs by:
+
+1. **In scratch org definition file:**
+   ```json
+   {
+     "snapshot": "MySnapshot"
+   }
+   ```
+
+2. **Or via command flag:**
+   ```bash
+   sf org create scratch --snapshot MySnapshot --target-dev-hub <alias> --alias <name> --json
+   ```
+
+See `snapshot_usage.md` for detailed examples.
+
+---
+
+## Additional Resources
+
+- See `cli_flags.md` for detailed explanation of all available flags
+- See `snapshot_usage.md` for how to use snapshots in scratch org creation

package/skills/dx-org-manage/references/definition_file_options.md

@@ -0,0 +1,224 @@
+# Scratch Org Definition File Options
+
+Complete reference for scratch org definition file configuration. Use this when users need to configure org features, settings, or advanced options beyond basic org creation.
+
+## File Structure
+
+```json
+{
+  "orgName": "My Company",
+  "edition": "Developer",
+  "features": ["<feature>", "<feature>"],
+  "settings": {
+    "<SettingType>": {
+      "<settingName>": <value>
+    }
+  },
+  "adminEmail": "admin@example.com",
+  "description": "Scratch org for feature X development",
+  "hasSampleData": false,
+  "snapshot": "SnapshotName",
+  "sourceOrg": "00D1234567890ABC",
+  "username": "custom.username@example.com"
+}
+```
+
+## Core Fields
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| `orgName` | string | Yes | Name of the company (user-visible) |
+| `edition` | string | Yes* | Developer, Enterprise, Group, Professional, or Partner variants |
+| `adminEmail` | string | No | Email for the admin user |
+| `description` | string | No | Description shown in Dev Hub |
+| `hasSampleData` | boolean | No | Include standard sample data (default: false) |
+| `username` | string | No | Custom username for admin (must be globally unique) |
+
+\* Not required if using `snapshot` or `sourceOrg`.
+
+**CLI Flag Overrides:** When using a definition file with `--definition-file`, you can override any of these fields with CLI flags:
+- `--edition` overrides `edition`
+- `--name` overrides `orgName`
+- `--username` overrides `username`
+- `--description` overrides `description`
+- `--admin-email` overrides `adminEmail`
+- `--release` overrides `release`
+- `--snapshot` overrides `snapshot`
+- `--source-org` overrides `sourceOrg`
+
+CLI flags take precedence over definition file values.
+
+## Features Array
+
+Enable org features by adding to `features` array. Common features:
+
+```json
+"features": [
+  "Communities",
+  "ServiceCloud",
+  "Sites",
+  "MultiCurrency",
+  "PersonAccounts",
+  "Walkthroughs",
+  "AdvancedPersonAccountSecurity"
+]
+```
+
+**Finding available features:**
+- Run: `sf org list metadata-types --target-org <dev-hub>`
+- Look for `FeatureParameterValueSet` type
+- Or check: https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm
+
+## Settings Object
+
+Configure org settings by type. Format:
+
+```json
+"settings": {
+  "lightningExperienceSettings": {
+    "enableS1DesktopEnabled": true
+  },
+  "mobileSettings": {
+    "enableS1EncryptedStoragePref2": false
+  },
+  "securitySettings": {
+    "passwordPolicies": {
+      "minimumPasswordLength": 10
+    }
+  }
+}
+```
+
+**Common settings:**
+
+### Language Settings
+```json
+"languageSettings": {
+  "enableTranslationWorkbench": true
+}
+```
+
+### Chatter Settings
+```json
+"chatterSettings": {
+  "enableChatter": true
+}
+```
+
+### Path Settings
+```json
+"pathAssistantSettings": {
+  "pathAssistantEnabled": true
+}
+```
+
+## Alternative Creation Sources
+
+### Snapshot
+```json
+{
+  "snapshot": "BaselineSnapshot"
+}
+```
+
+Creates org from a snapshot. The `edition` field is optional when using snapshots.
+
+### Source Org (Org Shape)
+```json
+{
+  "sourceOrg": "00D1234567890ABC"
+}
+```
+
+Creates org from an org shape. The `edition` field is optional when using org shapes.
+
+**Note:** `snapshot` and `sourceOrg` are mutually exclusive.
+
+## Release Overrides
+
+Control which Salesforce release the scratch org uses:
+
+```json
+{
+  "release": "preview"
+}
+```
+
+Options: `preview` (next release), `previous` (previous release). Only use during Salesforce release transition periods.
+
+## Duration Control
+
+While not part of the definition file, you can override duration with the CLI flag:
+```bash
+--duration-days 15
+```
+
+Maximum: 30 days. Default: 7 days.
+
+## Packaging Options
+
+```json
+{
+  "ancestorId": "04t...",
+  "ancestorVersion": "1.0",
+  "namespace": "myns"
+}
+```
+
+Used for second-generation package (2GP) development.
+
+**CLI Packaging Flags:**
+- `--no-ancestors` - Exclude 2GP ancestors from the scratch org
+- `--no-namespace` - Create scratch org without namespace, even if Dev Hub has one
+
+## Example: Full Configuration
+
+```json
+{
+  "orgName": "Acme Corp Dev Org",
+  "edition": "Developer",
+  "description": "Feature X development scratch org",
+  "adminEmail": "dev-team@acme.com",
+  "hasSampleData": false,
+  "features": [
+    "Communities",
+    "ServiceCloud",
+    "MultiCurrency"
+  ],
+  "settings": {
+    "lightningExperienceSettings": {
+      "enableS1DesktopEnabled": true
+    },
+    "securitySettings": {
+      "passwordPolicies": {
+        "minimumPasswordLength": 10,
+        "minimumPasswordLifetime": false,
+        "obscure": false
+      }
+    },
+    "languageSettings": {
+      "enableTranslationWorkbench": true
+    }
+  }
+}
+```
+
+## Connected App Authentication
+
+For enhanced security, use a Connected App for authentication:
+
+```bash
+sf org create scratch --definition-file config.json --client-id <consumer-key>
+```
+
+When `--client-id` is provided, CLI prompts for the client secret. The scratch org will use the Connected App for authentication instead of default JWT.
+
+## Common Pitfalls
+
+| Issue | Cause | Fix |
+|-------|-------|-----|
+| Features not available | Feature name spelled wrong or not available in edition | Check feature name spelling and edition compatibility |
+| Settings ignored | Invalid setting name or structure | Verify setting exists in Metadata API docs |
+| JSON parse error | Invalid JSON syntax | Validate JSON with linter |
+| Conflicting options | Both `snapshot` and `sourceOrg` specified | Use only one alternative creation source |
+| CLI flag ignored | Trying to override a field that doesn't support override | Only certain fields can be overridden (see CLI Flag Overrides section) |

package/skills/dx-org-manage/references/edition_types.md

@@ -0,0 +1,78 @@
+# Scratch Org Edition Types
+
+Reference for choosing the right Salesforce edition for scratch org creation.
+
+## Available Editions
+
+| Edition | When to use | License limits | Features |
+|---------|-------------|----------------|----------|
+| `developer` | Default choice for most development | 2 user licenses | Most features available, best for general development |
+| `enterprise` | Enterprise-specific features needed | 5 user licenses | All enterprise features, territory management, advanced approvals |
+| `group` | Testing Professional edition behavior | 5 user licenses | Professional edition features |
+| `professional` | Professional edition-specific testing | 5 user licenses | Professional edition feature set |
+
+## Partner Editions
+
+Only available if the Dev Hub is a Partner Business Org:
+
+| Edition | When to use |
+|---------|-------------|
+| `partner developer` | Partner app development |
+| `partner enterprise` | Partner enterprise app testing |
+| `partner group` | Partner professional edition testing |
+| `partner professional` | Partner professional edition apps |
+
+## Edition Comparison
+
+### Developer Edition (Recommended Default)
+- **Best for**: General development, most common use case
+- **Features**: Apex, Visualforce, Lightning, Process Builder, Flow, most platform features
+- **Limitations**: 2 user licenses (sufficient for most dev work)
+- **Use when**: User doesn't specify or needs general Salesforce development environment
+
+### Enterprise Edition
+- **Best for**: Enterprise-specific features, larger team testing
+- **Additional features**: Territory Management 2.0, Advanced Approval Processes
+- **Use when**: Testing enterprise-only features or need more than 2 users
+
+### Group/Professional Edition
+- **Best for**: Testing behavior specific to Professional edition
+- **Use when**: Building apps for Professional edition customers or testing edition-specific constraints
+
+## Choosing an Edition
+
+Follow this decision tree:
+
+```text
+1. Does user specify edition? → Use specified edition
+2. Does user need Partner edition? → Check if Dev Hub is Partner Business Org
+3. Does user need Enterprise features? → Use enterprise
+4. Default → Use developer
+```
+
+## CLI Usage
+
+**With flag:**
+```bash
+sf org create scratch --edition developer --alias my-org
+```
+
+**With definition file:**
+```json
+{
+  "edition": "Developer"
+}
+```
+
+**Important notes:**
+- Edition value is case-insensitive in CLI flags but case-sensitive in definition files (capital first letter)
+- Partner editions use space format: `partner developer`, `partner enterprise`, etc. (no hyphen)
+- CLI flag `--edition` overrides definition file `edition` if both are specified
+
+## Common Errors
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `edition value must be one of` | Invalid edition name | Use: developer, enterprise, group, professional, or partner editions (e.g., "partner developer") |
+| Partner edition not available | Dev Hub is not a Partner Business Org | Use non-partner edition or switch to Partner Dev Hub |
+| Features not available in edition | Requested features not available in chosen edition | Use Enterprise edition or remove unavailable features |