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.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-config-migrationSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-provider-engagement-complianceSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
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
- Distinctive: line 30
When the user asks about configuring Application Settings, ask them which mode they prefer:
- Distinctive: line 35
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 …
≈ “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.
Files
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:
- Show me the documentation — I'll configure it myself in the Salesforce UI
- 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 Label | FieldName | DataType | Valid Values | Default |
| Default Browser | DefaultBrowser | PICKLIST | Safari, Chrome, InAppBrowser | Safari |
| Password Type | PasswordType | PICKLIST | Numeric, Alphanumeric | Numeric |
Integer Settings
| UI Label | FieldName | DataType | Description | Default |
| Hourly Dashboard Refresh Limit | HourlyDashboardRefreshLimit | INTEGER | Number of times dashboard can refresh per hour | 1 |
Text/URL Settings
| UI Label | FieldName | DataType | Description |
| App Download URL | AppDownloadUrl | TEXT | Full URL to download the app from the App Store |
Boolean Toggle Settings
| UI Label | FieldName | DataType | Description |
| Let users use View Online option | LetUsersUseViewOnline | BOOLEAN | Show "View Online" on home screen |
| Let users view reports | LetUsersViewReports | BOOLEAN | Allow report viewing in mobile |
| Enable Background Notifications | EnableBackgroundNotifications | BOOLEAN | Push notifications when app is backgrounded |
| Enable advanced search | EnableAdvancedSearch | BOOLEAN | Enable advanced search functionality |
| Use Advanced Search for lookups | UseAdvancedSearchForLookups | BOOLEAN | Use advanced search in lookup fields |
| Use Advanced Search for account lookups | UseAdvancedSearchForAccountLookups | BOOLEAN | Use advanced search specifically for account lookups |
| Let users override lookup search fields | LetUsersOverrideLookupSearchFields | BOOLEAN | Allow users to customize lookup search fields |
| Enable Dynamic Actions | EnableDynamicActions | BOOLEAN | Enable dynamic action framework |
| Let users publish platform events | LetUsersPublishPlatformEvents | BOOLEAN | Allow platform event publishing from mobile |
| Hide app upgrade notifications | HideAppUpgradeNotifications | BOOLEAN | Suppress app update notifications |
| Show persistent help text | ShowPersistentHelpText | BOOLEAN | Always show help text on fields |
| Enable Survey Branching Single Page | EnableSurveyBranchingSinglePage | BOOLEAN | Single-page survey branching mode |
| Enable Survey Confirmation | EnableSurveyConfirmation | BOOLEAN | Show 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 Label | FieldName | DataType | Description |
| Login Page Type | LoginPageType | PICKLIST | Type of login page to show |
| Default Landing Tab | DefaultLandingTab | TEXT | Which tab opens after login |
| Maximum Offline Days | MaxOfflineDays | INTEGER | How many days the app works offline |
| Enable Offline Mode | EnableOfflineMode | BOOLEAN | Allow 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
- Review all settings before go-live — Run
list_admin_settings({ category: "ApplicationSettings" })and verify each setting matches your implementation requirements. - Enable Advanced Search — Most implementations benefit from advanced search. Enable all three search toggles for the best user experience.
- Background Notifications — Enable for visit reminders and time-sensitive alerts. Requires push notification setup in the mobile app.
- Password Type — Use
Alphanumericfor higher security requirements.Numericis faster for field reps. - Dashboard Refresh Limit — Keep at 1-3 to avoid excessive API calls. Higher values may impact performance.
- Profile-Based Overrides — Use
ProfileBasedAppSettingsto 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-schemaskill - Mobile Cache Generation: See
lsc-mobile-validationskill - Home Page Configuration: See
lsc-home-page-configurationskill - Quick Actions: See
lsc-quick-actions-configurationskill
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
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.

