Scribd
Upload
6 views6 pages

CX - API For Customer Invoices

The Business Requirements Document outlines the project for creating an API to send customer invoices from Salesforce, aiming to improve the claims process by utilizing invoices regardless of order age. Key requirements include adding an option for customer invoices in Salesforce and creating an API to retrieve invoices. The document also includes a test plan and a glossary of terms related to the project.

Uploaded by

Prem Chand Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views6 pages

CX - API For Customer Invoices

The Business Requirements Document outlines the project for creating an API to send customer invoices from Salesforce, aiming to improve the claims process by utilizing invoices regardless of order age. Key requirements include adding an option for customer invoices in Salesforce and creating an API to retrieve invoices. The document also includes a test plan and a glossary of terms related to the project.

Uploaded by

Prem Chand Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Information Technology: Project Planning

Business Requirements Document (BRD)

Project Information

Business Unit CX
Project Sponsor Brian Gerello
Project Name CX – API for Customer Invoices
Project Number / Identifier FETR0031129
Business Relationship Manager Sheri Schrier
11/07/24
Background and Context Support Sending Customer Invoices from a Request in Salesforce.
Business Objective Customer Care is pulling the customer order acks today from Salesforce to reference for claims cases. This
only works if the order has not been purged. We want to change to using customer invoices for the claims so
the process will work regardless of age of the order.

Notable Differences from Current State to Future State


Currently :
Future state:

JELD-WEN Confidential Page 1


Information Technology: Project Planning
Business Requirements Document (BRD)

Business Requirements and Functional Requirements

Business Requirement Document (BRD) Functional Requirement Document Priority


(FRD) and Non-Functional
Requirements (NFRD)
Business Business Requirement / Use Case (“Why”) Functional Functional Requirement / E,C,O
Requirement Requirement Use Case (“How”)
ID # ID # Note: Include business,
compliance, security,
performance, etc.
Priority: Essential (E),
Conditional (C), Optional (O)
BR_001 Add an option for customer invoices to the Actions button from the order search O
Salesforce results that works similar to the View Order Acknowledgment Selection Option.
This should call a Titan API for Customer Invoices.

JELD-WEN Confidential Page 2


Information Technology: Project Planning
Business Requirements Document (BRD)

BR_002 Create an API for Salesforce to call to retrieve invoices.


Salesforce should pass the Entity and the invoice number along with the selection parameters
Titan & shown in the screen shot below… some may be always used for the print option vs. ones that
Salesforce Salesforce sends. Titan should generate an invoice from the custinv.rpt

Will need to support deselecting all print options for invoices can be generated without the
prices. These will be used for claims cases where we may want to send item detail to a
homeowner or installer, but not show the price the dealer paid for the product.

BR_003 Similar to the order acks, once the invoice is retrieved, it should attach in the file upload where
Salesforce agents can select to send it and it could be viewable in the field service mobile app by technicians
in the field

JELD-WEN Confidential Page 3


Information Technology: Project Planning
Business Requirements Document (BRD)

Test Plan

 Preferred Test Server: GRISUP/btst (based on which db the Salesforce sandbox is pointed to
 Preferred Test Database: stflush/btflush
 Preferred Test Entity: DV
 Titan functions: custinv.rpt
 Known impacts:

Test Steps – Please provide detailed steps (including screenshots where possible/reasonable) of both the modified functions and other related
functions

1. Agent will use the Salesforce Order Search to look up order 214841 from entity DV in the Sales History Status.

2. From the Actions Menu, select Customer Invoice. (current screen, new screen should have a View Invoice option.

JELD-WEN Confidential Page 4


Information Technology: Project Planning
Business Requirements Document (BRD)

3. Validate the invoice attaches to the file upload to be used by the agent to view and/or send out. The file should be accessible by technicians
in the field service mobile app too.

Glossary of Terms

Term Abbreviation Description / Definition


JELD-WEN Confidential Page 5
Information Technology: Project Planning
Business Requirements Document (BRD)
/ Acronym
Essential Requirement E Solution will not function or be acceptable unless the requirement is delivered in an agreed manner
Conditional Requirement C Requirement that would enhance the solution or product, but would not render it unacceptable if it were absent
Optional Requirement O A requirement that is not mandatory for the solution or product to function

JELD-WEN Confidential Page 6

You might also like