ExpedienteController

Overview

The ExpedienteController manages conciliation expedientes (case files) in the Sistema de Abogados application. It handles expediente creation, updates, deletion, search functionality, and relationship management with subject matters (submaterias), invited parties, and conciliators. Namespace: App\Http\Controllers Extends: Controller

Dependencies

The controller uses the following models:

Expedientes - Main expediente model
Cliente - Client model
Submaterias - Subject matter model
InvitadoConciliacion - Invited party model
Conciliador - Conciliator model
Expediente_has_submateria - Expediente-Submateria pivot model
expediente_has_invitado - Expediente-Invited party pivot model
Expediente_has_conciliador - Expediente-Conciliator pivot model
ExpedienteDocumento - Expediente document model

Methods

index()

Lists all expedientes with pagination and search functionality. Purpose: Display a paginated list of expedientes with optional search filtering Parameters: None (uses request('search') for search query) Returns: View conciliacion.expediente.index with expedientes, clients, and subject matters Response Data:

expedientes

Collection

Paginated collection of expedientes (5 per page)

clientes

Collection

All clients for filtering/assignment

ex_submaterias

Collection

All expediente-submateria relationships

Code Example:

public function index()
{
    $expedientes = Expedientes::search(request('search'))->paginate(5);
    $clientes = Cliente::all();
    $ex_submaterias = Expediente_has_submateria::all();
    return view('conciliacion.expediente.index', 
        compact('expedientes','clientes','ex_submaterias'));
}

Route: conciliacion.expediente.index

create()

Displays the expediente creation form. Purpose: Show the form for creating a new expediente Parameters: None Returns: View conciliacion.expediente.create with clients Response Data:

clientes

Collection

All available clients to assign to the expediente

Code Example:

public function create()
{
    $clientes = Cliente::all();
    return view('conciliacion.expediente.create', compact('clientes'));
}

Route: conciliacion.expediente.create

store()

Creates a new expediente with validation. Purpose: Store a new expediente in the database Request Parameters:

n_expediente

string

required

Expediente number or identifier

fecha_inicio

date

required

Expediente start date

fecha_final

date

Expediente end date (optional)

descripcion

text

Expediente description (optional)

estado

string

required

Expediente status

id_cliente

integer

required

Client ID associated with the expediente

Validation Rules:

[
    'n_expediente' => 'required', 
    'fecha_inicio' => 'required',
    'fecha_final' => 'nullable',
    'descripcion' => 'nullable',
    'estado' => 'required',
    'id_cliente' => 'required'
]

Returns: Redirect to conciliacion.expediente.index with success message Success Message: “Expediente registrado correctamente.” Code Example:

public function store(Request $request)
{
    $validated = $request->validate([
        'n_expediente' => 'required', 
        'fecha_inicio' => 'required',
        'fecha_final' => 'nullable',
        'descripcion' => 'nullable',
        'estado' => 'required',
        'id_cliente' => 'required'
    ]);
    Expedientes::create($validated);
    return to_route('conciliacion.expediente.index')
        ->with('message', 'Expediente registrado correctamente.');
}

Route: conciliacion.expediente.store

show()

Displays detailed information for a specific expediente. Purpose: Show complete expediente details including subject matters, invited parties, conciliators, and documents Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Returns: View conciliacion.expediente.expediente with expediente data and related entities Response Data:

expediente

Expedientes

The expediente instance

submaterias

Collection

All available subject matters

invitados

Collection

All invited parties

conciliadores

Collection

All conciliators

ex_invitados

Collection

Invited parties assigned to expedientes

ex_submaterias

Collection

Subject matters assigned to expedientes

ex_conciliadores

Collection

Conciliators assigned to expedientes

ex_documentos

Collection

Documents associated with expedientes

Code Example:

public function show(Expedientes $expediente)
{
    $submaterias = Submaterias::all();
    $invitados = InvitadoConciliacion::all();
    $conciliadores = Conciliador::all();
    $ex_invitados = expediente_has_invitado::all();
    $ex_submaterias = Expediente_has_submateria::all();
    $ex_conciliadores = Expediente_has_conciliador::all();
    $ex_documentos = ExpedienteDocumento::all();
    return view('conciliacion.expediente.expediente', 
        compact('expediente','submaterias','invitados',
                'conciliadores','ex_invitados','ex_submaterias',
                'ex_documentos','ex_conciliadores'));
}

Route: conciliacion.expediente.show

edit()

Displays the expediente edit form. Purpose: Show the form for editing an existing expediente Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Returns: View conciliacion.expediente.edit with expediente and clients Response Data:

expediente

Expedientes

The expediente instance to edit

clientes

Collection

All available clients

Code Example:

public function edit(Expedientes $expediente)
{
    $clientes = Cliente::all();
    return view('conciliacion.expediente.edit', 
        compact('expediente','clientes'));
}

Route: conciliacion.expediente.edit

