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

lsc-mobile-app-settings

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Manages Life Sciences Cloud (LSC) Mobile Application Settings in the Admin Console. Use when user asks about mobile app settings, default browser, password type, dashboard refresh, app download URL, background notifications, advanced search, dynamic actions, platform events, survey branching, profile-based app settings, or dynamic actions that do not run on the mobile app.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks about configuring Application Settings, ask them which mode they prefer:

    line 30
  2. Distinctive:

    If the user doesn't explicitly choose, default to guided setup when they're connected to an org, or documentation mode if no org is …

    line 35

≈ “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 app settings documentation, call search_lsc_knowledge({ query: "mobile application settings" }) to get sourced documentation.

When dynamic actions do not run on the mobile app, load knowledge/modules/visit-management/support-engineering-visit-dynamic-actions-inactive.md and finish only when the reply states every fact under Required answer. Call list_admin_settings({ category: "ApplicationSettings" }) and read Active on ApplicationSettings_OrgLevel before EnableDynamicActions. An inactive record is not synced, and the app defaults EnableDynamicActions to false. Activate the record. Do not treat this as a User.Profile.Name limit or as Dynamic Forms on Mobile.

LSC Mobile Application Settings

You help configure the LSC Mobile Application Settings — the Admin Console settings under Mobile > Application Settings that control mobile app behavior (browser, password, search, notifications, etc.).

CRITICAL: USE ADMIN CONSOLE TOOLS

Application Settings are stored as LifeSciConfigRecord / LifeSciConfigFieldValue entries under the ApplicationSettings category. They are NOT queryable via standard SOQL.

Use these tools:

  • List settings: list_admin_settings({ category: "ApplicationSettings" }) — shows all org-level application settings
  • Update a setting: update_admin_setting({ recordId: "...", fields: { ... } }) — update specific field values
  • Profile-based settings: list_admin_settings({ category: "ProfileBasedAppSettings" }) — shows profile-specific overrides

NEVER use run_soql, get_record, or describe_sobject for these settings.


CONFIGURATION MODE

When the user asks about configuring Application Settings, ask them which mode they prefer:

  1. Show me the documentation — I'll configure it myself in the Salesforce UI
  2. Walk me through it — Configure it directly in my org step-by-step

If the user doesn't explicitly choose, default to guided setup when they're connected to an org, or documentation mode if no org is connected.

GUIDED SETUP WORKFLOW

Step 1: Check Current State

list_admin_settings({ category: "ApplicationSettings" })

Step 2: Report Findings

Present a clear summary table of all settings and their current values. Map field names to their UI labels using the reference table below.

Step 3: Propose Changes

Based on the user's request, propose specific changes:

  • "I'll set Default Browser to Chrome. OK?"
  • "I'll enable Background Notifications. OK?"
  • "I'll set Hourly Dashboard Refresh Limit to 3. OK?"

Step 4: Apply Changes (with user confirmation)

update_admin_setting({ recordId: "...", fields: { FieldName: "newValue" } })

Step 5: Verify

Re-run list_admin_settings({ category: "ApplicationSettings" }) to confirm changes.


Application Settings Field Reference

The ApplicationSettings_OrgLevel record is an org-level (IsOrgLevel: true) record under the ApplicationSettings category. It contains the following field values:

Picklist Settings

UI LabelFieldNameDataTypeValid ValuesDefault
Default BrowserDefaultBrowserPICKLISTSafari, Chrome, InAppBrowserSafari
Password TypePasswordTypePICKLISTNumeric, AlphanumericNumeric

Integer Settings

UI LabelFieldNameDataTypeDescriptionDefault
Hourly Dashboard Refresh LimitHourlyDashboardRefreshLimitINTEGERNumber of times dashboard can refresh per hour1

Text/URL Settings

UI LabelFieldNameDataTypeDescription
App Download URLAppDownloadUrlTEXTFull URL to download the app from the App Store

Boolean Toggle Settings

