A report is visible in one schema but not in another

Created by Joan Nuguid, Modified on Fri, 12 Sep at 4:18 PM by Joan Nuguid

If a report isn't showing up in one JAVLN schema but is in another, here's a simplified checklist to troubleshoot the issue:

1. Report Manager (Admin > Reports > Report Manager):

Roles: Is the report assigned to the correct user roles?
Active Status: Is the report marked as "Active"?
Parameters & Output: Are report parameters set correctly, and is the output type/format valid (e.g., PDF, XLSX)?
Report File: Does the report file exist in this schema, or does it need to be added via a JIRA request?

2. System Lists (Admin > System Lists):

Matching Names: For reports like "Bulk Process Client Statements," does the entry in the relevant System List (e.g., FusionClientStatement) exactly match the report's name in Report Manager?
Other Lists: Check related System Lists (e.g., FusionPaymentFile, PaymentMethods, BatchPaymentSubType) for activity and correct configurations if relevant to the report.

3. Module Configurations & Workflows (Admin > Access > Modules):

Module Roles: If it's an inline report, are the necessary roles assigned to the module it's linked to?
Inline Link: Is the report correctly linked as an inline report within its module?
Workflow: Is the module containing the report included in the correct workflow?
DMS Settings: For documents sent to a DMS, are "Save as Document" and "Send to DMS?" enabled in Report Manager's Usage tab?

4. Feature Flags:

Enabled Flags: Some reports and features require specific feature flags to be TRUE in the schema. Check if any relevant flags (e.g., TEMP_SYNC_STANDARD_REPORTS_ALLOWED, CLIENT_STATEMENT_IMPROVEMENT_ENABLED) are active.

5. Database Views & Technical:

Missing Views/Tables: Confirm that all required database views (e.g., REPORT_POLICY_AGEN_COMMS) and tables (e.g., REPORT_JOB_PARAMETERS) for the report are present in the schema.
Schema Copy: Be aware that certain settings might reset when a schema is copied, requiring re-initialization.

In essence, first check Report Manager roles and activity, then ensure associated System List entries are correct, verify module links and workflow inclusion, check relevant feature flags, and finally, confirm underlying database components are in place for that specific schema.