Skip to main content
Use serval in twins and put this configuration under seed_config.serval. Serval IT service management and identity operations workspace with users, teams, groups, tickets and messages, app resources and access controls, workflows and approval runs, forms, entities, schedules, SLAs, and webhooks.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.serval. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Seeding behavior

You can provide flat resource arrays or nest statuses, priorities, members, and tickets inside a team. Resource alias values can be referenced as {"$ref":"alias.id"}.

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

users[]

teams[]

groups[]

team_users[]

team_groups[]

statuses[]

priorities[]

labels[]

categories[]

tickets[]

tickets[].labelIds[]

ticket_messages[]

custom_services[]

app_instances[]

app_resources[]

app_resource_roles[]

access_profiles[]

access_policies[]

access_requests[]

workflows[]

workflow_runs[]

guidances[]

forms[]

folders[]

tags[]

entity_types[]

entity_types[].fields[]

entities[]

entities[].fieldValues[]

schedules[]

schedules[].weeklyHours.monday[]

schedules[].weeklyHours.tuesday[]

schedules[].weeklyHours.wednesday[]

schedules[].weeklyHours.thursday[]

schedules[].weeklyHours.friday[]

sla_definitions[]

webhooks[]

See Scenario seeding for saving, provisioning, and resetting fixtures.