agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-mobile-validation/SKILL.md

lsc-mobile-validation

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Validates Life Sciences Cloud (LSC) Mobile app configuration to prevent issues. Use when user is preparing for mobile deployment, troubleshooting mobile sync issues, or asking about DB Schema / mobile cache configuration.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    IMPORTANT: When validating mobile configuration, use the audit_mobile_config tool to run automated checks.

    line 15
  2. Distinctive:

    If validation reveals missing features or misconfiguration:

    line 28
  3. Very specific:

    If the user reports a specific error message, use diagnose_lsc_issue.

    line 36
  4. Distinctive:

    When validating mobile configuration:

    line 111
  5. Distinctive:

    Fix: Ensure Status is Active/Published and IntegrationStatus is Ok

    line 151
  6. Distinctive:

    Fix: Ensure required schemas are assigned to the profile

    line 169

≈ “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

For mobile validation rules and guidance, call search_lsc_knowledge({ query: "mobile validation configuration" }) to get sourced documentation.

LSC Mobile Configuration Validator

You help validate LSC mobile app configuration to prevent sync and functionality issues.

Automated Validation

IMPORTANT: When validating mobile configuration, use the audit_mobile_config tool to run automated checks. This tool validates against known common issues and provides specific resolution steps.

Quick Validation Groups

ScenarioCommand
User can't log inaudit_mobile_config({ group: 'mobile-login-check' })
Before go-liveaudit_mobile_config({ group: 'pre-deployment' })
Sync not workingaudit_mobile_config({ group: 'sync-troubleshooting' })
Full health checkaudit_mobile_config({ group: 'full-mobile-audit' })

Check Trigger Handlers & Admin Console Settings

If validation reveals missing features or misconfiguration:

  • list_trigger_handlers() — Check if required trigger handlers are enabled
  • toggle_trigger_handler({ handlerName: "...", active: true }) — Enable/disable a handler
  • list_admin_settings({ category: "..." }) — View Admin Console settings for a category
  • update_admin_setting({ recordId: "...", fields: { IsActive: true } }) — Update a setting

Diagnosing Specific Errors

If the user reports a specific error message, use diagnose_lsc_issue. It finds matching known causes and validation rules and checks the org for them:

diagnose_lsc_issue({ symptom: 'Device sync transaction record was not found' })

Mobile Cache Status

USE THE check_mobile_cache_status TOOL to check cache status. Do NOT write SOQL queries manually.

check_mobile_cache_status()

Objects that DO NOT EXIST (never query these):

  • MobileMetadataCache__c, MobileApplicationDetail, lsc4ce__MobileMetadataCache__c - NONE OF THESE EXIST

The correct object is LifeSciMobileMetadataRecord but the tool handles this for you.

Key Fields (for reference)

FieldDescription
NameName of the DB Schema record
ProfileIdProfile this schema is assigned to
StatusActive, Inactive, New, Published, Processing, etc.
IntegrationStatusError, New, Ok, Pending
IntegrationErrorCodeError code if sync failed
IntegrationErrorMessageError details if sync failed

Admin Console Location

Admin Console > Mobile > Object Metadata Cache Configuration

This is where admins create and manage DB Schema records through the UI.

Tip: For managing individual DbSchema records (create, update, delete, SOQL filters), see the lsc-db-schema skill.

Required DB Schema Records by Feature

Each LSC feature requires specific DB Schema records to be active for mobile:

Field Email

  • Email template records
  • Email fragment records
  • Consent/subscription records

Next Best Action (NBA)

  • NBA configuration records
  • Action records

Next Best Customer (NBC)

  • NBC settings records
  • Provider/Account related records

Lists & Filters

  • Actionable list records

App Alerts/Notifications

  • Alert configuration records

Visit Management

  • Visit records
  • Product discussion records
  • Sample records (if sampling enabled)

Sample Management

  • Sample limit records
  • Sample inventory records
  • Sample transaction records

Validation Workflow

When validating mobile configuration:

  1. Check setup status:
    Use check_lsc_setup to verify org connection
  2. Query all mobile metadata records:
    SELECT Id, Name, Status, IntegrationStatus, IntegrationErrorCode, IntegrationErrorMessage
    FROM LifeSciMobileMetadataRecord
    ORDER BY Name
  3. Identify issues:
    • Records with IntegrationStatus = 'Error'
    • Records with Status != 'Active' and Status != 'Published'
    • Missing records for enabled features
  4. Check profile assignments:
    SELECT Id, Name, Profile.Name, Status
    FROM LifeSciMobileMetadataRecord
    WHERE ProfileId != null
  5. Report findings:
    • List all configured schemas
    • Flag any errors or inactive records
    • Identify potentially missing schemas based on enabled features

Common Mobile Issues

Data Not Appearing on Mobile

Query to run:

SELECT Id, Name, Status, IntegrationStatus
FROM LifeSciMobileMetadataRecord
WHERE Name LIKE '%<feature>%'

Fix: Ensure Status is Active/Published and IntegrationStatus is Ok

Mobile Sync Failures

Query to run:

SELECT Id, Name, IntegrationErrorCode, IntegrationErrorMessage
FROM LifeSciMobileMetadataRecord
WHERE IntegrationStatus = 'Error'

Fix: Review error messages and correct configuration

Feature Not Working for Specific Profile

Query to run:

SELECT Id, Name, Profile.Name, Status
FROM LifeSciMobileMetadataRecord
WHERE Profile.Name = '<profile_name>'

Fix: Ensure required schemas are assigned to the profile

Mobile Sync Objects

For deeper sync troubleshooting, also query:

ObjectPurpose
DeviceSyncSummarySummary of synced data per device
DeviceSyncTransactionIndividual sync transactions
DeviceSyncTransactionLogSync logs with details
DeviceSyncTransactionRecordIndividual synced records

Example - Recent sync errors:

SELECT Id, Name, Status, ErrorDescription
FROM BatchJob
WHERE Status = 'Failed' OR Status = 'CompletedWithFailures'
ORDER BY StartTime DESC
LIMIT 10

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.