Related

• Document templatesScreen

  The list of your organization's document templates (demand letters, offer letters, termsheets, agreements, allotment letters, receipts, cost sheets), with filters and the actions to create, duplicate, open or delete one.

• Document templateScreen

  The template designer: write a template's wording with merge fields, set its letterhead, title and page layout, preview it against a real record, and publish, retire or restore its versions.

• LetterheadsScreen

  Set up the branding wrapped around generated documents: logo, header and footer, page size, orientation, margins and page numbers, for the whole organization or for one project.

• RulesScreen

  Every automation rule in your organization, system and custom, with filters, the switch that turns each rule on or off, and shortcuts to edit, test, clone, see the run history of or delete a rule.

• RuleScreen

  One automation rule's page: read or change its basics, trigger, conditions and actions, test it against a record, clone or delete it, and switch a system rule on or off.

• Message templatesScreen

  The list of your organization's message templates: the wording that Send email actions and campaigns use, with filters and the actions to create, open or delete one.

• Booking documentsScreen

  The letters and agreements generated for one booking, such as the allotment letter, together with the receipts of its payments and the letters of its demands, with the button to generate another from a published template and the icons to preview, download, email, void or delete each one.

• EstimateScreen

  One estimate version: its charges by group, payment plan, approvals, unit and parking hold and validity, with the lifecycle actions to send, finalize, request approval, approve or reject, extend, cancel, version and book.

• Society & TenantsScreen

  On a redevelopment project, link the society being redeveloped, keep its members and the project's landowners and PAP tenants, and give each of them an offer that allots new units and sets the benefits the developer pays.

• Set up a letterheadHow-to

  Create the organization's default letterhead with its header, footer, page size and margins, upload the logo, and optionally add a project's own letterhead, so generated letters carry your branding.

• Design a new document templateHow-to

  Create a document template for a record type, write its wording with merge fields, repeat a table row for line items, show a block only when a condition holds, preview it against a real record and publish it so people can generate documents from it.

• Revise, retire or reopen a published templateHow-to

  Change a published document template without disturbing the version in use, publish the changes as a new version, go back to an earlier version, and take a template out of use or bring it back.

• Generate a document from a recordHow-to

  From a booking, demand, opportunity, estimate or offer, pick a published template and a format, generate the numbered document, check it on screen and download it; every document is also listed in the organization-wide Generated documents log.

• Issue an offer with its letterHow-to

  Publish the offer letter template once, then issue a draft offer so the letter is generated and filed with it and the offer moves to Issued.

• Document templates, published versions and letterheadsConcept

  A document template is an HTML letter with merge fields written for one record type; publishing it freezes a numbered version that generation uses while the draft stays editable, and a letterhead (the template's own, else the project's, else the organization's default) supplies the logo, header, footer and page layout around it.

• System rules and starter templatesConcept

  The 53 automation rules, six email templates and six draft document templates every organization starts with: which ship switched on, why the customer-facing ones ship off, what is locked, and how to switch, clone or customise them.

• Workflow rules, conditions, actions and the rule ownerConcept

  What a workflow rule is made of (one kind of record, one trigger, conditions, ordered actions, an optional chained event), how conditions and action settings are evaluated, how versions, tests and clones work, and why every rule has an owner whose permissions its runs use.

• Template will not save, publish or render: a tag, expression or the HTML is wrongTroubleshooting

  A document template, message template or rule action that carries a broken merge tag is refused when saved or published, names the field and the line; a template that parses but fails while filling in a record, or whose HTML the PDF or Word engine cannot lay out, fails at preview, generation or sending; the editor's own dialogs and fields have their own checks.

• Generate document has nothing to offer: no published template for this record typeTroubleshooting

  Documents are generated only from published document templates of the record's type; the starter templates (cost sheet, allotment letter, offer letter and others) ship as drafts, so until someone publishes one, Generate document has nothing to pick, offers issue without a letter and workflow rules that generate the template fail.

• Email shows as logged or refused: the mail server is not configured or rejected the messageTroubleshooting

  Outgoing mail is sent through a mail server set up for the installation, not inside the app; while none is configured every email (document, campaign, workflow, invitation, verification) is only logged and reported as not delivered, and when the server refuses a message the recipient is marked failed; the person who runs the installation configures mail, then you resend.

• "No access" or "You do not have permission": your role lacks a permissionTroubleshooting

  Every screen, button and picker is gated by a permission on a module; your role decides which you hold, so a missing one shows as a No access card, a refused action, a greyed-out button with a hover reason, or a picker that explains which permission it needs.