S+ Notification Template Extraction from Live System

Automation Name

S+ Notification Template — Live System Extraction to Excel

This automation navigates a client's live S+ (Strategy Management) notifications page, extracts every component and event from the system UI, and generates a bilingual (AR/EN) Excel template ready for the team to enter notification content into the system. Instead of working from a BRD document, this pulls directly from what the system actually has — ensuring zero drift between documentation and reality.

How It Works

The Prompt

Use this prompt in a Claude Code session with browser access (Claude in Chrome / Cowork). Replace {{URL}} with the client's actual notifications page URL, and attach the S+ Notification Master Template (.xlsx) so Claude matches its exact format.

@{{path-to-template}}/SPlus_Notifications_Template.xlsx

Go to the following URL and extract ALL notification events for every component
listed in the left sidebar:

{{URL}}

Follow these steps exactly:

1. Navigate to the URL and identify all components listed in the left sidebar
   (e.g., Objective L1, Objective L2, KPI L1, Initiative, Track, Project,
   Key Result, etc.).

2. For each component in the sidebar, click on it, then:
   a. Open the event dropdown (top-right "Select Event" combobox).
   b. Scroll through the entire dropdown to capture every single event option
      — do NOT assume events are the same across components.
   c. Record the exact event name as it appears in the dropdown.
   d. Check the existing template tab(s) below the dropdown — record the
      template name, channel, and any receivers already configured.
   e. Read the template body (the rich text editor content) and extract all
      template variables/properties used (anything in double curly braces
      like {{variableName}}).

3. Do NOT skip any component. Even if a component shows "No available options,"
   document that explicitly.

4. Use read_page with the listbox ref_id to get the full list of dropdown
   options when they are too long to fit on screen — visual screenshots alone
   may miss items.

5. After extracting all events from every component, generate an Excel (.xlsx)
   file that matches the EXACT format of the attached S+ Notification Master
   Template:

   EXCEL FORMAT REQUIREMENTS:
   - Use the same column structure as the attached template:
     Column A: Component (exact component name from the sidebar)
     Column B: Event (exact event name from the dropdown)
     Column C: Subject (bilingual Arabic / English notification subject)
     Column D: Email Body English (full English email template with variables)
     Column E: Email Body Arabic (full Arabic email template with variables)
     Column F: Notification Centre Body English (short in-app notification)
     Column G: Notification Centre Body Arabic (short in-app notification)

   - Create separate sheets matching the attached template structure
     (e.g., Objectives, KPIs, Initiatives, Key Results, Variables Reference)

   - Populate all bilingual content (Subject, Email Body EN/AR,
     Notification Centre EN/AR) following the same patterns as the attached
     template — use the same greeting format, variable placement, and
     sign-off style

   - Include all template variables in double curly braces:
     {{receiver}}, {{Name_en}}, {{Name_ar}}, {{userCausedEvent}}, {{webUrl}},
     {{Frequency}}, {{owner_126}}, {{finishDate_131}}, etc.

   - Include a Variables Reference sheet listing every template variable
     with English description, Arabic description, and which components use it

   - Apply professional formatting: headers with dark fill + white text,
     borders on all cells, text wrapping enabled, appropriate column widths

   - If an event exists in the system dropdown but has NO template configured
     yet (empty body, no receivers), still include it in the Excel with full
     bilingual content so the team can enter it

6. Be thorough. Check every component, every event, every template.
   Do not assume components share the same events — verify each one
   individually.

7. Save the final Excel file to the outputs folder.

URL Pattern Reference

https://{client-subdomain}.masterteam.sa/template/{template-id}/notifications/{component-id}?eventId={event-id}&activeIndex={index}

Required Files

Downloadable Templates

What Gets Extracted

The automation extracts directly from the live system UI — not from a BRD or any document. It captures:

Output Format — Excel Structure

The generated Excel matches the standard S+ notification template format exactly:

Sheet Structure

Column Structure (All Sheets)

Typical Events Found Per Component

These are the events commonly found in S+ notification configurations. The actual events vary by client — that's why the automation extracts from the live system rather than assuming.

Objective Events

• When Objective created
• When Objective updated

KPI / Performance Indicator Events

• When Performance Indicator Created
• When Performance Indicator updated
• When Performance Indicator Measures updated
• When Performance Indicator Measure opened
• When Performance Indicator Measure Value updated
• Daily Reminder before Performance Indicator locked
• One day before Performance Indicator locked
• When Performance Indicator locked
• When Performance Indicator unlocked
• When Corrective Actions Plan Created
• When Corrective Actions Plan updated

Initiative Events

• When Initiative added
• When Initiative updated
• When Action item created
• When Action item updated
• When Action item deleted
• When Action item progress updated

Track Events

• When Track added
• When Track updated
• When Action item created / updated / deleted / progress updated

How to Use

1. Open Claude Code (desktop app, CLI, or web) with browser access enabled
2. Have the client's S+ notifications page URL ready
3. Attach the S+ Notification Master Template (.xlsx) — this is the format reference
4. Paste the prompt above — replace {{URL}} with the actual URL and {{path-to-template}} with the file path
5. Claude navigates the system, clicks through every component and event
6. Claude generates an Excel file matching the template format with full bilingual content
7. Download the Excel from the outputs folder
8. Hand it to the configuration team — they can enter each row directly into the system

Key Differences from BRD-Based Approach

Best Practices

• Always use the attached template — this ensures the output Excel matches the exact format the team expects
• Check both tabs if the client has multiple strategy templates (e.g., "DGA Strategy" and "Organization Health") — each may have different components
• Verify dropdown completeness — the prompt instructs Claude to scroll through the full dropdown and use read_page for accuracy
• Events with no template are still captured — the Excel includes full bilingual content so the team can enter them fresh
• Run per template — if a client has multiple strategy templates, run the extraction once per template tab

Quality Checklist

Conclusion

This automation eliminates the guesswork of building notification templates from BRD documents. By extracting directly from the client's live S+ system, it captures every component, every event — including ones that may not be documented in any BRD. The output is a ready-to-use Excel file in the exact format the configuration team expects, with full bilingual content for every notification event.