FAQ

General

Does this work without ERPNext?

Yes. The app requires only Frappe (v15 or v16). ERPNext is optional. It works with any DocType that has a Frappe Workflow attached — HR leave applications, custom approval flows, project approvals, etc.

Does it modify my source documents?

No. The app is entirely read-only with respect to your source documents. It reads workflow state and assignment data, then writes only to its own tables: Reminder Log and Approval SLA Record.

What happens to documents already past the SLA threshold when I first install?

On the first scheduler run after installation, the engine will process all matching pending documents — including old ones. If you have a backlog of stale approvals, expect an initial wave of reminders. You can limit this by setting a high Pending Days value on your rules temporarily, then lowering it once the backlog is cleared.

Can I have different rules for different companies?

Yes. The Company field on a rule filters it to documents belonging to that company. Create one rule per company as needed.

Rules

What if no Workflow State is set on the rule?

The rule matches any document of the target DocType that has been pending (in any state) for longer than the Pending Days threshold. This is useful when you want to chase all pending documents regardless of their specific state.

Can I use the same rule for multiple DocTypes?

No — each rule targets one Reference DocType. Create separate rules for each DocType you want to monitor.

What does Max Reminders = 0 mean?

Setting Max Reminders to 0 on a rule tells the engine to use the Global Max Reminders value from Approval Reminder Settings. Setting the global value to 0 means unlimited reminders.

Escalation & SLA

Can I escalate to a whole team?

Yes. Use Escalate To Role in an escalation step. All enabled users with that role receive the escalation notification.

Does the SLA clock reset when a document changes state?

Yes. The engine tracks Entered State On — when the document entered its current state. If the workflow moves the document to a new pending state, the SLA clock restarts from that point.

How is average approval time calculated?

It is the average of Approval Date - Document Created On across all closed SLA records (where Approval Date is populated).

Was this article helpful?