Anastasia Abrahim
  • Home
  • About Me
    • Resume
  • My Works
    • Agency File Management
    • Precision Plan Comparison
    • Rigel
    • Sony Sandbox
    • Motherboard
    • Client Config
    • Healix Global - External Website
    • Magna Global - External Website
    • Sample Site Maps Flows
    • Sample Workflow Diagrams
    • JIRA-Issued Story Artifacts
    • Product Documentation
    • Sample Deliverables from Past Roles

JIRA-Issued Story Artifacts

AFM-28 – Regular User Access to Notifications Tab

AFM-28 – Let Regular Users See Notifications

What’s this all about?

We want to allow regular users (not admins) to access the Notifications tab inside the Agency File Management tool.

That way, they can use the system to get alerts or updates — but without seeing or editing other admin-level features.

How does it work?

  • There’s a permission group in Bridge called Agency File Management_User.
  • When a user is added to this group, they are given access to the Notifications tab only.
  • This limits what they can see and interact with, keeping it safe and simple.

What do we need to test?

  • Confirm a user added to Agency File Management_User can see the Notifications tab.
  • Make sure they cannot access any other AFM tabs or settings.
  • Ensure the user can still fully use the Notifications tab as intended.
Reminder: This doesn’t give users full system access. It only allows them to use the Notifications tab so they can do their part without risk to system integrity.
Picture
AFM-337 – Full Network Report Format & Delivery

AFM-337 – Make the Report Include All Networks, Organize It Better

Include All Networks

Right now, the report only shows the biggest 6 networks. But we want it to include all 10 A+E networks, like:

  • A&E
  • CI
  • FYI
  • HEE
  • HIS
  • LIFE
  • LIFEMOV
  • LRW
  • MH
  • VICE

Excel Format Improvements

Instead of showing everything on one giant sheet, break it out into tabs by network inside the Excel file.

XML and JSON Structure

If we’re also sending this as XML or JSON, let’s group that data by network too — just like the Excel tabs — so it’s easier to follow.

Batched File Delivery

  • Put all the deals for one agency into a single file.
  • Inside that file, there can be multiple advertisers and deals.
  • Don't zip the files. Just deliver them as regular files.

Example Format

Agency Advertiser Deal # Etc.
Agency Advertiser #1 Deal #1 ...
Agency Advertiser #1 Deal #2 ...
Agency Advertiser #2 Deal #1 ...
Agency Advertiser #2 Deal #1 ...
Picture
BRID-3752 – Add New Fields to File Setup

BRID-3752 – Add More Fields to File Setup Page

What’s This About?

We’re improving the “Available Fields” list on the File Setup page. Think of it like giving users extra options they can pick from when creating reports.

These new fields come from WideOrbit’s database, and we’re mapping them so they appear in the UI — ready to use.

What Fields Are Being Added?

