What problem does it solve?
It solves the problem of creating a working PJE “download” workflow for a specific tribunal when the REST/JSF endpoints, headers, and session cookies differ subtly across deployments.
Core Features & Use Cases
- Guides HAR capture for listing and downloading: instructs how to generate two HAR files (process listing and document download) using DevTools while logged in with a certificate.
- Derives tribunal-specific configuration from HAR: identifies BASE_URL, essential cookies, and X-pje-* headers, then maps REST and JSF endpoints needed for the automation.
- Produces parametrized scripts/config: consolidates findings into a
config_tribunal.json and adapts templates into scripts that can list processes, obtain access keys, and download PDFs.
Use case example: You have a HAR from one tribunal and need to adapt the download automation to another tribunal (different domain/cookies/headers) so you can list pending cases and download digital records as PDFs.
Quick Start
Provide the HAR files captured while logged into your tribunal (listing and one download) and ask the assistant to generate a tribunal-specific config_tribunal.json plus the adapted listing and PDF download scripts.
