Frappe HR (HRMS) Jobs Page

George-Raafat · August 29, 2026, 7:34am

Hi,
I got this error in “https:///job_application/new?job_title=HR-OPN-2026-0001”
$ bench version
erpnext 16.33.0 ()
frappe 16.32.0 ()
hrms 16.17.0 ()

I tried to enter as a new applicant without loging in, after some search, I think the error is coming from here:

github.com/frappe/hrms

hrms/hr/web_form/job_application/job_application.json

version-16

{
 "allow_comments": 1,
 "allow_delete": 0,
 "allow_edit": 0,
 "allow_incomplete": 0,
 "allow_multiple": 0,
 "allow_print": 0,
 "anonymous": 0,
 "apply_document_permissions": 0,
 "client_script": "frappe.web_form.after_load = () => {\n\tconst job_opening = frappe.utils.get_query_params().job_title;\n\tif (!job_opening) return;\n\n\tfrappe.call({\n\t\tmethod: \"frappe.client.get_value\",\n\t\targs: {\n\t\t\tdoctype: \"Job Opening\",\n\t\t\tfilters: job_opening,\n\t\t\tfieldname: \"job_title\",\n\t\t},\n\t\tcallback: (r) => {\n\t\t\tif (!r?.message) return;\n\t\t\tconst title = frappe.utils.escape_html(r.message.job_title);\n\t\t\t$(frappe.web_form.fields_dict[\"job_title\"].wrapper)\n\t\t\t\t.find(\".control-value\")\n\t\t\t\t.text(title);\n\t\t},\n\t});\n};\n\nfrappe.web_form.on(\"resume_link\", (field, value) => {\n\tif (!frappe.utils.is_url(value)) {\n\t\tfrappe.msgprint(__(\"Resume link not valid\"));\n\t}\n});\n",
 "condition_json": "[]",
 "creation": "2016-09-10 02:53:16.598314",
 "doc_type": "Job Applicant",
 "docstatus": 0,
 "doctype": "Web Form",
 "hide_footer": 0,
 "hide_navbar": 0,
 "idx": 0,
 "introduction_text": "",
 "is_standard": 1,

This file has been truncated. show original

is anyone else facing this issue or am I doing something wrong?

Support-BizloomERP · August 30, 2026, 7:00pm

I faced the same issue. The problem seems to be that the Job Application Web Form is calling frappe.client.get_value from after_load, but the request is being made as Guest when the candidate is not logged in.

I wouldn’t recommend whitelisting frappe.client.get_value globally just to fix this.

A safer approach is to create a small guest accessible whitelisted method that only returns the required job_title, and call that method from the Web Form instead.

Alternatively, if this was introduced/fixed in a later HRMS v16 release, upgrading HRMS would be the first thing I’d try before maintaining a custom patch.

For anyone running hrms 16.17.0, it would be interesting to know if the issue is still present on the latest v16 release.