Appearance
Report Builder
The Report Builder is PinkApple’s controlled self-service reporting workspace.
Navigation: Administration -> Reporting -> Report Builder
What The Builder Is For
Use the builder for governed ad-hoc reporting where the need is real but a dedicated curated procedure is not yet necessary.
The builder is a middle ground between:
- fully governed catalog reports
- uncontrolled direct database querying
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:
- VIEW
- TABLE
- PROCEDURE
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 technical admins or strong power users because parts of the definition are still JSON-oriented.
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 writing a dedicated stored procedure immediately
Do not use the builder when:
- the report is statutory
- the report is board-critical
- the logic needs highly curated backend control
- the output is a formal financial statement
Recommended Builder Workflow
- Register a safe source.
- Create the builder definition.
- Validate it in Run Builder.
- Refine filters, grouping, and output columns.
- Decide whether it stays as a builder definition or graduates into the main report catalog with a dedicated dataset procedure.