2023.13: Document Labels, PO Email Info, NTE Update

Created by Kenneth Abad, Modified on Tue, 12 Sep, 2023 at 12:37 PM by Kenneth Abad

Features:   


Document Labels (BN-5003, BN-5084): We have made some changes to document labels based on where the document is being uploaded in the system. We have removed unused labels and renamed all 'quote' labels to 'proposal' to keep consistent throughout the app. 


Label changes:

  1. Client Quote → Client Proposal

  2. Quote Approved → Proposal Approved

  3. Quote Declined → Proposal Declined

  4. Supplier Quote → Supplier Proposal

  5. Vendor Quote → Vendor Proposal


Label Removals:

  1. Correspondence

  2. Quote


Label Additions:

  1. Certification


PO email information (BN-5053): Changes have been made to the subject line layout for any PO that is sent from the system. The structure for the new subject line will be: Tracking#, Client, Location, Priority.



NTE Update on Approval (BN-4149): This update brings a change to Work Orders. When a vendor proposal is approved, the NTE on the vendor Purchase Order for the vendor will automatically be updated to match the costs in the proposal. This change also affects Client Proposals that are approved, as they will now update the DNE on a work order to the total cost of the proposal automatically.


If there is already an approved proposal, when a new proposal is approved, it will take the costs from the most recently approved proposal and update the NTE/DNE from there.


Bug Fixes: 


Projects AIA Invoice (BN-5278): We have fixed a bug with the AIA invoices for Projects that was causing values to not populate on the PDF.


Toast Links (BN-5298): We have fixed a bug that was causing all toast pop ups, not the bread, to have broken links and not lead to their intended destination. They will now correctly guide you to the correct destination.


Duplicate Vendor bug (BN-5257): We have fixed a bug that was causing errors when marking a vendor as a duplicate.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article