update()

Updates an existing expediente with validation. Purpose: Update expediente information in the database Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Request Parameters:

n_expediente

string

required

Expediente number or identifier

fecha_inicio

date

required

Expediente start date

fecha_final

date

Expediente end date (optional)

descripcion

text

Expediente description (optional)

estado

string

required

Expediente status

id_cliente

integer

Client ID (optional on update)

Validation Rules:

[
    'n_expediente' => 'required', 
    'fecha_inicio' => 'required',
    'fecha_final' => 'nullable',
    'descripcion' => 'nullable',
    'estado' => 'required',
    'id_cliente' => 'nullable'
]

Returns: Redirect to conciliacion.expediente.index with success message Success Message: “Expediente Actualisado correctamente.” Code Example:

public function update(Request $request, Expedientes $expediente)
{
    $validated = $request->validate([
        'n_expediente' => 'required', 
        'fecha_inicio' => 'required',
        'fecha_final' => 'nullable',
        'descripcion' => 'nullable',
        'estado' => 'required',
        'id_cliente' => 'nullable'
    ]);
    $expediente->update($validated);
    return to_route('conciliacion.expediente.index')
        ->with('message', 'Expediente Actualisado correctamente.');
}

Route: conciliacion.expediente.update

destroy()

Deletes an expediente from the database. Purpose: Remove an expediente with foreign key constraint handling Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Returns:

Success: Redirect to conciliacion.expediente.index with success message
Error: Back with alert message if constraints exist

Success Message: “Expediente eliminado correctamente.” Error Message: “No puede eliminar! Tiene asignado recursos.” Code Example:

public function destroy(Expedientes $expediente)
{
    try{
        $expediente->delete();
        return to_route('conciliacion.expediente.index')
            ->with('messagedestroy', 'Expediente eliminado correctamente.');
    }catch(\Exception $e){
        return back()->with('messageAlert', 
            'No puede eliminar! Tiene asignado recursos.');
    }
}

Route: conciliacion.expediente.destroy Notes:

Uses try-catch to handle foreign key constraint violations
Related entities must be removed before deleting the expediente

assignSubmateria()

Assigns a subject matter (submateria) to an expediente. Purpose: Create a relationship between an expediente and a subject matter Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Request Parameters:

id_submateria

integer

required

Subject matter ID to assign

Returns: Back to previous page with success message Success Message: “Submateria asignado.” Code Example:

public function assignSubmateria(Request $request, Expedientes $expediente)
{
    $validated = $request->input();
    $validated['id_expediente'] = $expediente->id;
    Expediente_has_submateria::create($validated);
    return back()->with('message', 'Submateria asignado.');
}

Route: Custom route for assigning subject matter Notes:

Automatically sets id_expediente from the route parameter
Creates a pivot table entry

removeSubmateria()

Removes a subject matter assignment from an expediente. Purpose: Delete the relationship between an expediente and a subject matter Parameters:

ex_submateria

Expediente_has_submateria

required

Expediente-submateria pivot model instance (route model binding)

Returns: Back to previous page with success message Success Message: “Submateria Removido.” Code Example:

public function removeSubmateria(Expediente_has_submateria $ex_submateria)
{
    $ex_submateria->delete();
    return back()->with('messagedestroy', 'Submateria Removido.');
}

Route: Custom route for removing subject matter

assignInvitado()

Assigns an invited party to an expediente. Purpose: Create a relationship between an expediente and an invited party Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Request Parameters:

id_invitado

integer

required

Invited party ID to assign

Returns: Back to previous page with success message Success Message: “invitado asignado.” Code Example:

public function assignInvitado(Request $request, Expedientes $expediente)
{
    $validated = $request->input();
    $validated['id_expediente'] = $expediente->id;
    expediente_has_invitado::create($validated);
    return back()->with('message', 'invitado asignado.');
}

Route: Custom route for assigning invited party Notes:

Automatically sets id_expediente from the route parameter
Creates a pivot table entry

removeInvitado()

Removes an invited party assignment from an expediente. Purpose: Delete the relationship between an expediente and an invited party Parameters:

ex_invitado

expediente_has_invitado

required

Expediente-invited party pivot model instance (route model binding)

Returns: Back to previous page with success message Success Message: “invitado Removido.” Code Example:

public function removeInvitado(expediente_has_invitado $ex_invitado)
{
    $ex_invitado->delete();
    return back()->with('messagedestroy', 'invitado Removido.');
}

Route: Custom route for removing invited party

assignConciliador()

Assigns a conciliator to an expediente. Purpose: Create a relationship between an expediente and a conciliator Parameters:

expediente

Expedientes

required

Expediente model instance (route model binding)

Request Parameters:

id_conciliador

integer

required

Conciliator ID to assign

Returns: Back to previous page with success message Success Message: “Conciliador asignado.” Code Example:

