@salesforce/afv-skills 1.45.0 → 1.47.0

package/skills/life-sciences-fieldsalesrep-coordinate/references/stage-2-starter-config-profile-layout-assignments.md

@@ -0,0 +1,171 @@
+# Profile Layout Assignments Reference
+
+## Overview
+
+After page layouts are deployed (Step 10), the skeleton profile files must be updated with `<layoutAssignments>` entries that map each layout to its object and optionally a record type.
+
+Both profile files under `.lsc-starter-config/LSStarterConfig/PackageComponents/profiles/SkeletonProfile/` must be updated:
+- `LSC Custom Profile.profile-meta.xml`
+- `Admin.profile-meta.xml`
+
+## Layout-to-Object/RecordType Mapping
+
+| Layout File | Object | Record Type (if applicable) |
+|-------------|--------|---------------------------|
+| Account-HCO Account Layout | Account | Health_Care_Organization |
+| ActivityPlanTerritory-Activity Plan Territory Layout | ActivityPlanTerritory | — |
+| Case-LSC Case Layout | Case | Medical_Info_Request, Medical_Inquiry, Question |
+| CommSubscription-Communication Subscription Layout | CommSubscription | — |
+| CommSubscriptionChannelType-Communication Subscription Channel Type Layout | CommSubscriptionChannelType | — |
+| CommSubscriptionConsent-Communication Subscription Consent Layout | CommSubscriptionConsent | — |
+| HealthcareProvider-Healthcare Provider Layout | HealthcareProvider | Health_Care_Organization, Health_Care_Provider |
+| Inquiry-LSC Inquiry Layout | Inquiry | Adverse_Event, LSC_General, Medical_Inquiry |
+| InquiryQuestion-LSC Inquiry Question Layout | InquiryQuestion | — |
+| InquiryQuestionAnswer-LSC Inquiry Question Answer Layout | InquiryQuestionAnswer | — |
+| PersonAccount-Person Account HCP Layout | PersonAccount | Health_Care_Provider, PersonAccount |
+| ProviderVisit-LSC Provider Visit Layout | ProviderVisit | — |
+| ProviderVisitProdDiscussion-Product Feedback | ProviderVisitProdDiscussion | Patient_Tracking, Product_Feedback |
+| Visit-LSC Visit Layout | Visit | — |
+
+## XML Format for layoutAssignments
+
+Insert these entries directly, right before the closing `</Profile>` tag in each file. This is a mechanical edit driven by the Step 10 layout selection — do not show the block for review or ask the user to confirm the profile edit (see the Step 11 note in `overview.md`). Placement inside `<Profile>` is not order-sensitive; before `</Profile>` is always valid.
+
+### Without Record Type
+
+```xml
+<layoutAssignments>
+    <layout>Account-HCO Account Layout</layout>
+</layoutAssignments>
+```
+
+### With Record Type
+
+When a layout is assigned to specific record types, add one entry per record type:
+
+```xml
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Medical_Info_Request</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Medical_Inquiry</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Question</recordType>
+</layoutAssignments>
+```
+
+## Full layoutAssignments Block (All Layouts)
+
+If all layouts are selected, add these entries to both profiles:
+
+```xml
+<layoutAssignments>
+    <layout>Account-HCO Account Layout</layout>
+    <recordType>Account.Health_Care_Organization</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>ActivityPlanTerritory-Activity Plan Territory Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Medical_Info_Request</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Medical_Inquiry</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Case-LSC Case Layout</layout>
+    <recordType>Case.Question</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>CommSubscription-Communication Subscription Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>CommSubscriptionChannelType-Communication Subscription Channel Type Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>CommSubscriptionConsent-Communication Subscription Consent Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>HealthcareProvider-Healthcare Provider Layout</layout>
+    <recordType>HealthcareProvider.Health_Care_Organization</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>HealthcareProvider-Healthcare Provider Layout</layout>
+    <recordType>HealthcareProvider.Health_Care_Provider</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.Adverse_Event</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.LSC_General</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.Medical_Inquiry</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>InquiryQuestion-LSC Inquiry Question Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>InquiryQuestionAnswer-LSC Inquiry Question Answer Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>PersonAccount-Person Account HCP Layout</layout>
+    <recordType>PersonAccount.Health_Care_Provider</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>PersonAccount-Person Account HCP Layout</layout>
+    <recordType>PersonAccount.PersonAccount</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>ProviderVisit-LSC Provider Visit Layout</layout>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>ProviderVisitProdDiscussion-Product Feedback</layout>
+    <recordType>ProviderVisitProdDiscussion.Patient_Tracking</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>ProviderVisitProdDiscussion-Product Feedback</layout>
+    <recordType>ProviderVisitProdDiscussion.Product_Feedback</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Visit-LSC Visit Layout</layout>
+</layoutAssignments>
+```
+
+## Selective Assignment
+
+If the user selected only specific layouts, include only the `<layoutAssignments>` entries for those layouts. For example, if only "Inquiry-LSC Inquiry Layout" and "Visit-LSC Visit Layout" were selected:
+
+```xml
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.Adverse_Event</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.LSC_General</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Inquiry-LSC Inquiry Layout</layout>
+    <recordType>Inquiry.Medical_Inquiry</recordType>
+</layoutAssignments>
+<layoutAssignments>
+    <layout>Visit-LSC Visit Layout</layout>
+</layoutAssignments>
+```
+
+## Deploy Updated Profiles
+
+After adding layout assignments, deploy both profiles:
+```bash
+sf project deploy start --source-dir .lsc-starter-config/LSStarterConfig/PackageComponents/profiles/SkeletonProfile --target-org <org>
+```

