data-access-securityUse before writing or running SECURED Fusion SQL — the kernel's opt-in data-access rule: in developer mode only when the user asked for data access / security or said yes when the align ask offered it, and every end-user read — a final answer, a data model's dataset or LOV SQL, a secured run, SQL in
datamodel-authoringUse when analyzing, modifying, or generating an Oracle BI Publisher data model (.xdmz) — datasets and their SQL, output group structure, group placement, master-detail group links, parameters, lexicals (flexfield/KFF), value sets (LOVs), event triggers (PL/SQL), bursting, or validations; the XML-fun
fusion-sql-reviewUse before authoring or changing ANY Fusion SQL (a final answer, a data model's dataset SQL, a run_sql/explain_plan probe you write, SQL in prose or in a hand-off prompt), when the user asks for a review of SQL, whenever findSimilarQueries returned ambiguous:true, and whenever the required output in
rendering-and-runningUse to render an authored/uploaded template + data to a real PDF/HTML/RTF/XLSX/text file, to LOOK at any produced output (Read paths, PDF pages), or to download, browse, run, or upload a catalog object on the live Fusion pod. Covers renderTemplate, the visual verify loop, prepareDataModelTest / prep
report-authoringUse when creating or modifying a BI Publisher report layout — a report (.xdoz), an interactive XPT table, a print/invoice-grade RTF template, an XSL stylesheet for plain-text / CSV / markdown / feed output, or a subtemplate (.xsb). Covers createReportFile / addReportLayout, the surgical modifyReport
using-templatesUse when the user wants a report or dashboard and could start from a ready-made template instead of a from-scratch layout. Covers listTemplates / getTemplate / instantiateTemplate — picking a template, sizing it by its params, filling its slots from the grounded data-model output tree, and handing o