public function assignConciliador(Request $request, Expedientes $expediente)
{
    $validated = $request->input();
    $validated['id_expediente'] = $expediente->id;
    Expediente_has_conciliador::create($validated);
    return back()->with('message', 'Conciliador asignado.');
}

Route: Custom route for assigning conciliator Notes:

Automatically sets id_expediente from the route parameter
Creates a pivot table entry

removeConciliador()

Removes a conciliator assignment from an expediente. Purpose: Delete the relationship between an expediente and a conciliator Parameters:

ex_conciliador

Expediente_has_conciliador

required

Expediente-conciliator pivot model instance (route model binding)

Returns: Back to previous page with success message Success Message: “Conciliador Removido.” Code Example:

public function removeConciliador(Expediente_has_conciliador $ex_conciliador)
{
    $ex_conciliador->delete();
    return back()->with('messagedestroy', 'Conciliador Removido.');
}

Route: Custom route for removing conciliator

Usage Examples

Creating a New Expediente

// POST /conciliacion/expedientes
$data = [
    'n_expediente' => 'EXP-2026-001',
    'fecha_inicio' => '2026-03-10',
    'fecha_final' => null,
    'descripcion' => 'Proceso de conciliación extrajudicial',
    'estado' => 'En Proceso',
    'id_cliente' => 7
];

Updating an Expediente

// PUT /conciliacion/expedientes/{expediente}
$data = [
    'n_expediente' => 'EXP-2026-001',
    'fecha_inicio' => '2026-03-10',
    'fecha_final' => '2026-06-15',
    'descripcion' => 'Conciliación finalizada exitosamente',
    'estado' => 'Concluido',
    'id_cliente' => 7
];

Assigning a Subject Matter

// POST /conciliacion/expedientes/{expediente}/assign-submateria
$data = [
    'id_submateria' => 5
];

Assigning an Invited Party

// POST /conciliacion/expedientes/{expediente}/assign-invitado
$data = [
    'id_invitado' => 12
];

Assigning a Conciliator

// POST /conciliacion/expedientes/{expediente}/assign-conciliador
$data = [
    'id_conciliador' => 3
];

Searching Expedientes

// GET /conciliacion/expedientes?search=EXP-2026
// The search parameter is automatically handled by the Expedientes model

Error Handling

Deletion Constraints

When attempting to delete an expediente with related records:

// If foreign key constraints or assigned resources exist
return back()->with('messageAlert', 
    'No puede eliminar! Tiene asignado recursos.');

Validation Errors

Laravel’s validation will automatically return error messages for:

Missing required fields (n_expediente, fecha_inicio, estado, id_cliente)
Invalid data formats
Type mismatches

Expedientes - Main expediente model at /home/daytona/workspace/source/app/Models/Expedientes.php
Cliente - Client model
Submaterias - Subject matter categorization
InvitadoConciliacion - Parties invited to conciliation
Conciliador - Conciliators assigned to cases
ExpedienteDocumento - Documents attached to expedientes

Workflow

Create Expediente - Start with basic information and client assignment
Assign Subject Matters - Categorize the expediente by legal subject
Assign Invited Parties - Add all parties involved in conciliation
Assign Conciliator - Designate the mediator for the process
Upload Documents - Attach relevant documentation
Update Status - Track progress through various states
Conclude or Archive - Mark as completed when resolved

Models

Controllers

Routes

Overview

Dependencies

Methods

index()

create()

store()

show()

edit()

update()

destroy()

assignSubmateria()

removeSubmateria()

assignInvitado()

removeInvitado()

assignConciliador()

removeConciliador()

Usage Examples

Creating a New Expediente

Updating an Expediente

Assigning a Subject Matter

Assigning an Invited Party

Assigning a Conciliator

Searching Expedientes

Error Handling

Deletion Constraints

Validation Errors

Workflow

Build docs developers (and LLMs) love

Models

Controllers

Routes

​Overview

​Dependencies

​Methods

​index()

​create()

​store()

​show()

​edit()

​update()

​destroy()

​assignSubmateria()

​removeSubmateria()

​assignInvitado()

​removeInvitado()

​assignConciliador()

​removeConciliador()

​Usage Examples

​Creating a New Expediente

​Updating an Expediente

​Assigning a Subject Matter

​Assigning an Invited Party

​Assigning a Conciliator

​Searching Expedientes

​Error Handling

​Deletion Constraints

​Validation Errors

​Related Models

​Workflow

Build docs developers (and LLMs) love

Overview

Dependencies

Methods

index()

create()

store()

show()

edit()

update()

destroy()

assignSubmateria()

removeSubmateria()

assignInvitado()

removeInvitado()

assignConciliador()

removeConciliador()

Usage Examples

Creating a New Expediente

Updating an Expediente

Assigning a Subject Matter

Assigning an Invited Party

Assigning a Conciliator

Searching Expedientes

Error Handling

Deletion Constraints

Validation Errors

Related Models

Workflow