Reporter Console: operational guides and field references

Reporter Console documentation now gives operators clearer step-by-step guidance, field references, and language-aligned pages for templates, reports, and data sources.

May 26, 2026 Documentation update No migration required

Affects

---

Operators, administrators, implementation teams, and integrators using Reporter through Lerian Console to create Templates, generate Reports, download outputs, or manage Data Sources.

This update applies to the documentation portal. It does not change Reporter behavior, API behavior, Data Source configuration, Template execution, generated Reports, or existing integrations.

What changed

---

Operational guides for Reporter Console tasks

Reporter Console action pages now explain the objective of each task, when to use it, what to check before starting, the step-by-step flow, expected results, common errors, and next steps.

Field references aligned with the Console UI

The pages now include focused field references for Template upload and update, Template Builder blocks, Report generation filters, Report status handling, and Data Source connection forms.

Field labels follow the Console UI. Portuguese pages use localized Console labels where the product is localized. Spanish pages keep English UI labels where the product is not localized.

Clearer Data Source journey

The documentation now clarifies that many Reporter workflows can start from Templates because internal product Data Sources may already be configured.

Use Data Sources when you need an external database connection, need to test an existing connection, or need to troubleshoot a Data Source that is unavailable or unhealthy.

API reference links as portal resources

Where a programmatic equivalent exists, the pages now point to the related Reporter API reference page in the portal.

Before

Reporter Console pages were shorter and less consistent across operational tasks. Data Source guidance could make the setup path look mandatory even when an internal source was already available.

After

The pages are structured as operator guides, field references stay readable without wide tables, and Data Sources are explained as a control area for external connections and connection testing.

Impact

---

This is a documentation-only update.

No migration is required. No product behavior changed. Existing Reporter workflows, APIs, Templates, Reports, and Data Sources keep working exactly as they do today.

Use the updated documentation when onboarding Reporter operators, reviewing Console workflows, or aligning operations across languages.

What you need to do

---

1. Review the updated Reporter Console documentation before onboarding operators or changing operating procedures.

2. Use the setup path and concepts map to decide whether your workflow starts from Templates or requires Data Source work first.

3. Use the field references when creating Templates, generating Reports, or configuring Data Sources.

4. Use the linked API reference pages when implementing or reviewing programmatic Reporter workflows.

Deadline

None.

Why

Reporter operators need to know which parts of the workflow happen in Lerian Console, which parts depend on existing Data Sources, and which fields affect generated Reports. The updated documentation reduces onboarding ambiguity, keeps UI labels consistent, and makes the Console workflow easier to follow for operational and integration teams.

Resources

---

• Reporter Module
• Reporter setup path
• Reporter concepts map
• Managing Templates
• Template Builder
• Generating a Report
• Managing Data Sources
• Reporter API reference quick start