Odoo Information | My Website

Role home screens, a lean task form, the NODE menu, plain-English guides, the hiding of unused apps (release 1); stage hygiene and stage→milestone labels (release 2); the board and the one-page job sheet (release 2b); lanes — the sheet reads in the viewer's discipline, the spine rail D0–D10, the city-records panel (release 3); Project #, Planned and Spent columns on the lean task lists (release 4); role implies its app badges, the Principal's access table applied once by migration, the access check server action (release 5, People brief Part B); 18.0.1.6.0 (2026-09-29, R110-R114): the Studio's first two screens - My jobs (/node/board: cards with the six-gate ring, Mine then everyone else, only what is owed to the viewer as a number) and The job (/node/job: one page, six gates in words, this week, who owes what, discipline tiles from the job's packets, documents, people with seat words, city record, Ask the Desk); one vocabulary - the ladder names, the D-steps and the task stages leave these pages; the six gates read from the milestone gate code, and the firm's six template lines are given their codes once by migration; every section crash-guarded. 18.0.1.6.1 (2026-09-29, R113 subtract first): the Builder view group; the NODE menu, the Project app and the other working lists leave staff sight (reversibly, previous groups kept); everyone without the Builder view lands on My jobs; the guide page rewritten in the six-gate words. 18.0.1.6.3 (2026-09-29, copy run): the two NODE root menus (NODE, NODE Ledger) leave staff sight too - the 1.6.1 pass had missed them; the Builder-view groups on both roots are now declared in the menu data, so every update keeps them. 18.0.1.6.4 (2026-09-29, three-second run): My jobs shows jobs - a job number or a client - and says in one line how many internal projects it does not show; duty and task rows keep their words beside a long name; the guide header has no stray dot. 18.0.1.6.5 (2026-09-29, the profession's words): the six gates read Agreement signed / Pre-design complete / SD approved by owner / Permit issued / Sign-offs requested / CO issued, project closed; This week names one owner, two, or a team of N; People on this job shows the seats that matter and one line for production. 18.0.1.6.6 (2026-09-29, one vocabulary): the six gates take the words given to Practice that day - Agreement signed / Prerequisites received / Schematic design approved / DOB approval / Closeout started / Closed - and the guide names the five job statuses (Active, On hold, Closed, Archived, Cancelled); the job page says Plans held until payment when the hold is set. 18.0.1.7.0 (2026-09-29, sprint 2, R123-R127): The packet (/node/packet: one page per discipline packet - stage bar, next act, the deliverables with Hand in / Verify / Release / Return behind the agreement module's own guards, the checklist grouped by gate in the one vocabulary and roles as seats, the element cards with Move on, coordination, filing, what the Order says, hours only, Ask the Desk); a discipline tile on the job page opens its packet. 18.0.1.7.1 (2026-09-29, copy run): a job milestone standing in for a discipline without a gate code is shown without acts; the packet's Ask says why when the line does not land. 18.0.1.7.2 (2026-09-29, copy run): Ask the Desk lands again - the duty it writes on the record now holds the job's next gate, which the register requires; without it the whole ask was silently lost. 18.0.1.7.3 (2026-09-29, his words): each deliverable born with the packet shows its phase and the job gate it leads to; the packet's filing block is headed Agency review and approval (his ruling: the stage is the authority's review, not the expeditor's filing); outlines one step darker on every Studio screen. 18.0.1.8.0 (2026-09-30, S2c step a - the panel's shape, his four marked screenshots): one screen answers one question for one seat. The job page leads with the stage word (Agency review and approval included: after G3, a released filed set puts the job at the agency); the six gates are said once, as small marks with their dates - the strip, the count and the 'opens when' banner leave the page (the guide keeps the words); two lines follow: 'Job waits on' (the deliverable in hand and who holds it, the same for every seat) and 'Owed to you' (the viewer's own next act on this job, never a gate). Disciplines sit in the order a building is built, under the industry's names with acronyms (SOE, SCP, BPD, BPP, SSP, TR1, TR8), three lines each: the deliverable in hand and its state, who owes the next act, the open field items; the ring is deliverables released; no producer names, no checklist percent. People becomes one line, Who to call (project manager, filing representative, principal). Documents is named for what it is, Latest files, until the released-deliverables list lands. 'Plans held until payment' reads 'Release hold on this job'. My jobs: nobody gets a wall of everyone else's jobs - a card leads with the stage and what the job waits on; the rest is a count and a link (All jobs); the principal sees every active job as rows under what needs him or is late. A practice-copy bar sits above the top line on the copy. 18.0.1.8.1 (2026-09-30, the panel's review of the mockup, his yes): one item, one place - Owed to you holds the acts others wait on (verify, release, seal, duties, field items), Due from you holds the viewer's own hand-ins and tasks with whom they go to and never a blank date, the principal's list splits into Your ruling and Your seal; a seat sees only the buttons its guard would allow, the person who verified reads a grey line instead of a Release button, the Principal's release in the reviewer's stead is its own act with a reason; the Seal on a released filed set with the link to the sealed set; Return asks the due-back date; the stage after schematic design keeps its sub-state chain (released, awaiting seal - sealed, ready to file - at the agency since); header rows on every list, no ring on the cards, closed jobs leave Every active job, empty tiles dim, contrast raised; no line describes a person. 18.0.1.8.2 (2026-09-30, proof of the other seats on the copy): a date outside this year carries its year; Due from you says 'you' when the viewer is the recipient; the filing representative's block-and-lot housekeeping sorts behind the filing acts. 18.0.1.8.3 (2026-09-30, proof of the Seal and the release in the reviewer's stead on the copy): Filed - the filing representative enters the filing number on a sealed set from the packet row (node_agreement 1.7.29), and the row then reads filed by, on, under; a release by someone other than the discipline's named reviewer reads in the reviewer's stead; the packet header line is Next on this packet, not Your next act; 1 open item, 3 open items, never item(s). 18.0.1.8.4 (2026-09-30, proof of Filed on the copy): the packet's Agency review and approval block reads the filed set's number and Filed · at the agency since when the packet task carries no application - one truth on the page. 18.0.1.8.5 (2026-09-30): the task's default Not filed no longer hides that word once a set is filed. 18.0.1.8.6 (2026-09-30, proof of the producer's desk): Due from you carries one hand-in per packet - the next deliverable in ladder order, not the whole ladder - and a hand-in without a date sits right after the late rows, not behind every dated task. 18.0.1.8.7 (2026-09-30): the hand-in heads Due from you, ahead of late tasks. 18.0.1.8.8 (2026-09-30): the hand-in row names the reviewer after the project manager from the discipline's named reviewers when the deliverable carries none of its own. 18.0.1.8.9 (2026-09-30, proof of the reviewer's seat on the copy): a verified set waits on the discipline's named reviewer - the release sits on that person's desk (Owed to you / Your ruling), and with no reviewer named the principal reads 'name the reviewer'; the packet header says reviewer <name>, never 'released by' before a release; the named reviewer who verified reads why the release is not theirs; the packet's next act is the first deliverable waiting on someone (verify, release, seal, the filing number), ahead of the checklist. 18.0.1.8.10 (2026-09-30): verify, release and seal rows head Owed to you and Your ruling - a set others wait on comes before undated housekeeping such as the G1 signings. 18.0.1.9.0 (2026-10-02, the Studio's landing pages): (1) a job carries a Multifamily flag and the Studio's pages - board, job list, Verify-Release, My work, The week, Production - list multifamily jobs only, the job page still opening for any job by id; (2) the principal's board is three stacks in order - Seal (released deliverables waiting on his seal, with who verified and released and when), Rule (the reserved rulings, counsel and accountant items plus the open duties a person or the Desk addressed to him, with the recommended answer where the record carries one) and Instruct (one line to a job and a person or the Desk, written as the same duty Ask the Desk writes) - over every active multifamily job as rows with stage, waits-on, project manager and days in stage, late first; the G1 signing line shows only on a job with no released gate still at To Do / Pre-design / Bidding, tasks and hand-ins on closed jobs or dated more than two years back leave his screen, and his Due from you shows the last 30 days and what is ahead with the rest as one count; every other seat's board as it was; (3) Verify-Release (/node/release): every deliverable waiting on the viewer's own act, grouped Verify / Release / Seal / Enter the filing number, with the packet's own act buttons and guards and the grey line where a guard says no; (4) My work (/node/work): the hand-ins and tasks due from the viewer, late first, dated next, undated last, one hand-in per packet; (5) The week (/node/week, project managers and the principal): this week's and overdue dates per job - deliverables, tasks, field items, application dates where the record carries them - under the job's waits-on line, a Desk-chases marker and Hold where the row's record carries an on-hold mark; (6) Production (/node/production): the last model run per job read from the job's *_model_run.json, Run again queuing a request (node.production.request) the Desk runs at night, and the model's health; (7) the NODE root keeps five entries for everyone - My jobs, The job, The packet, Verify-Release, My work - plus The week and Production for the project-manager group and the principal, the twelve working lists under Builder's desk (Builder view only, xml-ids kept), How a job moves a footer link on every Studio page; (8) Show as - a top-right switch for the Builder view only, rendering another seat's view with the viewer's own rights; (9) version 18.0.1.9.0, the new templates, controller, model and access rows declared. 18.0.1.9.1 (2026-10-02, panel review applied): (1) The week reads the agency clock date from the submission tasks (clock_due, with the application number and who submitted it) instead of five field names no model carries, and its line says agency clock dates; (2) hold mark - one On hold mark (node_on_hold) on tasks, deliverables and field items (models/hold_mark.py): Hold sets it, Back on the week clears it (same POST route, mark=off), the row stays on the record and shows on hold, and Desk chases shows only on rows not on hold whose date is overdue or within the week; (3) the principal's two computed rulings - name the reviewer for a verified set whose discipline has none, sign the agreement and release G1 - join his Rule stack, blocking first; (4) the Rule stack drops the Recommended answer column, which no record carries yet, and Who asks reads not recorded where no author is known; (5) menu: The job is All jobs, The packet is gone (it opened the same board), the Builder's desk list is My jobs (the list); (6) Verify-Release's standing line carries day names; (7) My work sorts as the board does - your hand-in first, then late, then by date; (8) field-item rows say the date once; (9) Production says what the model and a run are, reads health as sound / needs a look / failing, offers Run where no run is recorded, and its one-line empty states are sentences; (10) the words of the panel's section 3 - My desk, Verified by - released by, Which job?, late tasks, project manager <name> / no project manager yet, nobody named, To, Instruction as the subject of an Instruct note; (11) the Multifamily flag stays set by hand by the Desk - no migration - and its help says so; (12) Pipeline page (/node/pipeline, menu Pipeline; the principal, the Builder view and Sales users) - five columns of cards, Front door, Lead, Proposal out, Agreement signed, Job born, each card who, what, who owes the next move and since when, amber after ten quiet days; Not a lead archives an enquiry; an order is read by name, client, date and salesperson only; (13) version 18.0.1.9.1, the new controller, model and template declared. 18.0.1.9.2 (2026-10-02, panel review of 1.9.1): (1) the principal's job rows count late tasks only within the last 24 months, so years-old tasks never lead or label the list; (2) Rule: the 'sign the agreement and release G1' line is gone; 'name the reviewer' stays and now carries its recommended answer; a line without a recommended answer does not appear and is counted in one line instead; one line counts the jobs at To Do with no gate recorded - their project managers set them; Who asks reads 'the job's ladder (a computed line, no one asked)'; (3) The week makes no promise: each row has Chase, which marks it for the Desk's next round with who asked and when (new chase mark on tasks, deliverables and field items), and Done on a plain task, which closes it through its own state; deliverables, field items, packets and agency submissions are not closed from The week; the heading reads 'Chase marks a row for the Desk's next round; Hold takes it off the week's reminders'; Hold, Chase and Done are for the job's project manager and the principal, and an on-hold row says who held it and when; '3 late' reads '3 late items'; (4) Pipeline: no enquiry note is printed; Lead is an act - 'Lead - move on' moves the enquiry to the next stage, no enquiry form is opened; the page and its menu open to the principal, the Builder view and a new group, NODE intake - Pipeline (members named by the COO), in place of every Sales user; the front door shows every open enquiry at the first stage with no client test and no 14-day cut; the principal and the Builder view see new jobs of the last 14 days not yet on the Studio list; 'the front desk' and 'Sales' read 'not assigned yet'; the agreements line no longer claims a job is born at signing; (5) the board: 'Owed to you' reads 'Waiting on you'; Instruct is the principal's line, goes only to someone on that job, the principal or the Desk, and says so when the job is not on the register yet and no duty was written; tasks older than 24 months or on closed jobs leave every seat's lists, not only the principal's; a week deliverable with nobody on its packet reads 'no one named on the packet'; (6) version 18.0.1.9.2. 18.0.1.9.3 (2026-10-02, the live landing): flags the firm's multifamily jobs once on upgrade - the 48 jobs the Desk ticked on the practice copy, found by job id and exact name (by exact name alone where the id's name differs), never unticking any and writing nothing else - so My jobs is no longer empty on the live system; new jobs are still ticked by the Desk; dates on every Studio page read in New York time and today is New York's today (panel D7); version 18.0.1.9.3. 18.0.1.9.4 (2026-10-02, the record put right): (1) project managers from the job's own threads - on upgrade the project manager is set, once, on the three jobs where the job's Team plainly shows who runs it (1536 Gillespie Ave and 1780 Topping Ave to Sebastian Roverano, 1255 Fteley Ave to Ranim Hadeed), found by job id and exact name and the person by login; a job already right is left alone, every change goes to the log, nothing else is written; (2) a job with no gate recorded shows the record's own stage with the words stage from the record - gates not yet marked, on the board, the job page and The week, never Pre-design waiting on a signed agreement; (3) rehearsal and test records - a job or an enquiry whose name carries rehearsal, numbering check or vvTEST anywhere, or a word that starts with test (Test, test-portal; never Whitestone or Latest), whatever the case - leave every Studio list and the Pipeline, through one helper; (4) the Pipeline's front door shows at most 30 enquiries, only those that name a street address or carry a known client, and counts the rest in one line; Proposal out and Agreement signed show the last year and count the older ones in one line; version 18.0.1.9.4.

WhatsApp Messaging

Text your Contacts on WhatsApp

Sign

Send documents to sign online and handle filled copies

Helpdesk

Track, prioritize, and solve customer tickets

Quality

Control the quality of your products

eLearning

Manage and publish an eLearning platform

Planning

Manage your employees' schedule