package/skills/life-sciences-fieldsalesrep-coordinate/references/stage-2-starter-config-state-tracking.md

@@ -0,0 +1,64 @@
+# Deployment State Tracking
+
+Maintain a deployment state object throughout the workflow. This enables pause/resume and partial-deploy recovery.
+
+```text
+State = {
+  targetOrg: string,
+  steps: [
+    { name: "StandardValueSets", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "Objects", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "ProductSpecificationTypes", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "ProductSpecificationRecTypes", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "QuickActions", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "SkeletonProfile", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "LifeSciConfigRecords", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "LifeSciMetadataRecords", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "TriggerHandlers", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "PageLayouts", status: "pending|in-progress|done|failed", selected?: [], deployed?: [], detail?: string },
+    { name: "ProfileLayoutAssignments", status: "pending|in-progress|done|failed", detail?: string },
+    { name: "FlexiPages", status: "pending|in-progress|done|failed", selected?: [], deployed?: [], detail?: string },
+    { name: "ApplicationUpdate", status: "pending|in-progress|done|failed", detail?: string }
+  ]
+}
+```
+
+On failure at any step, show:
+
+```text
+Deployment paused at step: <StepName>
+    Completed: <N>/<Total> steps
+    Failed component: <component-name>
+    Error: <error-message>
+
+Options:
+  1. Retry failed step
+  2. Skip and continue
+  3. Roll back (where applicable)
+```
+
+Wait for user choice before continuing.
+
+## Progress Display
+
+After each step completes, display progress:
+
+```text
+[done]    Step 1/13: StandardValueSets — deployed
+[done]    Step 2/13: Objects — deployed
+[done]    Step 3/13: ProductSpecificationTypes — deployed
+[current] Step 4/13: ProductSpecificationRecTypes — in progress...
+[pending] Step 5/13: QuickActions — pending
+```
+
+At the end, show final summary:
+
+```text
+LSC Starter Config Deployment Complete
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+13/13 steps completed successfully
+   - 14 layouts deployed (user selected: all)
+   - 8 flexipages deployed (user selected: all)
+   - 28 trigger handlers activated
+   - Application file updated for selected flexipages
+```

package/skills/life-sciences-fieldsalesrep-coordinate/references/stage-2-starter-config-trigger-handlers.md

