This
The Snippet Framework User Interface Overview
The Snippet Framework is a backend execution engine. The user-facing experience for building and managing snippet-based Dynamic Applications is provided by a separate but closely related layer: the Dynamic Application Builder.
The Dynamic Application Builder
The Dynamic Application Builder is the product user interface within Skylar One for authoring, editing, testing, and debugging snippet-based Dynamic Applications. When you work with snippet arguments, Execution Environments, and collection step configuration in the Skylar One user interface, you are working through the Dynamic Application Builder.
The Dynamic Application Builder is an add-on layer to the standard Dynamic Application configuration page. It does not replace the existing user interface, and instead it extends snippet-specific capabilities.
For step-by-step instructions on using the Dynamic Application Builder, see the Dynamic Application Development manual.
The Low-Code Explorer (LCE) Service
The backend engine that powers the Dynamic Application Builder experience is the Low-Code Explorer service (LCE) service. The LCE service is a daemonized HTTP service that runs on Skylar One databases and Collector appliances. The tooling also runs on Administration Portal appliances in distributed deployments. Key actions in the user interface include library management, wheel downloads, execution environment alignment, snippet linting, and collection run. All of these are captured in organization-level audit logs.
The LCE Service:
- Manages Execution Environments and ScienceLogic Library installations
- Executes collection runs initiated from the Dynamic Application Builder
- Lints and validates snippet argument YAML
- Provides the endpoints for library management, test runs, and wheel downloads
- Aligns downloaded third-party library wheels to the current execution environment, replacing existing libraries when applicable
- Supports custom pip configuration for the Wheel Downloader, including custom repositories and trusted hosts, while preserving default behavior when not configured
The LCE service runs automatically as part of a Skylar One installation that includes the "Low-code Tools" PowerPack. Administrators do not typically interact with the LCE service directly as it is the backend engine behind the Dynamic Application Builder.
The third-party library download workflow can automatically align downloaded wheels to the current execution environment, replacing existing libraries when applicable. You can configure pip for the Wheel Downloader from the user interface to specify custom repositories and trusted hosts. Default pip behavior is preserved when no custom configuration is set.
In engineering documentation and release notes, the Dynamic Application Builder experience and the LCE backend service may be referenced together as the Snippet Framework User Interface. This manual and the product user interface use Dynamic Application Builder as the customer-facing name.
When you create a new collection object in the Dynamic Application Builder, the editor can automatically insert a default snippet argument structure sourced from the LCE service backend. This ensures the inserted default reflects the current execution environment and available steps. If the LCE endpoint is unavailable at the time of insertion, the editor falls back to a locally stored default instead.
Governance and Access Control
The LCE service enforces authentication and permission checks on all endpoints. Unauthenticated requests return HTTP 401; requests from users without sufficient permissions return HTTP 403. This applies to snippet, library, environment, and execution actions.
Key actions are captured in organization-level audit logs, including library management, wheel downloads, execution environment alignment, snippet linting, and collection runs.
Memory usage for the LCE service is managed through configurable MemoryHigh and MemoryMax values.