Proposal Summary
This proposal outlines the development of a feature to track and manage version control for service orders in the NetSuite system. The new feature will automatically update a version number field whenever changes are detected in the service order record or its associated sublist items. This will ensure that all modifications are accurately tracked, and the version number will be appended to the document number or name for easy reference.
The estimated effort for implementing the customization in the Sandbox and Production is 18 hours.
The scope and the provided estimate are based on the anticipation, expectation, and understanding through our discussions and email. If the scope change/additional feature development identified during actual development, they will be treated as change request.
Requirement from SteriTek
SteriTek needs to implement a version control system for service orders in NetSuite. A new field will be added to the service order record specifically to store the version number. This version number will be automatically incremented whenever any changes are detected in the service order or its associated sublist items.
Statement of Work (SOW)
We have reviewed the requirement thoroughly and please find below the deliverables we propose.
Key Components:
- A new custom field, “Version Number,” will be added to the Service Order record.
- A User Event script will be implemented to monitor changes within the Service Order, including both body and sublist fields. This script will update the “Version Number” whenever changes are detected.
- To track changes in body fields, the script will utilize a saved search that examines system notes, comparing the date of the search results with the last modified date of the record. This will allow the script to identify any modifications.
- For sublist changes, such as new item lines being added or existing lines being edited, the script will compare the old record with the new one. Any detected differences will trigger a version update.
- If any changes are detected—whether in body fields or sublists—the script will increment the “Version Number.”
- The “Version Number” field on the Service Order record will be updated accordingly, and the document number or name of the Service Order will be appended with the new version number as a suffix in the following format “ServiceOrderName_VersionNumber”.
Assumptions
- When a Service Order is initially created, the “Version Number” field will be empty, and no suffix will be added to the order’s name.
- The “Version Number” will be assigned only after the first edit and save of the record. Upon this first modification, the “Version Number” will be set to “1,” and the name of the record will be updated to “ServiceOrderName_1.”
- With each subsequent edit and save, the “Version Number” will increment, and the name of the Service Order will reflect this by appending the current version number, resulting in a format like “ServiceOrderName_VersionNumber.”
Estimated Effort
Completion of development in NetSuite Sandbox: 16 hours
Production movement after UAT Signoff: 2 hours
Total: 18 hours
Estimate assumptions:
- The estimate includes Project management, risk analysis, system analysis, development, unit testing, regression testing, documentation, and deployment.
- The rate is calculated based on our master service agreement.
- The implementer expects the client to sign off or report bugs within 7 days of UAT submission in Sandbox. If no feedback is received, the work will be considered approved, and an invoice for 16 hours will be issued.
Validity of this proposal
7 days from the date of submission.