agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-provider-engagement-compliance/SKILL.md

lsc-provider-engagement-compliance

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Guides Provider Engagement Compliance (Japan EPPV and MID) setup and troubleshooting. Use when user asks about EPPV, MID, Account Compliance, 取引先コンプライアンス, compliance cycles, Care Program with ProviderEngagementCompliance, Start Compliance Action Plan, Report Compliance Activity, PrvdEngmtComplianceCycle, or reporting on cycles.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.

    line 8
  2. Distinctive:

    Only the Start Compliance Action Plan button moves a plan to In Progress (not DML, API or edit form).

    line 44
  3. Very specific:

    Run check_eppv_config for an org-wide picture, and diagnose_lsc_issue with the exact symptom.

    line 55
  4. Distinctive:

    Start missing: Action Plan layout actions list.

    line 57
  5. Distinctive:

    Never suggest OmniStudio for the mobile tab.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

How to Answer EPPV / Account Compliance Questions

Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.

User asks about...Call this tool
Setup checklist, rules, gotchas, reportingget_lsc_module_docs({ module: "provider-engagement-compliance" })
Overview, what EPPV/MID are, rep experiencesearch_lsc_knowledge({ query: "EPPV MID Provider Engagement Compliance" })
Check an org's EPPV setupcheck_eppv_config() or check_eppv_config({ profileName: "<rep profile>" })
An error or symptomdiagnose_lsc_issue({ symptom: "<error text>" }) (known causes eppv-*)
DB Schema records for the featurelist_db_schema({ filter: "ActionPlan" }), create_db_schema, assign to the rep profile
Tab / quick actionlist_navigation_tabs, add_navigation_tab, list_lsc_actions, create_quick_action
Flows, plans, cycles in the orgrun_soql on ActionPlan, PrvdEngmtComplianceCycle, AssessmentTask, CareProgram (standard objects)
Mobile cachegenerate_mobile_metadata_cache({ profileName }) — one profile per call

Admin Console data, DB Schema and actions use their dedicated tools, never run_soql.

Model in one picture

CareProgram (Category ProviderEngagementCompliance) → CareProgramProduct, ActionPlanTemplateAssignment → ActionPlanTemplateVersion (Final) → Items (PrvdEngmtComplianceCycle) + ItemValues (Name, DurationInDays); ActionPlan (TargetId = HCO, TargetReferenceRecordId = CareProgram, ActionPlanType PrvdEngmtCompliance) → PrvdEngmtComplianceCycle (generated on Start) → completed by AssessmentTask (TaskType PrvdEngmtComplianceTask) on a Completed Visit.

Setup order (what worked)

  1. Enable feature; permission sets (reps: Core + Field Sales Representative; admins: Commercial Admin + Core).
  2. Action Plan State picklist values + Admin Console status mappings (distinct value per shipped state), Care Program statuses, Assessment Task record type and field set.
  3. Action Plan Status read-only for reps (FLS).
  4. Page layouts: Care Program, Care Program Product, Action Plan Template fields, and an explicit actions list on Action Plan (else no Start button).
  5. Sharing: Action Plan Template rule; territory sharing or ownership for plans and programs.
  6. Clone, schedule and activate the four flows (Update_Assessment_Task_On_Visit_Completion_Clone completes cycles).
  7. Account Compliance tab (desktop and mobile navigation), enabled for the rep profile.
  8. Quick action AssociateCareProgram ("Report Compliance Activity" on the iPad), assigned to the rep profile.
  9. Eleven DB Schema records (DbSchema_<Object>: CareProgram, CareProgramProduct, ActionPlan, ActionPlanItem, ActionPlanTemplate, ...Version, ...Assignment, ...Item, ...ItemValue, PrvdEngmtComplianceCycle, AssessmentTask), no field filters, assigned to the rep profile.
  10. Generate the cache per profile, then sync the iPad.

Full detail: the module doc support-engineering-eppv-setup-and-troubleshooting.

Rules to state up front

  • Only the Start Compliance Action Plan button moves a plan to In Progress (not DML, API or edit form); cycles generate on Start.
  • Plan start date: on/after the Care Program start date and not after today.
  • Care Program: Announce Date ≥ today; Start ≥ Pre-cycle Start ≥ Announce. No products once announce date is today or earlier (insert at today+2, add product, then set dates to today). No back-dating.
  • Final templates/versions are locked; changes need a new template, program and plans.
  • Pre-cycle: the iPad excludes the first cycle from completed and total (8 cycles show /7).
  • A cycle completes only via Report Compliance Activity on a Completed Visit inside the cycle window, after the flow runs and the iPad syncs. Plain Create Visit never completes one. The prvd_cmpl batch actions don't write plan progress.
  • iPad: badge = plan state; cycle chip = cycle whose dates include today; 未開始/進行中/完了 filters are plan-state filters.
  • Reporting: no standard cycle report type. Use single-object custom report types and verify against SOQL (a report once showed only Cycles 1–5 of 8). Plan-by-cycle matrix needs the EPPV Cycle Matrix LWC.

Troubleshooting flow

  1. Run check_eppv_config for an org-wide picture, and diagnose_lsc_issue with the exact symptom.
  2. "Unknown Account" / "Account and Place cannot be empty": check ActionPlan.TargetId and that the account is on the device.
  3. Start missing: Action Plan layout actions list.
  4. Cycle not completing: AssessmentTask exists, visit Completed and dated in the window, flow active with no faults, then sync.
  5. One-day-off dates: UTC display.

Never suggest OmniStudio for the mobile tab; use LSC apps or standard LWCs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.