Executions
Enforcing judgments: the execution file and its parties, the execution court, enforcement procedures, court decisions and sessions, the money collected and billed, finishing, suspending or rejecting a file, and the reports.
Tutorial 1
Your first execution file
Open an execution file for a judgment the client won, start it, record the amount it awards and its first enforcement procedure.
How-to 6
Open an execution file
Record an execution file with its type, client and the client's role, lawyers, execution court and number, link it to the case or consultation it comes from, or open it from a judged case, a consultation or a client request.
Track enforcement procedures
Record each request the firm files with the execution court, follow it from review to the court's answer, write the response, and finish or reject it.
Record decisions, sessions and hearings
Keep the execution court's decisions and the minutes of its sessions in the file, and schedule a hearing for it, each from the Actions of the file.
Record collections and bill the file
Follow the money of a financial execution, the amount awarded, what the court holds, each payment collected and what remains, print it, and invoice the firm's fees for the file.
Finish, suspend or reject a file
Close an execution file with its reason when it is fully enforced, suspend it while it waits and resume it later, or record that the court rejected it.
Print execution reports
Print the list of execution files for a period, by lawyer, state or client, and the list of the neglected ones.
Reference 8
Models and fields
Executions defines 26 model(s) and 227 field(s) on Jaah 19.0. This page lists every model the app creates or extends and the purpose of each field. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Menus and actions
Executions adds 17 menu(s) and 21 action(s). Each entry shows the full path as it reads in this language, what it opens and who can see it. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Views
Executions ships 50 view(s) on 25 model(s), 12 of them modifying views of other modules. Implementers use this page to see which screens the app changes. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Security
Executions defines 3 group(s), 44 access right(s) and 6 record rule(s). This page states who can see and edit what, in plain language, with the exact rules underneath. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Settings
Executions adds 17 setting(s) to Settings. Each one names the option as it appears on screen, what it does and where the value is stored. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Automations and scheduled actions
Executions runs 1 scheduled action(s), 0 automation rule(s) and 3 server action(s). This page tells you what happens on its own, how often, and what turns it off. Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Reports and email templates
Executions ships 5 printable report(s) and 9 email template(s). Generated from the installed database on 2026-10-14 for version 19.0.1.1.37.
Technical overview
Executions is version 19.0.1.1.37 of the module `j_law_execution`, depending on 3 other module(s). This page is the technical identity card: dependencies, licence, hooks and what the module contributes by kind. Generated from the installed database on 2026-10-14.
Explanation 1
How executions work
What an execution file is, where it comes from, the life of a file and of its procedures, how the money is followed and billed, and who sees what.