Release path
1.0.1Published Mar 4, 2026Package control recordPublished package
@pasar6987/sf-automotive-telemetry
Connected vehicle telemetry definitions, action triggers, versioning, and automated response workflows.
OSISchema 0.1.1Domain crmSource developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference
Published package · Latest published 1.0.1 Mar 4, 2026 · 6 datasets / 4 measures in the latest review · Updated Mar 11, 2026
Publisher
@pasar6987Published Mar 4, 2026Structure snapshot
6 datasets4 measures · 29 dimensionsReference context
Secondary package facts stay compact
- Updated
- Mar 11, 2026
- Visibility
- Public hub listing
- License
- MIT
- Created
- Mar 4, 2026
Reference facts
Secondary package facts after the usage path is clear
Licensing, categorization, ownership, and linked metadata stay below the runnable path so the page reads in the right order.
Format
OSI
Upstream
developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference
Repository
Not linked
Domain
Source
Owner
@pasar6987Organization
Independent
License
MIT
Visibility
Public hub listing
Publisher
@pasar6987Published Mar 4, 2026
Latest published version
1.0.1Published Mar 4, 2026
Tags
Schema preview
Schema 0.1.1
SDK handoff
Use this package in code and AI
After structure review, move straight into typed reads with load() or compact LLM context with to_prompt().
Python SDK
Python example for @pasar6987/sf-automotive-telemetry
This example uses the current package ref and, when preview data is available, fills in real dataset names from the published summary.
import rawctx
model = rawctx.load("@pasar6987/sf-automotive-telemetry")
prompt = rawctx.to_prompt(
"@pasar6987/sf-automotive-telemetry",
datasets=["TelemetryActionDefStep", "TelemetryActionDefinition"],
max_tokens=2000,
)
print(model.datasets) # ["TelemetryActionDefStep", "TelemetryActionDefinition", "TelemetryActionRelatedProcess"]
print(model.measures) # [Measure(name="TelemetryActionDefStep.SequenceNumber", ...), Measure(name="TelemetryActnDefStepAttr.MaximumValue", ...), Measure(name="TelemetryActnDefStepAttr.MinimumValue", ...)]
print(model.dimensions) # [Dimension(name="GroupName", ...), Dimension(name="OperationType", ...), Dimension(name="RemoteEndPointUrl", ...)]
print(model.relationships) # [Relationship(name='...', ...)]
print(prompt)README
Package narrative and examples
Use documentation after the package clears provenance, ownership, and runnable-path checks.
@pasar6987/sf-automotive-telemetry
Connected vehicle telemetry definitions, action triggers, versioning, and automated response workflows.
Overview
| Count | |
|---|---|
| Objects (Datasets) | 6 |
| Dimensions | 29 |
| Measures | 4 |
| Relationships | 0 |
Objects
- TelemetryActionDefStep — Represents a step in the action for a telemetry signal definition.
- TelemetryActionDefinition — Represents the action taken on a telemetry signal sent from a connected asset or vehicle, such as getting the current status of a vehicle or its component, or sending a request to perform a remote action on the vehicle or its component.
- TelemetryActionRelatedProcess — Represents the relationship between a telemetry action and a process triggered by the action such as a service catalog item definition or a product.
- TelemetryActnDefStepAttr — Represents the attributes of a telemetry action definition step.
- TelemetryDefinition — Represents the definition of the structure of a telemetry signal sent from a connected asset or vehicle.
- TelemetryDefinitionVersion — Represents a version of the structure of a telemetry signal sent from a connected asset or vehicle.
Install
rawctx snapshot-download @pasar6987/sf-automotive-telemetry
Structure review
Inspect package structure after the usage path is clear
Use the structural review when you need the package footprint, field counts, and model paths before a deeper explorer pass.
models/sf-automotive-telemetry.osi.yamlAI context included
6 datasets4 measures29 dimensions0 relationships
Topology
Semantic graph
Use the graph last, once provenance, documentation, and the runnable path are already clear.
Semantic Graph
Topology counts appear after the graph loads.
Loading graph
Semantic topology is still loadingCounts and graph nodes appear after the latest published summary has been fetched.