custom app

[GRH]

• Hi..As a part of servicenow training i want to build custom app .can you please give me a flowchart(blueprint) for the below custom app .I’m trying to build a custom application in ServiceNow for the Technical Governance Board (TGB) review process. Below is the full end-to-end requirement with comments explaining each step in detail. Can you please guide me on the best way to approach this?
  
  🔄 Business Use Case Summary:
  When a project is initiated, the architect needs to submit a SAD (Solution Architecture Design) document. This must go through multiple governance stages before the project can be approved. The governance process is handled by:
  
  Pre-ARB review
  
  ARB approval
  
  CAB group approvals (Security, Risk, Legal, etc.)
  
  📋 Step-by-Step Requirements with Comments:
  1️⃣ Governance Ticket Submission
  The Architect creates a Governance Ticket using a custom form (custom table like x_tgb_governance_ticket).
  
  They upload the SAD document as an attachment.
  
  Comment: This is the entry point of the process.
  
  2️⃣ Pre-ARB Review
  Ticket first goes to the Pre-ARB reviewer for initial screening.
  
  Comment: If Pre-ARB approves, then it moves forward to formal reviews.
  
  3️⃣ ARB Approval (Strict Rule)
  After Pre-ARB, ticket goes to ARB group.
  
  Comment: If any ARB member rejects, the ticket is immediately canceled.
  
  ARB can see all comments from CAB and add their own.
  
  4️⃣ CAB Group Approvals (6 Groups)
  After ARB approval, the ticket routes to 6 CAB groups (like Security, Legal, Risk, etc.).
  
  Comment: All 6 CAB groups must approve for the ticket to succeed.
  
  5️⃣ CAB Rejection Logic
  Each CAB group can reject up to 2 times.
  
  If a CAB group rejects a 3rd time, the ticket is permanently canceled.
  
  If rejected once or twice, the Architect can resubmit a new version of the SAD document.
  
  Comment: Only the rejected group’s approval should be re-triggered after resubmission, not all 6.
  
  6️⃣ Document Versioning
  Architects can upload new versions of the SAD document.
  
  Old versions cannot be deleted (disable delete on attachments).
  
  Comment: Useful for tracking document history and changes over time.
  
  7️⃣ Comment Visibility Rules
  CAB groups: Can only see their own comments.
  
  ARB group: Can see all comments from all 6 CAB groups.
  
  Architects: Cannot see any comments from CAB or ARB.
  
  Comment: This needs dynamic control, probably using Display Business Rule or script logic.
  
  8️⃣ Role-Based Access:
  Architects: Can only see tickets they submitted.
  
  ARB and CAB: Can see all tickets for review.
  
  Comment: Use ACLs on the ticket table (read, write, create, delete) and comment field if needed.

[GlideFather]

Hi @GRH 

you mentioned training. For that you are indeed in the right place, however learning starts with you, draft something try whatever you can, when stuck ask for help.

but you cannot expect someone be doing it for you ;))