Release path
1.0.1Published Mar 4, 2026@pasar6987/sf-service-incident-management
ITIL-aligned incident, problem, and change management for tracking service disruptions and coordinating resolution.
Published package · Latest published 1.0.1 Mar 4, 2026 · 8 datasets / 0 measures in the latest review · Updated Mar 11, 2026
Publisher
@pasar6987Published Mar 4, 2026Structure snapshot
8 datasets0 measures · 94 dimensionsSemantic Graph
Relationship counts appear after the graph loads.
Loading graph
Package graph is loadingPackage relationships will appear when the summary is ready.
Reference 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
Upstream
Repository
Domain
Source
Owner
@pasar6987Organization
License
Visibility
Publisher
Latest published version
Tags
Schema preview
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-service-incident-management
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-service-incident-management")
prompt = rawctx.to_prompt(
"@pasar6987/sf-service-incident-management",
datasets=["ChangeRequest", "ChangeRequestRelatedIssue"],
max_tokens=2000,
)
print(model.datasets) # ["ChangeRequest", "ChangeRequestRelatedIssue", "ChangeRequestRelatedItem"]
print(model.measures) # [Measure(name="measure_a", ...)]
print(model.dimensions) # [Dimension(name="BusinessJustification", ...), Dimension(name="BusinessReason", ...), Dimension(name="Category", ...)]
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-service-incident-management
ITIL-aligned incident, problem, and change management for tracking service disruptions and coordinating resolution.
Overview
| Count | |
|---|---|
| Objects (Datasets) | 8 |
| Dimensions | 94 |
| Measures | 0 |
| Relationships | 0 |
Objects
- ChangeRequest — Represents a decision to implement a formal request for a change (RFC).
- ChangeRequestRelatedIssue — Represents a junction object that relates a ChangeRequest to an Incident or Problem due to a service failure.
- ChangeRequestRelatedItem — Represents a junction object that relates a ChangeRequest to an Asset.
- Incident — An Incident is any unplanned business interruption that has wide-sweeping impacts and requires an urgent fix. This object contains the details of the incident, documenting the history of the incident from registration to closure.
- IncidentRelatedItem — Represents a junction object that relates an Incident to an Asset or Product.
- Problem — Problems represent the root cause data of one or more incidents. This object contains all the details of a problem, documenting the history of the problem from detection to closure.
- ProblemIncident — Represents a junction object that relates a Problem to an Incident.
- ProblemRelatedItem — Represents a junction object that relates a Problem to an Asset.
Install
rawctx snapshot-download @pasar6987/sf-service-incident-management
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.
