Feedback.Response

The Feedback.Response (Dataverse) table records the progress of project closure feedback requests within the CSMS solution.

Each project has one row, which updates as it moves through the feedback workflow.

---

🧭 How It Works

When a project status changes to “Completed”, the Project Manager is automatically sent a feedback approval request. At this point:

• A new row is added to the Feedback.Response table.
• The Feedback Status column is set to “Approval requested”.
  • (Note: This is a choice column, so it maps to a numeric value in the backend.)

---

🧩 Workflow Stages

The Project Manager uses the Feedback App to handle the request in one of three ways:

1. Approve feedback request
   • The survey is sent to the customer.
   • Feedback Status → “Sent”
2. Decline feedback request
   • The PM provides a reason for not seeking feedback.
   • Feedback Status → “Approval declined”
   • The reason is stored in the Feedback rejected reason column.
3. Reroute approval
   • If the PM indicates the wrong person was asked to approve, the approval request is redirected.
   • The Originator email address is updated.
   • Feedback Status remains “Approval requested”

Finally, when the customer completes the survey,

• Feedback Status → “Customer responded”

---

📋 Filtering and Use Cases

When analysing this table, you can filter rows to view specific workflow states:

Use Case	Filter by Feedback Status
All closed projects	(All rows in the table)
Awaiting PM approval	Approval requested
PM approved, awaiting customer feedback	Sent
Customer feedback received	Customer responded
PM declined feedback request	Approval declined

---

🧱 Table Structure

Each record includes standard reference and tracking fields:

Column	Description
Related project	Reference to a project record in tsl_bmtproject
Related account	Reference to a customer record in Account
Customer contact name	Name of the customer contact who received the survey
Customer contact email	Email address of the customer contact
Originator email address	Initially the project manager’s email; updated if rerouted
Project Item ID	Concatenated company ID / project ID
Project number	Numeric or alphanumeric project reference
Project name	Descriptive project title
Feedback rejected reason	Text field storing the PM’s reason for declining feedback

---

🔄 Next Steps

The table will begin populating automatically once the next “Completed” project flows through from the Data Warehouse.

A full write-up with flow charts and visuals will follow shortly.

If you need additional data or support accessing the table, please get in touch.