iVendNextDevelopers Request a sandbox

A builder's project across its quotes, orders and deliveries in stages

The customer asks: One builder's job kept as a project, with its quotes, orders, deliveries in stages and invoices named to it and listed together

What you build

The builder's project as your manifest's own record type: the builder (a customer), the site, the dates and the stages planned. A Project field of one name on the quote, the order, the delivery and the invoice, and a Stage field of one name on the lines of the quote, the order and the delivery, so Desk's own Create carries both from the quote to every delivery and invoice. The till's sales and orders get a Project field of their own name, so the till day's combined invoice does not take it. A print format, the project sheet, lists the job's documents with the viewer's own rights; each document list filters by project.

Limits

Tell the customer

Each builder's job is one project: its quotes, orders, deliveries in stages and invoices are named to it and listed together on one sheet, so the counter and the office see where the job stands.

What next

  1. Tell the customer the 3 limits above, and write them into the proposal.
  2. Follow the recipe: Project quotes and deliveries by stage.
  3. Copy the sample: S60 — Project quotes and deliveries by stage (pp_pqt), and change it.
  4. Build and test it on your sandbox (request one if you have none; what is on it).
  5. Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
  6. Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.

Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit