About this guide
This guide is for people who define and manage orchestrated journeys, and for service owners and operational teams who review their performance in Oracle Government Orchestration Service (GovOS). It covers journey definition and publication where Journey Builder is enabled, inspection of a published journey, and the leadership and operations dashboards.
The application screens show Government Orchestration Service in the masthead. This guide uses the visible control names so that you can follow the procedures.
Find your task
| To do this | Read this topic |
|---|---|
| Understand access and choose an application | Get started |
| Prepare, validate, and publish a journey definition | Define and publish a journey |
| Verify the version and structure of a published journey | Inspect a published journey |
| Review demand, progress, outcomes, or GenAI activity | Using dashboards |
| Interpret reporting gaps or get help | Check report quality and resolve problems |
Scope and availability
Journey Builder is included in Release 1.0 for authorized users. It accepts a YAML journey definition, validates it with the running platform, and can publish the exact validated draft. Obtain the application address, access, and authorization for your deployment before following its publication procedure.
The Government Leadership Dashboard is a staff-application leadership view that requires the GOVERNMENT_ADMIN role. Journey Events is the administration-application operations and service oversight view. Reporting availability depends on the configured environment and your access. These dashboards show aggregate reporting, not individual-case decisions.
This guide does not cover infrastructure deployment, identity-provider configuration, database administration, backups, or recovery. Use your organization’s approved runbooks for those tasks.
About the screenshots and data
The screenshots use sample reporting data, journey definitions, catalogue entries, and validation responses to illustrate the controls and measures. Their counts and identifiers are not live service measurements. Follow the publication procedure in your own authorized environment to validate and publish a journey.
Each figure has accompanying text description. Bold text identifies labels and controls visible in the application. A journey definition describes an orchestrated process; a run is one execution of it. A terminal outcome can include completion, withdrawal, cancellation, or failure.