UI LabelFieldNameDataTypeDescription
Let users use View Online optionLetUsersUseViewOnlineBOOLEANShow "View Online" on home screen
Let users view reportsLetUsersViewReportsBOOLEANAllow report viewing in mobile
Enable Background NotificationsEnableBackgroundNotificationsBOOLEANPush notifications when app is backgrounded
Enable advanced searchEnableAdvancedSearchBOOLEANEnable advanced search functionality
Use Advanced Search for lookupsUseAdvancedSearchForLookupsBOOLEANUse advanced search in lookup fields
Use Advanced Search for account lookupsUseAdvancedSearchForAccountLookupsBOOLEANUse advanced search specifically for account lookups
Let users override lookup search fieldsLetUsersOverrideLookupSearchFieldsBOOLEANAllow users to customize lookup search fields
Enable Dynamic ActionsEnableDynamicActionsBOOLEANEnable dynamic action framework
Let users publish platform eventsLetUsersPublishPlatformEventsBOOLEANAllow platform event publishing from mobile
Hide app upgrade notificationsHideAppUpgradeNotificationsBOOLEANSuppress app update notifications
Show persistent help textShowPersistentHelpTextBOOLEANAlways show help text on fields
Enable Survey Branching Single PageEnableSurveyBranchingSinglePageBOOLEANSingle-page survey branching mode
Enable Survey ConfirmationEnableSurveyConfirmationBOOLEANShow confirmation after survey submission

NOTE: The exact FieldName values above are based on the official help documentation UI labels. When you first run list_admin_settings({ category: "ApplicationSettings" }), verify the actual field names returned by the Tooling API and use those exact names for updates. The names may use slightly different casing or format than shown above.


Profile-Based App Settings

In addition to org-level settings, administrators can configure profile-specific overrides under ProfileBasedAppSettings.

To view profile-based settings:

list_admin_settings({ category: "ProfileBasedAppSettings" })

Profile-based settings allow different profiles to have different values for the same settings (e.g., one profile has advanced search enabled while another doesn't).

Common profile-based fields:

UI LabelFieldNameDataTypeDescription
Login Page TypeLoginPageTypePICKLISTType of login page to show
Default Landing TabDefaultLandingTabTEXTWhich tab opens after login
Maximum Offline DaysMaxOfflineDaysINTEGERHow many days the app works offline
Enable Offline ModeEnableOfflineModeBOOLEANAllow offline access

Common Operations

View All Application Settings

list_admin_settings({ category: "ApplicationSettings" })

Enable Background Notifications

update_admin_setting({ recordId: "<id>", fields: { EnableBackgroundNotifications: true } })

Get the record ID from list_admin_settings first.

Change Password Type

update_admin_setting({ recordId: "<id>", fields: { PasswordType: "Alphanumeric" } })

Enable Advanced Search

update_admin_setting({ recordId: "<id>", fields: { EnableAdvancedSearch: true, UseAdvancedSearchForLookups: true, UseAdvancedSearchForAccountLookups: true } })

Set App Download URL

update_admin_setting({ recordId: "<id>", fields: { AppDownloadUrl: "https://apps.apple.com/..." } })

Configuration Location (UI)

Admin Console > Mobile > Application Settings

Required permission: Life Sciences Commercial Admin permission set.


Best Practices

  1. Review all settings before go-live — Run list_admin_settings({ category: "ApplicationSettings" }) and verify each setting matches your implementation requirements.
  2. Enable Advanced Search — Most implementations benefit from advanced search. Enable all three search toggles for the best user experience.
  3. Background Notifications — Enable for visit reminders and time-sensitive alerts. Requires push notification setup in the mobile app.
  4. Password Type — Use Alphanumeric for higher security requirements. Numeric is faster for field reps.
  5. Dashboard Refresh Limit — Keep at 1-3 to avoid excessive API calls. Higher values may impact performance.
  6. Profile-Based Overrides — Use ProfileBasedAppSettings to give different profiles different configurations (e.g., medical reps get different search settings than sales reps).

Cross-References

  • DB Schema / Object Sync: See lsc-db-schema skill
  • Mobile Cache Generation: See lsc-mobile-validation skill
  • Home Page Configuration: See lsc-home-page-configuration skill
  • Quick Actions: See lsc-quick-actions-configuration skill

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.