EMS

Technical Reference: ems.certificate

Overview

A certificate request is a student (or former student) asking the centre to certify something about them. The centre issues it as a numbered PDF, stamped in EMS by whoever issued and approved it. Each request belongs to a certificate type (ems.certificate.type), which defines what the certificate says and the approval circuit: an ordered list of steps, each one done by whoever holds a position of the centre (ems.role). The administrator configures the types and their circuits from Academic management > Configuration > Certificates > Certificate types.

EMS ships one type, FCT (Formació en Centres de Treball): it certifies that the student completed a number of hours of workplace training at a collaborating company. Its circuit:

  1. the VET coordinator (ems.role_vetcoord) completes the company’s details (company, VAT number, period, hours, agreement registration number);
  2. the Secretary (ems.role_secretary) issues it: it gets its number and the “Issued” stamp;
  3. the Director (ems.role_director) approves it (“Vist i plau”): the final PDF is generated, with the pages of the required documents appended (FCT: the agreement), and sent to the applicant.

How a request starts:

The applicant’s details (name, identity document, study, school year of the FCT) are mandatory; the company’s (name, VAT number, period, hours, agreement number) are optional, since the applicant rarely has them: the VET coordinator completes them.

Documentation. A type may require documents (Required attached documentation, with one line per document: e.g. FCT requires the FCT agreement). Each line says who may attach it: the applicant, positions of the circuit, or - nobody ticked - anyone taking part; the administrator always. Every required document must be attached before the issuing step, and a line with Add to the certificate has its pages appended to the PDF. Besides, any request takes Other documentation: optional files anyone taking part attaches, never added to the certificate.

Not a qualified electronic signature: the stamps are EMS’s own record of who issued and approved the certificate (ems.report_validation_stamp, as in minutes and convalidation resolutions).

Module files: models/certificates/certificate.py, models/certificates/certificate_type.py, models/certificates/certificate_wizard.py, models/contacts/portal.py (_ems_can_file_requests_for, _ems_certificate_portal_visible), models/contacts/contact.py (contact_type company), controllers/portal_certificate.py, reports/certificates/report_certificate.xml, mails/certificates/certificate.xml, data/main/ems.certificate.type.xml, data/main/mail.activity.type.csv, data/main/res.partner.category.csv, data/cat/ems.role.csv (role_vetcoord → group_vet_coordinator), security/groups.xml, security/rules/certificates.xml, security/ir.model.access.csv, views/academic_management/certificates/, views/academic_management/certificate_type/, views/community/contact/company.xml, views/portal/portal_certificates.xml, tests/test_certificate.py, tests/test_portal_certificate.py, tests/test_certificate_tour.py, static/tests/tours/certificate_tour.js, tests/test_docs_screenshots_certificates.py (the manuals’ screenshots)

Hierarchy and relations