New Field Name WideOrbit Table WideOrbit Field Comment
Account Executive WO_ORDERS PRIMARY_ACCOUNT_EXEC_ID On Report will need Display Name not ID
Sales Office WO_ORDERS SALES_OFFICE_ID On Report will need Display Name not ID
Trackage Title WOCNS_TRACKAGE_TITLES TRACKAGE_TITLE_NAME
Alt Order # WO_ORDERS ALT_ORDER_NUMBER
Display Times WOA_OLU(channel#), WOCNS_OLU_EXTRACTS(channel#) DISPLAYED_TIMES
Intended AirDate WOA_OLU(channel#), WOCNS_OLU_EXTRACTS(channel#) INTENDED_AIR_DATE
Unit Count WO_ORDERS TOTAL_ORDER_UNITS
Rate Card Name WOCNS_RATE_CARDS NAME Latest Ratecard Version Name

Why It Matters

  • Users will have more data to work with when building reports.
  • It helps support internal teams by letting them see extra fields like Sales Office, AirDate, or Rate Card Name.
  • Some values (like Account Exec and Sales Office) need to show names, not IDs, for clarity.
Picture
BRID-3753 – Add Summary Tab to Excel Report

BRID-3753 – Add Summary Tab to DR Excel Spreadsheet

What's this all about?

When someone creates an Excel file using the Create Rule screen, we want to add a special Summary tab at the beginning of the spreadsheet. This helps the client quickly see what's inside the rest of the report — like a snapshot of everything that follows.

How will the data be organized?

The summary will show a breakdown using this order:

  • Week Start (Monday–Sunday)
  • Network
    • Advertiser (each one listed separately)
      • Brand (each one has its own Break Code)
        • Break Code (like LT or NT)
          • Length
          • Daypart

What will the columns be?

  • Rate
  • Length (eq)
  • EUR (Gross)
  • Spots/Week

Each column will include:

  • A grand total
  • Subtotals for each Advertiser Brand

Design Notes

The layout should include indentation so it’s easy to read:

  • Advertisers
  • Brands under each Advertiser
  • Break Codes under each Brand
Business Reason: The client wants a high-level summary that helps them understand what data is in all the other Excel tabs — without having to dig.
Picture
BRID-2981 – Update Logic for Sending Ratecards

BRID-2981 – Logic for Sending Ratecards to Partners

What’s this about?

Before we send pricing information (called ratecards) to our partner platforms like Videology, Amobee, or QTT, we need to make sure two fields are filled out:

  • Factor
  • Ratecard

If those aren’t both filled out, the ratecard should not be sent — or it should only be sent for the ones that are complete.

Scenario Examples

Given: A ratecard job is triggered for Videology, Amobee, and QTT
When: "Factor" and "Ratecard" fields are both filled in
Then: Send to all three (Videology, Amobee, QTT)
Given: Ratecard job includes only one marketplace with both fields filled
When: Other marketplaces are missing data
Then: Send only the completed one

Acceptance Criteria

  • Only send Open, Precision, and Private market ratecards if both Factor and Ratecard fields are filled in.
  • In the output file, only include dayparts where both values are present.
Why this matters: This ensures our partners only get valid and complete data. No blanks. No confusion.
Picture
BRID-2980 – Update Ratecard Distribution by Marketplace

BRID-2980 – Ratecard Distribution by Marketplace

What’s this about?

When a revenue manager updates a ratecard (pricing info), they may only want to change it for one marketplace — not all of them.

This update makes sure the change stays in the same category (like Open Market) and does not spill over to others like Precision or Private Market.

Scenarios

Given: Revenue manager modifies a ratecard in Open Market
When: It’s filled in for some dayparts
Then: Only those dayparts (current and next quarter) in Open Market are updated
Given: Ratecard is updated in Precision Market
Then: System should only apply changes to Precision’s matching dayparts
Given: Ratecard is added in Private Market
Then: System should apply only within that same Private group

Acceptance Criteria

  • Add marketplace as a new condition for applying ratecard logic.
  • If a user updates ratecards for one daypart, only update the same marketplace for the current and next quarter.
  • Do NOT distribute to any other marketplaces.
Why this matters: It prevents sending wrong or incomplete pricing data to other markets that aren't ready — saving time, confusion, and rework.
Picture
BRID-2901 – Update Avails File Logic for Open & Precision Market

BRID-2901 – Avails Logic Update for Open & Precision

What's this about?

Vendors (like 3rd-party partners) want to know how many ad slots they can book. This ticket updates the rules so they can clearly see the max number of ads allowed for a specific hour and selling title — based on advanced logic.

How does it work?

  • The system checks new logic using two special columns:
    • Advanced Platform Factors – “Factor”
    • Max Per Hour
  • The Avails file is now split into two separate files:
    • Open Market: Network_OpenAvails_mmddyyhhmm.xml
    • Precision Market: Network_PrecisionAvails_mmddyyhhmm.xml

What should be tested?

  • Confirm that max available ad slots are shown correctly for each selling title and hour.
  • Validate the split logic: Open Market vs. Precision Market files are generated correctly.
  • Check that logic only includes values that use the new platform factor rules.
Why it’s helpful:
It makes sure partners never guess how many slots they can sell. Everything is calculated and shown clearly.
Picture
AFM – Keep Zero Avails on File for Quarter

AFM – Keep Selling Titles on File Even When Avails Are Zero

What’s the goal?

Sometimes all the available ad slots (called “avails”) for a show get used up. But we still want to show the name of that show (the Selling Title) on the file for the entire quarter. Why? So our partners like Amobee don’t get confused when something disappears.

How will it work?

  • Even when the avails = 0 for a title, the title still stays on the file for the rest of the quarter.
  • This is only for the current quarter — not forever.
  • Example: If a show had 1 slot left on Monday and that slot was used, we still show the show’s name on Tuesday.

What needs to be true?

  • The file logic checks if avails = 0
  • If it is, the Selling Title still appears
  • This continues until the quarter ends
Why this matters: Amobee was having trouble when titles disappeared after being bought out. This fix keeps their records consistent and easy to reconcile.
Picture
Proudly powered by Weebly
  • Home
  • About Me
    • Resume
  • My Works
    • Agency File Management
    • Precision Plan Comparison
    • Rigel
    • Sony Sandbox
    • Motherboard
    • Client Config
    • Healix Global - External Website
    • Magna Global - External Website
    • Sample Site Maps Flows
    • Sample Workflow Diagrams
    • JIRA-Issued Story Artifacts
    • Product Documentation
    • Sample Deliverables from Past Roles