Report Builder

The Report Builder is Pinkapple’s controlled self-service reporting workspace.

Navigation: Reporting -> Setup -> Report Builder where enabled

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Report Builder	Reporting -> Setup -> Report Builder where enabled	Maintain safe sources, builder definitions, and controlled self-service report definitions.
Run Builder	Reporting -> Setup -> Report Builder, then Run Builder	Validate builder definitions before broader use.
Report Catalog	Reporting -> Setup -> Report Catalog	Promote stable report needs into governed catalog reports where appropriate.
Run Reports	Reporting -> Reports -> Run Reports	Run governed reports that have been published for users.

What The Builder Is For

Use the builder for governed ad-hoc reporting where the need is real but a dedicated curated catalog report is not yet necessary.

The builder is a middle ground between:

• fully governed catalog reports
• uncontrolled data extraction

It is not meant to replace core financial or statutory reporting.

Builder Tabs

The builder contains:

• Safe Sources
• Builder Definitions
• Run Builder

Safe Sources

Safe sources are the approved sources a builder definition is allowed to read from.

Supported source types in the UI are shown as approved source categories selected by administrators. Users should focus on whether the source is understandable, stable, and appropriate for the reporting question.

Each safe source records:

• source name
• display name
• source type
• description
• active status

Treat safe sources as a whitelist. Only expose sources that are:

• stable
• understandable
• acceptable from a security standpoint
• appropriate for reporting use

Builder Definitions

Builder definitions are reusable ad-hoc report specifications.

They typically store:

• builder code
• builder name
• source
• selected columns
• filter definitions
• grouping
• ordering
• row limit
• visibility scope
• active status

The builder definition form is best suited to administrators or strong power users because it controls columns, filters, grouping, ordering, and visibility.

Visibility

Builder definitions support scoped visibility such as:

• PRIVATE
• GLOBAL

Recommended usage:

• keep definitions PRIVATE while designing and validating
• promote to GLOBAL only after you trust the output and want broader reuse

Run Builder

Use Run Builder as the validation stage for builder definitions.

Confirm all of the following:

• the source returns the expected columns
• filters behave correctly
• grouping and ordering are usable
• the output stays within the row limit
• the report is worth keeping as a reusable definition

When To Use The Builder

Use the builder when:

• the business question is still evolving
• the output is primarily tabular
• the logic does not need a curated statement structure
• configuration is preferable to requesting a dedicated governed report immediately

Do not use the builder when:

• the report is statutory
• the report is board-critical
• the logic needs highly curated finance or system-owner control
• the output is a formal financial statement

Recommended Builder Workflow

1. Register a safe source.
2. Create the builder definition.
3. Validate it in Run Builder.
4. Refine filters, grouping, and output columns.
5. Decide whether it stays as a builder definition or graduates into the main report catalog with a governed data source.

Related Pages

• Administration & Setup
• System Settings
• Operations & Usage