@@ -0,0 +1,122 @@
+# Trigger Handlers Reference
+
+## Handler List
+
+The following trigger handlers must be activated:
+
+1. AffiliationUniquenessGenericHandler
+2. AffiliationUniquenessHandler
+3. HardAffiliationHandler
+4. AffiliationReciprocalHandler
+5. HealthcareProviderAffiliationHandler
+6. AffiliationPrimaryChangeHandler
+7. AffiliationAccountUpdateHandler
+8. TerrAcctRcmdActionSharingHandler
+9. TerrAccRcmActStatusUpdateHandler
+10. CaseMSLQueueHandler
+11. CaseChangeOwnershipHandler
+12. CaseShareToCreatorHandler
+13. StagePathPermissionsHandler
+14. AccountPlanDeleteChildrenHandler
+15. AccountPlanChangeStatusHandler
+16. SetAccPlanPercentCompleteHandler
+17. AcctPlanObjDeleteChildrenHandler
+18. SetAccObjectPercentCompleteHandler
+19. ActionPlanDeleteChildrenHandler
+20. SetSprintPercentCompleteHandler
+21. SetGoalAsgmtPercentCompleteHandler
+22. SetActionPlanPercentCompleteHandler
+23. AssessmentTaskDeleteAPItemHandler
+24. AssessmentTaskSharingHandler
+25. TerritoryBusinessPlanDeleteHandler
+26. GoalAssignmentDeleteHandler
+27. TerritoryBusPlanChangeStatusHandler
+28. SetTerrBusPlanPrcntCompleteHandler
+
+## Activation Method
+
+Trigger handlers in Life Sciences Cloud are **`LifeScienceTriggerHandler`** records — a standard Tooling API entity (NOT a managed `lsc4ce__TriggerHandler__c` custom object). All queries and updates MUST use `--use-tooling-api`. Relevant fields:
+
+- `DeveloperName` — the handler name (e.g. `AffiliationUniquenessGenericHandler`)
+- `IsActive` — the active flag (Boolean)
+- `ObjectApiName` — the object the handler runs on
+
+> **Verified behavior:** the standard-API sobject name `lsc4ce__TriggerHandler__c` does NOT exist and returns `sObject type '...' is not supported`. `LifeScienceTriggerHandler` is only accessible via the Tooling API. A freshly-deployed org typically has ~185 handlers, all `IsActive=false` initially; the 28 below are the subset the starter config activates.
+
+### Preferred: Query then Update (Tooling API)
+
+First, get the handler's Id and current state:
+```bash
+sf data query --query "SELECT Id, DeveloperName, IsActive FROM LifeScienceTriggerHandler WHERE DeveloperName = '<HandlerName>'" --target-org <org> --use-tooling-api --json
+```
+
+Then activate by Id:
+```bash
+sf data update record --sobject LifeScienceTriggerHandler --record-id <Id> --values "IsActive=true" --target-org <org> --use-tooling-api
+```
+
+### Batch: query all inactive IDs in one call, then update each
+
+Individual query-then-update per handler is slow (each `sf` invocation has startup overhead; 28 sequential handlers can exceed 2 minutes). Fetch all still-inactive IDs in ONE query, then loop the updates.
+
+> **STOP-GATE (do not drop the last handler).** Build the update loop so it processes **every** returned ID. Two failure modes to avoid: **(1)** a naive `while read` over a *captured* ID list drops the final ID when that list has no trailing newline (the classic "27 of 28" bug); **(2)** an unquoted `for id in $IDS` loop relies on **bash word-splitting**, which **zsh does NOT do by default** — under zsh the whole multiline blob stays a single `$id`, every update fails on an invalid record-id, and you get **"0 of 28"**. Do NOT use either. The portable, shell-agnostic, drop-safe pattern is to pipe `jq` (which newline-terminates every record, including the last) into `while IFS= read -r id` via **process substitution** `< <(...)`: it behaves identically in bash and zsh and keeps the loop in the current shell so the counter survives. After the loop, always re-run the Verification query below and confirm the active count equals the full handler count (28) before proceeding — if it is short, identify the straggler(s) by name and activate each individually.
+
+Use a single query filtered to `IsActive = false` (already-active handlers are skipped automatically — re-running is safe but wasteful), then loop with one of the safe patterns:
+
+```bash
+ORG=<org>
+n=0; total=0
+# Pipe jq (newline-terminates EVERY record, incl. the last) into `while read` via
+# process substitution `< <(...)`. Portable across bash AND zsh; the loop stays in the
+# current shell so $n/$total survive. Never `for id in $IDS` (zsh won't word-split it).
+while IFS= read -r id; do
+  total=$((total+1))
+  sf data update record --sobject LifeScienceTriggerHandler --record-id "$id" \
+    --values "IsActive=true" --target-org "$ORG" --use-tooling-api >/dev/null && n=$((n+1))
+  echo "  ...$n activated"
+done < <(sf data query \
+  --query "SELECT Id FROM LifeScienceTriggerHandler WHERE IsActive = false AND DeveloperName IN ('AffiliationUniquenessGenericHandler','AffiliationUniquenessHandler','HardAffiliationHandler','AffiliationReciprocalHandler','HealthcareProviderAffiliationHandler','AffiliationPrimaryChangeHandler','AffiliationAccountUpdateHandler','TerrAcctRcmdActionSharingHandler','TerrAccRcmActStatusUpdateHandler','CaseMSLQueueHandler','CaseChangeOwnershipHandler','CaseShareToCreatorHandler','StagePathPermissionsHandler','AccountPlanDeleteChildrenHandler','AccountPlanChangeStatusHandler','SetAccPlanPercentCompleteHandler','AcctPlanObjDeleteChildrenHandler','SetAccObjectPercentCompleteHandler','ActionPlanDeleteChildrenHandler','SetSprintPercentCompleteHandler','SetGoalAsgmtPercentCompleteHandler','SetActionPlanPercentCompleteHandler','AssessmentTaskDeleteAPItemHandler','AssessmentTaskSharingHandler','TerritoryBusinessPlanDeleteHandler','GoalAssignmentDeleteHandler','TerritoryBusPlanChangeStatusHandler','SetTerrBusPlanPrcntCompleteHandler')" \
+  --target-org "$ORG" --use-tooling-api --json | jq -r '.result.records[].Id')
+echo "Activated $n of $total inactive handler(s)."
+```
+
+If every one of the 28 was already active, the query returns zero rows and the loop is a no-op — that is a valid PASS, not a failure.
+
+### Verification
+
+After activation, confirm the active count equals the full handler count (28) — count directly rather than eyeballing rows:
+```bash
+sf data query --query "SELECT COUNT(Id) active FROM LifeScienceTriggerHandler WHERE IsActive = true AND DeveloperName IN ('AffiliationUniquenessGenericHandler','AffiliationUniquenessHandler','HardAffiliationHandler','AffiliationReciprocalHandler','HealthcareProviderAffiliationHandler','AffiliationPrimaryChangeHandler','AffiliationAccountUpdateHandler','TerrAcctRcmdActionSharingHandler','TerrAccRcmActStatusUpdateHandler','CaseMSLQueueHandler','CaseChangeOwnershipHandler','CaseShareToCreatorHandler','StagePathPermissionsHandler','AccountPlanDeleteChildrenHandler','AccountPlanChangeStatusHandler','SetAccPlanPercentCompleteHandler','AcctPlanObjDeleteChildrenHandler','SetAccObjectPercentCompleteHandler','ActionPlanDeleteChildrenHandler','SetSprintPercentCompleteHandler','SetGoalAsgmtPercentCompleteHandler','SetActionPlanPercentCompleteHandler','AssessmentTaskDeleteAPItemHandler','AssessmentTaskSharingHandler','TerritoryBusinessPlanDeleteHandler','GoalAssignmentDeleteHandler','TerritoryBusPlanChangeStatusHandler','SetTerrBusPlanPrcntCompleteHandler')" --target-org <org> --use-tooling-api --json
+```
+The returned `active` count MUST be **28**. If it is fewer, list the still-inactive names (query the same set with `IsActive = false`), activate each straggler individually, and re-run this count until it reads 28. Do NOT proceed to the next step while any handler is inactive.
+
+### Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| `sObject type 'lsc4ce__TriggerHandler__c' is not supported` | Wrong object name / missing tooling flag | Use `LifeScienceTriggerHandler` with `--use-tooling-api` |
+| "No records found" | Handler `DeveloperName` doesn't exist in the org | The managed package may not have created it yet; skip and note |
+| Command times out activating all 28 | Sequential per-handler `sf` calls are slow | Fetch all inactive IDs in one query, then loop updates (see the safe-loop patterns above); skip already-active ones |
+| "27 of 28 activated" / last handler skipped | A `while read` over a *captured* list dropped the final unterminated line | Use the jq-piped `while IFS= read -r` via process substitution shown above; re-run the count check and activate any straggler individually |
+| "0 of 28 activated" (loop ran once, all IDs mashed into one value) | An unquoted `for id in $IDS` loop under **zsh**, which does not word-split unquoted params — `$IDS` stayed one multiline string | Use the jq-piped `while IFS= read -r` via process substitution shown above (portable across bash/zsh); never rely on `for` word-splitting |
+| "Insufficient access" | User lacks edit permission on the tooling entity | User needs appropriate permission set |
+
+### Progress Reporting
+
+Report activation progress:
+```text
+Activating trigger handlers: 15/28 complete...
+```
+
+If any handler fails, collect all failures and report at the end:
+```text
+3 handlers could not be activated:
+  - CaseMSLQueueHandler: No record found
+  - StagePathPermissionsHandler: Field not found
+  - AssessmentTaskSharingHandler: Insufficient access
+
+25/28 handlers activated successfully.
+Options:
+  1. Retry failed handlers
+  2. Skip and continue to next step
+```