@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/health-cloud-virtual-visit-config-configure/SKILL.md

@@ -1,135 +0,0 @@
----
-name: health-cloud-virtual-visit-config-configure
-description: "Use this skill when users want to manage VirtualVisitConfig records: the Health Cloud / Life Sciences Video Calls (telehealth) configuration behind the Video Visits Settings page in Setup. Trigger when users mention virtual, visit, config, virtual visit config."
-metadata:
-  version: "1.0"
----
-
-# Managing Virtual Visit Config
-
-## When to Use This Skill
-
-Manage VirtualVisitConfig records: the Health Cloud / Life Sciences Video Calls (telehealth) configuration behind the Video Visits Settings page in Setup. The steps use standard sObject REST for create, read, update and delete. The same configuration can also be deployed through the Metadata API. Required to create: DeveloperName (unique) and MasterLabel. UsageType (CHIME, INTELLIGENT_FORM_READER, SENTIMENT_ANALYSIS, KEY_PHRASE_EXTRACTION or ENTITY_DETECTION) can be used by only one record, so creating or updating a second record to the same UsageType fails with a duplicate-value error; records with a blank UsageType are not limited. A UsageType is accepted only when the org has the matching feature enabled, otherwise the save fails with "Invalid Value for Usage Type." Run describe first to get the createable fields and the picklist values for UsageType, VisitRegion and ComprehendServiceType. NamedCredentialId is a lookup to a Named Credential holding the external video service credentials; create that record first.
-
-## Workflow
-
-Standard sObject REST provides full CRUD plus describe on VirtualVisitConfig. The fields available at runtime depend on the org and the user's permissions, so run describe first and build the payload from the createable fields. Query existing records by UsageType before creating, because only one record per UsageType is allowed; to change a record's UsageType to one already in use, delete or re-type the other record first. If the save fails with "Invalid Value for Usage Type.", the feature behind that UsageType is not enabled in the org. Use a real Named Credential Id for NamedCredentialId.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User needs create, read, update and delete access to VirtualVisitConfig. (check: `<udd:crud:VirtualVisitConfig>`)
-- The org must have at least one of the supporting features enabled: Video Calls, Einstein Document Reader, Einstein Sentiment Analysis, or the Natural Language Service (key phrase or entity detection). Without one of them the configuration is not available and the Setup page does not render. (check: `Video Calls enabled || Einstein Document Reader enabled || Sentiment analysis enabled || Key phrase extraction enabled || Entity detection enabled`)
-- User needs the Customize Application permission to create, update or delete records; reading needs View Setup. (check: `Customize Application permission`)
-- User needs at least one of: the Video Calls permission, Health Cloud access, portal access, or administrator access to Einstein Document Reader, sentiment analysis or the Natural Language Service. (check: `Video Calls permission || Health Cloud access || Portal access || Administer Einstein Document Reader || Administer sentiment analysis || Administer natural language service`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `describe` | read | — | `GET /services/data/v67.0/sobjects/VirtualVisitConfig/describe` | — |
-| `list` | read | — | `GET /services/data/v67.0/query` | — |
-| `get-by-id` | read | — | `GET /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}` | `list` |
-| `create` | write | — | `POST /services/data/v67.0/sobjects/VirtualVisitConfig` | `describe` |
-| `update` | write | — | `PATCH /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}` | `get-by-id` |
-| `delete` | write | — | `DELETE /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}` | `get-by-id` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  describe["describe (read)"]
-  list["list (read)"]
-  get_by_id["get-by-id (read)"]
-  create["create (write)"]
-  update["update (write)"]
-  delete["delete (write)"]
-  list --> get_by_id
-  describe --> create
-  get_by_id --> update
-  get_by_id --> delete
-```
-
-### Read operations
-
-#### `describe`
-
-Retrieve the VirtualVisitConfig sObject describe — fields, picklist values, FLS, createable/updateable flags.
-
-**Call:** `GET /services/data/v67.0/sobjects/VirtualVisitConfig/describe`
-
-**Output:** DescribeSObjectResult for VirtualVisitConfig — use this to build the field list for list / create / update payloads.
-
-#### `list`
-
-List VirtualVisitConfig records. Pair this with /describe first to pick field names.
-
-**Call:** `GET /services/data/v67.0/query`
-
-**Inputs:**
-
-- `where` *(`String`)* — Optional SOQL WHERE clause to filter Virtual Visit Config records.
-- `limit` *(`int`)* — Optional SOQL LIMIT value.
-- `q` *(`string`)*
-
-**Output:** Query response with records[] of VirtualVisitConfig — Id plus any SELECTed fields.
-
-#### `get-by-id`
-
-Retrieve a specific VirtualVisitConfig record by Id.
-
-**Call:** `GET /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}`
-
-**Inputs:**
-
-- `Id` *(`ID`)* — Id of the VirtualVisitConfig record to fetch.
-
-**Depends on:** `list`
-
-**Output:** Single VirtualVisitConfig record with all readable fields per user FLS.
-
-### Write operations
-
-#### `create`
-
-Create a VirtualVisitConfig record. Required: DeveloperName and MasterLabel. Run describe first for the createable fields. Only one record per UsageType is allowed in an org (duplicates fail), and a UsageType is accepted only when its feature is enabled in the org.
-
-**Call:** `POST /services/data/v67.0/sobjects/VirtualVisitConfig`
-
-**Inputs:**
-
-- `body` *(`object`)* — Field/value map for the new VirtualVisitConfig. Populate from /describe's createableFields list.
-
-**Depends on:** `describe`
-
-**Rollback:** Call delete with the returned Id to undo the create.
-
-#### `update`
-
-Update an existing VirtualVisitConfig record. Merge-patch semantics.
-
-**Call:** `PATCH /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}`
-
-**Inputs:**
-
-- `Id` *(`ID`)* — Id of the VirtualVisitConfig to update.
-- `body` *(`object`)* — Partial field/value map — only include fields you want to change.
-
-**Depends on:** `get-by-id`
-
-#### `delete`
-
-Delete a VirtualVisitConfig record.
-
-**Call:** `DELETE /services/data/v67.0/sobjects/VirtualVisitConfig/{Id}`
-
-**Inputs:**
-
-- `Id` *(`ID`)* — Id of the VirtualVisitConfig to delete.
-
-**Depends on:** `get-by-id`

package/skills/industries-account-score-settings-query/SKILL.md

@@ -1,78 +0,0 @@
----
-name: industries-account-score-settings-query
-description: "Use this skill when users want to read or toggle the Health Cloud Account Score org preference (ORG_PREFERENCE_ACCOUNT_SCORE_ENABLED). Trigger when users mention account, score, settings, account score settings."
-metadata:
-  version: "1.0"
-  accessCheck: "HealthCloudAccessCheck.ORG_HAS_HEALTH_CLOUD"
----
-
-# Querying Account Score Settings
-
-## When to Use This Skill
-
-Read or toggle the Health Cloud Account Score org preference (ORG_PREFERENCE_ACCOUNT_SCORE_ENABLED). Step 1 returns the current boolean; step 2 flips it. Both routes are AURA-IS-CANONICAL — no Connect / Tooling / sObject column exposes this single org-pref bit, and substituting Metadata API IndustriesSettings deploy is contract-lossy (drops the controller's per-call HealthCloud-license + Customize-Application gate and the single-call atomicity admins rely on). Score-range classification CRUD is rendered as a child component but lives behind a separate operation in its own setup node, not this SOR.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Org licensed for Health Cloud (HealthCloudAccessCheck.ORG_HAS_HEALTH_CLOUD). Without the license the write step throws NoAccessException; the read step returns the underlying pref but is not exposed in the Setup UI. (check: `HealthCloudAccessCheck.ORG_HAS_HEALTH_CLOUD`)
-- Caller holds Customize Application or System Administrator. Required for the toggle write; the read is ungated. (check: `Customize Application permission`)
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `handleAccountScoreEnabledToggle_2`: call `verify-handle-account-score-enabled-toggle` (`GET /headless/invoke/industries/industries-healthcare/account-score-settings/get-account-score-enabled-org-pref`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `getAccountScoreEnabledOrgPref_1` | read | implemented | `GET /headless/invoke/industries/industries-healthcare/account-score-settings/get-account-score-enabled-org-pref` | — |
-| `handleAccountScoreEnabledToggle_2` | read | implemented | `PATCH /headless/invoke/industries/industries-healthcare/account-score-settings/handle-account-score-enabled-toggle` | `getAccountScoreEnabledOrgPref_1` |
-| `verify-handle-account-score-enabled-toggle` | verify | implemented | `GET /headless/invoke/industries/industries-healthcare/account-score-settings/get-account-score-enabled-org-pref` | `handleAccountScoreEnabledToggle_2` |
-
-### Read operations
-
-#### `getAccountScoreEnabledOrgPref_1`
-
-Read ORG_PREFERENCE_ACCOUNT_SCORE_ENABLED. Returns a single boolean reflecting whether Health Cloud Account Score is on for this org. Ungated read. AURA-IS-CANONICAL: no public Connect/Tooling/sObject surface exposes this single org-pref bit, and Metadata IndustriesSettings retrieve returns ~200 sibling booleans for one bit of state.
-
-**Call:** `GET /headless/invoke/industries/industries-healthcare/account-score-settings/get-account-score-enabled-org-pref`   — status: `implemented`
-
-**Output:** JSON boolean. true = Account Score is enabled for this org; false = disabled. The toggle UI binds directly to this value.
-
-#### `handleAccountScoreEnabledToggle_2`
-
-Toggle ORG_PREFERENCE_ACCOUNT_SCORE_ENABLED. Body is a JSON boolean (true=enable, false=disable). Per-call gate enforces ORG_HAS_HEALTH_CLOUD + Customize Application (or System Admin) and throws NoAccessException on failure. AURA-IS-CANONICAL: substituting Metadata IndustriesSettings deploy is contract-lossy — async deploy job, the per-call license + perm check is bundled into deploy-result feedback rather than thrown synchronously, and atomicity for a single-pref toggle is dropped.
-
-**Call:** `PATCH /headless/invoke/industries/industries-healthcare/account-score-settings/handle-account-score-enabled-toggle`   — status: `implemented`
-
-**Inputs:**
-
-- `value` *(`boolean`)*
-
-**Depends on:** `getAccountScoreEnabledOrgPref_1`
-
-**Rollback:** Re-issue handleAccountScoreEnabledToggle_2 with the prior boolean
-captured from getAccountScoreEnabledOrgPref_1 before the write. The
-org pref is a scalar boolean and the write is idempotent — issuing
-the same value twice is a no-op; flipping back restores state. No
-separate rollback API exists.
-
-### Verify operations
-
-#### `verify-handle-account-score-enabled-toggle`
-
-Re-read ORG_PREFERENCE_ACCOUNT_SCORE_ENABLED to confirm handleAccountScoreEnabledToggle_2 set the pref to the requested value. Same backing helper as step 1; semantic verify pair (read returns the exact bit the write set).
-
-**Call:** `GET /headless/invoke/industries/industries-healthcare/account-score-settings/get-account-score-enabled-org-pref`   — status: `implemented`
-
-**Depends on:** `handleAccountScoreEnabledToggle_2`
-
-**Output:** JSON boolean equal to the value passed into handleAccountScoreEnabledToggle_2 if the toggle succeeded.

package/skills/industries-actionable-list-data-sources-dmo-configure/SKILL.md

@@ -1,177 +0,0 @@
----
-name: industries-actionable-list-data-sources-dmo-configure
-description: "Use this skill when users want to configure Data Cloud DMOs as Actionable List data sources. Trigger when users mention actionable, list, data, sources, dmo, actionable list data sources dmo."
-metadata:
-  version: "1.0"
----
-
-# Managing Actionable List Data Sources Dmo
-
-## When to Use This Skill
-
-Configure Data Cloud DMOs as Actionable List data sources. Read the Data-Space gate (`isDataSpaceEnabled` Aura — no Connect alternative for the org-feature-flag aggregate). Read and toggle the `ActionableListDMOPref` org preference via the canonical Setup Connect API `GET`/`PATCH /services/data/v67.0/setup/org/preferences/ActionableListDMOPref` (body `PreferenceCheckInputRepresentation{desiredState: boolean}` → response `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}`). Browse Data Spaces via Connect `setup.platform.data-clean-room-install-packages.getAllDataSpaces` (data-space rows), then DMOs in a chosen space via `getDmoListPaginated` (Aura — value-add DataModelListConfig filter + pagination), and inspect a DMO via `getDmoFields` / `getDmoDetails` (Aura — projected response shapes).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User holds ActionableList feature access (`@ServiceComponentAccessGuard Actionable List access`, enforced by the Actionable List DMO setup operations.java); required for the Aura-routed steps in this SOR. (check: `Actionable List access`)
-- Org has ActionableList enabled — `ActionableListDMOPref` registered behind `Actionable List enabled`; required for any pref read/write. (check: `Actionable List enabled`)
-- Connect setup-metadata routes (`setOrgPreference` / `isOrgPreferenceEnabled`) require `View Setup permission` (setup-metadata operation.java) plus per-pref WRITE access — the setup metadata provider service.setOrgPreference` line 990 calls `validateAccess(orgPreferences.keySet(), ORG_PREFERENCES, Access_Type.WRITE)` and rejects unauthorized pref names. (check: `View Setup permission`)
-- Connect `getAllDataSpaces` requires `Data Cloud setup access` (setup-access gate); apply only when the agent has admin-CDP access. (check: `Data Cloud setup access`)
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `write-org-preference`: call `verify-is-org-preference-enabled` (`GET /services/data/v67.0/setup/org/preferences/{preferenceName}`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `isDataSpaceEnabled_1` | read | implemented | `GET /headless/invoke/platform/actionable-list-data-sources-dmo` | — |
-| `verify-is-org-preference-enabled` | verify | implemented | `GET /services/data/v67.0/setup/org/preferences/{preferenceName}` | `write-org-preference` |
-| `read-all-data-spaces` | read | implemented | `GET /headless/invoke/platform/data-clean-room-install-packages/get-all-data-spaces` | `isDataSpaceEnabled_1` |
-| `read-dmo-details` | read | implemented | `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-details` | `read-dmo-list-paginated` |
-| `read-org-preference` | read | implemented | `GET /services/data/v67.0/setup/org/preferences/{preferenceName}` | `isDataSpaceEnabled_1` |
-| `write-org-preference` | write | implemented | `PATCH /services/data/v67.0/setup/org/preferences/{preferenceName}` | `read-org-preference` |
-| `read-dmo-list-paginated` | read | implemented | `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-list-paginated` | `read-all-data-spaces` |
-| `read-dmo-fields` | read | implemented | `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-fields` | `read-dmo-list-paginated` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  isDataSpaceEnabled_1["isDataSpaceEnabled_1 (read)"]
-  verify_is_org_preference_enabled["verify-is-org-preference-enabled (verify)"]
-  read_all_data_spaces["read-all-data-spaces (read)"]
-  read_dmo_details["read-dmo-details (read)"]
-  read_org_preference["read-org-preference (read)"]
-  write_org_preference["write-org-preference (write)"]
-  read_dmo_list_paginated["read-dmo-list-paginated (read)"]
-  read_dmo_fields["read-dmo-fields (read)"]
-  write_org_preference --> verify_is_org_preference_enabled
-  isDataSpaceEnabled_1 --> read_all_data_spaces
-  read_dmo_list_paginated --> read_dmo_details
-  isDataSpaceEnabled_1 --> read_org_preference
-  read_org_preference --> write_org_preference
-  read_all_data_spaces --> read_dmo_list_paginated
-  read_dmo_list_paginated --> read_dmo_fields
-```
-
-### Read operations
-
-#### `isDataSpaceEnabled_1`
-
-Read whether Data Cloud Data Spaces are enabled in the org. AURA-IS-CANONICAL: no Connect/Tooling/Metadata surface exposes this org-feature-flag bit (`getAllDataSpaces` returns the list, not the enable flag). Gates the browse subgraph.
-
-**Call:** `GET /headless/invoke/platform/actionable-list-data-sources-dmo`   — status: `implemented`
-
-**Output:** boolean — true when Data Cloud's Data Space feature is enabled in the org (Setup admin sees the DMO data-source option), false otherwise.
-
-#### `read-all-data-spaces`
-
-Return every data-space row defined on the tenant — devName, prefix, status enum (ACTIVE|PROCESSING|ERROR), type enum (DEFAULT|CUSTOM), permSet, definitionId. Schema-perfect substitute for the Aura `getDataSpaces` (same data-spaces payload shape). Throws FailToGetDataspaces on backend failure.
-
-**Call:** `GET /headless/invoke/platform/data-clean-room-install-packages/get-all-data-spaces`   — status: `implemented`
-
-**Depends on:** `isDataSpaceEnabled_1`
-
-**Output:** Array of data-space rows: id, devName, name, prefix, createdBy, modifiedDateTime, description, status (ACTIVE|PROCESSING|ERROR), type (DEFAULT|CUSTOM), permSet, definitionId, modifiedByUserName, isSharingRestricted, isPreSelectedSandboxDataspace. Agent uses `devName` as input to `read-dmo-list-paginated`.
-
-#### `read-dmo-details`
-
-Return `DataModelObject{id, name, label, category, creationType}` for one DMO by name. AURA-IS-CANONICAL: the controller projects from `MktDataModelRepresentation` (developerName/masterLabel/dataObjectCategoryDevName/creationType.apiValue); no public Connect API exposes this exact projection.
-
-**Call:** `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-details`   — status: `implemented`
-
-**Inputs:**
-
-- `dmoName` *(`string`)* — DMO developerName from `read-dmo-list-paginated.dmo[].name`. Blank/null returns null.
-
-**Depends on:** `read-dmo-list-paginated`
-
-**Output:** `DataModelObject{id, name, label, category, creationType}` or null when the DMO is not found / lookup fails.
-
-#### `read-org-preference`
-
-Read the current `ActionableListDMOPref` org preference before deciding whether to toggle. Returns `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}`. Skip the write step if the current value already matches the desired state.
-
-**Call:** `GET /services/data/v67.0/setup/org/preferences/{preferenceName}`   — status: `implemented`
-
-**Inputs:**
-
-- `preferenceName` *(`string`)* — Preference name path parameter. Use `ActionableListDMOPref` for this SOR.
-
-**Depends on:** `isDataSpaceEnabled_1`
-
-**Output:** `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}` — true when the actionable-list DMO data-source integration is enabled in the org.
-
-#### `read-dmo-list-paginated`
-
-List Data Cloud DMOs available in a chosen data space. AURA-IS-CANONICAL: the controller applies a `DataModelListConfig` filter + pagination that no public Connect API reconstructs. Returns `PaginatedDmosResponse{dmo[], totalCount}`.
-
-**Call:** `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-list-paginated`   — status: `implemented`
-
-**Inputs:**
-
-- `dataSpaceName` *(`string`)* — `devName` of the target data space from `read-all-data-spaces`.
-- `searchText` *(`string`)* — Optional case-insensitive substring filter over DMO name/label. Empty/null returns unfiltered.
-- `limit` *(`integer`)* — Page size. Positive integer.
-- `offset` *(`integer`)* — Zero-based offset for pagination. Combine with `limit` to page through results.
-
-**Depends on:** `read-all-data-spaces`
-
-**Output:** `PaginatedDmosResponse{dmo: array<{name, label, category, creationType}>, totalCount: integer}` — use `dmo[].name` as input to `read-dmo-details` / `read-dmo-fields`.
-
-#### `read-dmo-fields`
-
-Return the field metadata map for one DMO (used by the actionable-list field-picker UI). AURA-IS-CANONICAL: projects field metadata into a shape tailored to the actionable-list flow; no public Connect API reconstructs the same projection.
-
-**Call:** `GET /headless/invoke/platform/actionable-list-data-sources-dmo/get-dmo-fields`   — status: `implemented`
-
-**Inputs:**
-
-- `dmoName` *(`string`)* — DMO `developerName` from `read-dmo-list-paginated.dmo[].name`. Blank/null returns null.
-
-**Depends on:** `read-dmo-list-paginated`
-
-**Output:** Field metadata projection (map keyed by field devName). Consumers read the map to populate the actionable-list field-picker UI.
-
-### Write operations
-
-#### `write-org-preference`
-
-Toggle the `ActionableListDMOPref` org preference on or off via the canonical Setup Connect API. Body `PreferenceCheckInputRepresentation{desiredState: boolean}`. Response echoes the persisted value as `PreferenceCheckOutputRepresentation{isPreferenceEnabled}`. Resolves the enable-DMO-as-Actionable-List-source workflow.
-
-**Call:** `PATCH /services/data/v67.0/setup/org/preferences/{preferenceName}`   — status: `implemented`
-
-**Inputs:**
-
-- `preferenceName` *(`string`)* — Preference name path parameter. Use `ActionableListDMOPref` for this SOR.
-- `desiredState` *(`boolean`)* — `true` to enable the DMO data-source integration; `false` to disable it. Body is `PreferenceCheckInputRepresentation{desiredState: <this>}`.
-
-**Depends on:** `read-org-preference`
-
-**Output:** `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}` — echoes the value persisted by this call. Agent asserts this matches `desiredState`; the verify step re-reads to confirm durability.
-
-### Verify operations
-
-#### `verify-is-org-preference-enabled`
-
-Read the `ActionableListDMOPref` org preference via the canonical Setup Connect API to confirm `write-org-preference` took effect. Returns `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}`; the value MUST match the boolean written by the prior step.
-
-**Call:** `GET /services/data/v67.0/setup/org/preferences/{preferenceName}`   — status: `implemented`
-
-**Inputs:**
-
-- `preferenceName` *(`string`)* — Preference name path parameter. Use `ActionableListDMOPref` for this SOR — same value passed to the read/write preference steps. Binds the `{preferenceName}` URL segment of the verify GET.
-
-**Depends on:** `write-org-preference`
-
-**Output:** `PreferenceCheckOutputRepresentation{isPreferenceEnabled: boolean}`. Agent compares `isPreferenceEnabled` against the boolean it wrote in `write-org-preference`.