erDiagram
    EMS_CERTIFICATE_TYPE ||--|{ EMS_CERTIFICATE_TYPE_STEP : "step_ids (cascade)"
    EMS_CERTIFICATE_TYPE ||--o{ EMS_CERTIFICATE_TYPE_DOCUMENT : "document_ids (cascade)"
    EMS_ROLE }o--o{ EMS_CERTIFICATE_TYPE_DOCUMENT : "role_ids (who attaches it)"
    EMS_CERTIFICATE ||--o{ EMS_CERTIFICATE_DOCUMENT : "document_ids (cascade)"
    EMS_CERTIFICATE_TYPE_DOCUMENT ||--o{ EMS_CERTIFICATE_DOCUMENT : "type_document_id (cascade)"
    EMS_CERTIFICATE_DOCUMENT }o--o{ IR_ATTACHMENT : "attachment_ids (its files)"
    EMS_CERTIFICATE_TYPE }o--o{ EMS_LEVEL : "level_ids (who may request it on the portal)"
    EMS_ROLE ||--o{ EMS_CERTIFICATE_TYPE_STEP : "role_id (restrict)"
    EMS_CERTIFICATE_TYPE ||--o{ EMS_CERTIFICATE : "type_id (restrict)"
    EMS_CERTIFICATE_TYPE_STEP |o--o{ EMS_CERTIFICATE : "step_id (current step)"
    RES_PARTNER ||--o{ EMS_CERTIFICATE : "student_id (restrict)"
    RES_PARTNER |o--o{ EMS_CERTIFICATE : "training_company_id (collaborating company)"
    EMS_STUDY |o--o{ EMS_CERTIFICATE : "study_id"
    EMS_COURSE |o--o{ EMS_CERTIFICATE : "course_id (course it was issued in)"
    EMS_CERTIFICATE ||--o{ EMS_CERTIFICATE_STAMP : "stamp_ids (cascade)"
    EMS_CERTIFICATE }o--o{ IR_ATTACHMENT : "other_attachment_ids (optional documentation)"
    EMS_CERTIFICATE |o--o| IR_ATTACHMENT : "certificate_pdf_id"

ems.certificate.type

Field Type Notes
name Char, translatable E.g. “FCT (Formació en Centres de Treball)”.
kind Selection What the certificate says and which data it needs: only fct for now. Each kind has its own report body and form fields.
level_ids M2m ems.level Levels whose current students may request it from the portal (FCT: CFGM, CFGS). Empty: never offered on the portal (the secretariat still registers it).
requires_documents Boolean “Required attached documentation”: the document_ids lines are required before the issuing step (FCT: yes). Ticked with no line is refused (_check_documents).
document_ids O2m ems.certificate.type.document The required documents, by sequence.
step_ids O2m ems.certificate.type.step The approval circuit, by sequence.
active Boolean Archived types are no longer offered.

ems.certificate.type.document

Field Type Notes
sequence, name Integer, Char (translatable) Order and the document’s name (“FCT agreement”).
applicant_uploads Boolean The applicant may attach it (portal or form link).
role_ids M2m ems.role Positions whose holders may attach it (the type form offers the circuit’s). Neither the applicant nor a position ticked: anyone taking part.
append_to_certificate Boolean Its pages are appended to the PDF.

Seeded in data/main/ems.certificate.type.xml with noupdate="1": the centre configures the circuit from the UI and no upgrade reverts it.

ems.certificate.type.step

Field Type Notes
sequence, name Integer, Char (translatable) Order and label (“Complete the company’s details”).
role_id M2o ems.role Whose step it is: its holders get the task and may act. The administrator may always act too.
action Selection complete (“Complete the data”: fills in data, moves on), issue (“Issue the certificate”: number + “Issued” stamp), approve (“Approve”: “Approved” stamp). The labels are full phrases on purpose: a bare “Issue” or “Complete” would take another screen’s translation (“Incident”).

Constraints (_check_steps on the type): at least one step, exactly one issue step, and every approve step after it. The last step finishes the request: the PDF is generated and sent.

ems.certificate (request)

Field Type Notes
name Char CERT-<start>-<end, two digits>-<4-digit counter> (e.g. CERT-2026-27-0001), assigned by the issue step (ems.base.next_course_number, code ems.certificate.course.<id>), in the course current on that day (course_id). Empty before: a cancelled or rejected request uses no number.
type_id, kind M2o, related  
state Selection draft (waiting for the applicant’s form, former students only), in_progress, documentation (waiting for the applicant), issued, rejected, cancelled. Written by the actions only (write() refuses it outside sudo).
step_id M2o ems.certificate.type.step The current step while in_progress/documentation.
student_id, requester_id M2o res.partner The student (or former student) in EMS, and who filed it on the portal. Optional: a former student who is not in EMS is opened with only their full name (student_name) and email (_check_applicant), and fills in the rest in the form.
origin Selection portal or secretariat.
applicant_email Char Where a former student’s form link, requests for documentation and the certificate go. Portal requests use student_id._ems_informed_recipients().
student_name, student_document, study_id, fct_school_year Char, Char, M2o, Char The applicant’s details, mandatory on submission. Prefilled from the contact when known. study_id must belong to one of the type’s levels (_check_study_level; the form and the portal only offer those). On the portal, fct_school_year suggests the courses EMS has (a datalist) but takes any text, for older years.
training_company_id M2o res.partner Collaborating company (contact_type = 'company'). Required by the complete step and after.
company_name, company_vat Char What the applicant wrote, kept as text: the form never creates contacts. Create company (action_create_company) creates one from them.
period_start, period_end, hours, agreement_reference Date, Date, Integer, Char The workplace training; the first three required by the complete step.
document_ids O2m ems.certificate.document One line per required document of the type, created with the request (_ems_sync_documents, again if the type changes while in draft). Each must have files before the issue step.
other_attachment_ids M2m ir.attachment Optional documentation, anyone taking part. Never appended.
stamp_ids O2m ems.certificate.stamp One per finished step: step, action, user, date. The PDF prints those of issue and approve steps.
certificate_pdf_id M2o ir.attachment The final PDF.
applicant_form_open Boolean The applicant may still edit their form from the link: set when the form is sent or the portal request filed, cleared as soon as someone of the centre writes the request (or one of its documents) or acts on it (step done, return, request documentation, reject, cancel). _ems_portal_can_edit(): in draft, or in progress with this flag. While open, the portal shows the form with Save changes (_ems_portal_fill updates and leaves a note).
info_request, return_reason, reject_reason, cancel_reason Text Last request for documentation, the last return to the previous step, why it was rejected or cancelled.
step_user_ids M2m res.users, computed, searchable Holders of the current step’s role. is_pending_for_me (searchable) = the current user is one of them, or is the administrator and the request is in progress. can_act = may press the step’s button. can_manage = may reject, cancel or mark the documentation received: the secretariat (and the administrator) or a holder of the current step. can_issue_now = may issue it right away (action_issue_now): a holder of the issue step’s position, or the administrator, while the request is in draft or before that step. The form only offers each button to whoever can use it.

ems.certificate.document (a required document of a request)

Field Type Notes
type_document_id M2o ems.certificate.type.document Name, order, who attaches it and whether it is appended come from it.
attachment_ids M2m ir.attachment Its files (PDF or images), tied to the line by ems.attachment_link_mixin, so they follow the request’s access rights.
uploaders, is_attached, can_upload computed Who attaches it (“Anyone”, or the applicant and positions); whether it has files; whether the current user may attach them (administrator, anyone-line, or holder of one of its positions, while the request is open). write() only accepts attachment_ids, and only from who can_upload.

On the portal, the applicant gets one file input per required document they may attach (document_<ems.certificate.type.document id>) and one for other documentation (documents); _ems_portal_attach ignores a document the applicant may not attach.

CRUD flow

stateDiagram-v2
    [*] --> draft: secretariat registers a former student's request
    draft --> in_progress: applicant submits the form (token link)
    [*] --> in_progress: portal request (current student or family)
    in_progress --> documentation: Request documentation
    documentation --> in_progress: applicant answers / Documentation received
    in_progress --> in_progress: step done (next step) / Return (previous step)
    in_progress --> issued: last step done (PDF + email)
    in_progress --> rejected: Reject
    draft --> in_progress: Issue it now (issue step done)
    in_progress --> in_progress: Issue it now (earlier steps skipped)
    draft --> cancelled: Cancel
    in_progress --> cancelled: Cancel (before the issue step)
    cancelled --> in_progress: Reopen (first step)

Emails

The four emails (mails/certificates/certificate.xml: the form for a former student, a request for documentation, the certificate issued, the request rejected) use the card layout of EMS emails, as the Google account ones (ems.mail_layout_certificate, built on ems.mail_layout_card in views/shared/mail_layout/card.xml). Its button opens the request with its access token and says what to do there by the request’s state: fill in the form, answer the centre, download the certificate, or see the request.

Performance

Measured on a synthetic fixture of 300 requests (rolled back), as a holder of the VET coordinator position: list Pending for me (80 rows) 24 ms / 16 queries cold, 14 ms / 4 warm; list without filter 14 ms / 6 cold; form read 18 ms / 23 cold, 1 ms warm; the documentation lines’ can_upload 14 ms / 15 cold. A centre issues FCT certificates in the order of tens to a few hundred a year.

Permission audit (2026-11-17)

Every role of ROLE_GROUP_XMLIDS, in a rolled-back odoo shell transaction: menus Certificates, Certificate types and Collaborating companies, ACL, readable records and what the views offer. 0 mismatches: the Certificates menu shows to the administrator, the secretariat, the Director and the VET coordinator (Academic management shows to the VET coordinator for it, and nothing else of that menu); the types to the administrator only; the companies to the administrator, the secretariat, Heads of Studies and the VET coordinator. A user given the VET coordinator group without holding the position reads no request: the group comes from the position, and the record rule reads its holders.

Access control

Role ems.certificate Types and steps Notes
Administrator (group_academic_admin) rwcu rwcu May act on any step.
Secretariat (group_secretary) rwc, every request r Registers former students’ requests, sends the form, follows every request up. Acts on the steps of the roles it holds, and, holding the issue step’s, may issue a request right away, skipping the steps before it (action_issue_now).
Director (group_director) rw, every request r Acts on the approve step (role holder).
VET coordinator (group_vet_coordinator, given by role_vetcoord) rw, requests of types with a step of a role they hold r Acts on the complete step.
Any teacher (group_teacher) rw, same rule r A role holder of a step without the menu (any role an administrator puts in a circuit) reaches it from the task.
Portal none (controller with sudo) none Only the student’s own requests (get_portal_student), or the one the token opens.

Collaborating companies

res.partner.contact_type gains company (“Collaborating company”), with its category (ems.partner_category_company) and the menu Educational Community > Collaborating companies. It behaves as a provider contact (company fields, VAT, addresses, child contacts such as the company tutor) but is a separate list, so suppliers and training companies never mix.