Related

• 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.

• Put a starter document template into useHow-to

  Review one of the six starter templates that come as drafts, preview it against a real record, publish it, and switch on the system workflow rule that sends it automatically.

• 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.

• Email, void or delete a generated documentHow-to

  Send a generated document to the buyer as an attachment, cancel one that is wrong by voiding it (it stays on record with its number), delete one that was never sent, and trace what happened in the audit log.

• Switch on a system ruleHow-to

  Switch on one of the ready-made system rules that ship switched off, such as emailing the demand letter when a demand is issued: publish the document template it uses, review and preview its email template, then press Switch on and check its runs.

• Customise a system ruleHow-to

  Change what a ready-made system rule does (its timing, conditions, recipients or wording) by cloning it into your own rule, editing the copy, switching the copy on and the original off.

• Build and switch on a custom ruleHow-to

  Build your own automation rule on the rule editor (what it watches, what starts it, which records qualify and what it does), save it switched off, try it on a real record with a dry run, then switch it on and check its runs.

• Design an email template and use it in a ruleHow-to

  Write a reusable email (subject, designed body, plain-text version and optional generated attachments) with merge fields, preview it against a real record, and have a workflow rule send it.

• Put demand, payout and revenue runs on a scheduleHow-to

  Have demand runs, payout runs, revenue runs and RERA sweeps prepared on a timetable instead of by hand: start from the ready-made schedule on each runs page, adjust the day, time and options, save the rule, or simply switch on the matching system rule.

• Run a manual rule from a recordHow-to

  Press a workflow button on a booking, payment, opportunity, estimate, commission or demand page (for example "Send payment reminder" on a demand), fill in its small form, and follow the run to the end.

• Chain two rules with a custom eventHow-to

  Make one rule start another: define a custom event type, let the second rule listen to it with the On Event trigger, and have the first rule raise it when it finishes.

• Create, assign and complete a taskHow-to

  Add a follow-up task by hand, link it to the record it is about and give it to a colleague; the assignee is told in their notifications, finds it on the dashboard and marks it done.

• Investigate a failed automationHow-to

  When a reminder, task or automatic run didn't happen, check that the workflow engine is working, find the run that failed and read its error, fix the cause, then retry the run or requeue the event.

• DocumentsScreen

  The Documents area of Settings, where you manage document templates and letterheads and see every document generated or uploaded in your organization.

• 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.

• 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.

• Generated documentsScreen

  The organization-wide log of every document generated from a template or uploaded against a record, where you preview, download, email, void or delete them.

• WorkflowsScreen

  The Workflows area of Settings, where you manage automation rules, event types and message templates, and check the runs, the outbox and the engine's health.

• 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.

• New ruleScreen

  Build an automation rule on a full page: which records it watches, what starts it, which records qualify, and the ordered actions it carries out.

• 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.

• Event typesScreen

  The named events a rule can listen to: the system events NirmaanOne raises itself and the custom events you add to chain rules or to raise from your own integrations.

• 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.

• New message templateScreen

  Write a message template on its own page: code, name, channel, record type, subject, the designed email body and its plain-text version, attachments, and the merge-field reference.

• Message templateScreen

  One message template's page: change its wording, attachments and settings, and preview it filled in for a real record.

• RunsScreen

  Every time a rule ran: what started it, which record it worked on, how each action went, and the panel from which an errored run is retried.

• OutboxScreen

  The events recorded when records change, on their way to the rules that listen to them, with the runs each event produced and the panel from which a failed event is requeued.

• HealthScreen

  Whether the automation engine can process what the rules produce: the engine flag, its message queue, its worker, the outbox and run counts, and the scheduler's heartbeat.

• TasksScreen

  Follow-ups for you and your team: add tasks by hand or let workflow rules raise them, link each to the record it is about, assign it, and mark it done.

• NotificationsScreen

  Your in-app inbox: every message the workflow rules sent you, newest first, with links to the records they are about and a way to mark them read.

• 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.

• Merge fields and filtersConcept

  Merge fields are the double-brace placeholders in document and message templates ({{ entity.demand_no }}, {{ contact.name }}) that are replaced with the record's values when a document or message is rendered; filters such as inr, words and date format the value, and Repeat row / Show when add tables and conditional blocks.

• 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.

• Triggers and event typesConcept

  The five ways a workflow rule starts (On Create, On Update, On Event, Scheduled, Manual), the catalogue of system event types the app raises, the daily due-date events for instalments and overdue demands, how recurrences are counted, and custom event types that chain rules.

• 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 runs and the outboxConcept

  How a change becomes automation: the outbox event written with the change, the pick-up that hands it to the engine, one run per listening rule with a recorded result per action, the statuses each passes through, and how Errored runs are retried and Failed events requeued.

• Message templatesConcept

  The reusable wording of the emails that workflow rules, record-page buttons and campaigns send: a code, a channel, a subject and body with merge fields, an optional rich HTML body and up to five generated-document attachments, rendered against the record that triggered it.