Download the PHP package codetechnl/laravel-taskbridge-filament-4 without Composer

taskbridge-filament-4

Filament v4 admin panel integration for laravel-taskbridge. Provides a complete UI for managing scheduled jobs, viewing run history, and triggering manual executions — all without touching AWS directly.

Features

• Scheduled Jobs CRUD — create, edit, view, and delete scheduled jobs; changes auto-sync to EventBridge
• One-time job visibility — one-time schedules appear in the table alongside recurring jobs with an "once" badge; records are kept until pruned
• Type filter — filter the table by job type: all, one-time only, or recurring only
• Status dot column — color-coded indicator showing last run status at a glance
• Dynamic constructor argument fields — scalar constructor parameters (bool, int, float, string) render as typed inputs in create/edit forms and in action modals
• Run now / Dry run actions — trigger immediate or simulated execution from the table
• Human-readable cron descriptions — cron expressions are translated to plain English (e.g. 0 8 * * 1 → "Every Monday at 08:00") in the table tooltip and the view page
• Activate / Deactivate — enable or disable a job directly from the view page
• Run Logs — full audit history of every execution with status, duration, trigger type, and structured output
• Dashboard widget — summary of total, active, disabled, and recently-failed jobs

Requirements

• PHP 8.3+
• Laravel 12 or 13
• Filament 4.x
• codetechnl/laravel-taskbridge (installed and configured)

Installation

Register the plugin

Add the plugin to your Filament panel provider:

That's it. The plugin automatically registers the Scheduled Jobs resource, the Run Logs resource, and the TaskBridge stats widget.

Custom theme (required)

Filament v4 uses Tailwind v4, which only compiles utility classes from paths listed in @source directives. Filament's default bundled theme does not scan third-party plugin views, so without a custom theme the TaskBridge widget and some form/picker elements will render unstyled.

1. Generate a Filament theme

This creates resources/css/filament/admin/theme.css and wires it into your Vite config and panel provider (->viteTheme('resources/css/filament/admin/theme.css')).

2. Add the TaskBridge views to the theme

Open resources/css/filament/admin/theme.css and add @source directives for this package's views and PHP files:

The src/**/*.php line is needed because some Tailwind classes are authored as strings in PHP (e.g. extraAttributes(['class' => ...]) inside resources and actions).

3. Rebuild

If you've changed TASKBRIDGE_NAME_PREFIX, moved the package to a different path, or installed under a Composer alias, adjust the @source paths accordingly — they are relative to the theme file.

What you get

Scheduled Jobs resource

A full CRUD interface for your registered jobs:

• Create — select a job class from your registered jobs, configure queue connection, cron expression, retry policy, description, and enable/disable
• Edit — update any settings; saved changes auto-sync to EventBridge
• View — detailed job info (class, schedule, status, description, group) with activate/deactivate header actions and inline run history
• Filters — filter by group, enabled state, last status, and job type (one-time / recurring)

Row actions available on every job:

One-time jobs do not support Run now, Dry run, or Edit — they are read-only once created and self-destruct on EventBridge after firing.

When a job has scalar constructor parameters, Run now and Dry run each render an input field per parameter inside their confirmation modal. Values are type-cast to the declared PHP type before the job is executed.

Bulk actions: Enable selected, Disable selected, Delete selected

Header actions:

Sync, Validate, and Import are grouped under a Tools button (outlined, gray, wrench icon). Schedule Once and Add Job remain as standalone header actions.

Table columns

View page

The view page shows two sections side by side:

• Job — class name, whether the class exists, description, identifier, group
• Schedule — job type badge (One-time / Recurring), cron expression with human-readable description, enabled status

Header actions:

• Activate — enables the job and syncs to EventBridge (visible when disabled, recurring only)
• Deactivate — disables the job and removes from EventBridge (visible when enabled, recurring only)
• Edit — opens the edit form (recurring only)

The Run History relation manager is shown inline at the bottom.

Run Logs resource

A read-only audit log of every job execution. Columns include status, trigger type, duration, jobs dispatched, and structured output.

Filters: job name, identifier, status, trigger type.

Row action: Output — opens a modal with the full structured output when a job reported metadata.

Dashboard widget

A stats overview widget showing:

• Total jobs
• Active (enabled) jobs
• Disabled jobs
• Failed runs in the last 24 hours (shown in red when > 0)

Plugin configuration

All options are set fluently on TaskBridgePlugin::make():

All available options

Navigation nesting: Filament v4 supports flat navigation only (Group → Items). There is no support for nested groups (e.g. System → Task Bridge → Items). Use a single group name.

Authorisation

Pass a policy class to restrict access:

The policy is applied to ScheduledJobResource. Standard Filament policy methods apply: viewAny, create, update, delete, etc.

Creating a job in the UI

Job picker modal

On the Create page, clicking Browse jobs opens a modal that lists all discovered job classes grouped by their group. Use the search box to filter by name or group.

• Compatible jobs (scalar constructor only) — shown as clickable cards. Click one to select it.
• Incompatible jobs (non-scalar constructor parameters) — shown as disabled cards with a red warning that lists the offending parameters. These cannot be scheduled from the UI without code changes.

Once a job is selected, TaskBridge automatically pre-fills:

• Identifier — derived from the class name + name prefix
• Cron expression — from #[SchedulableJob(cron:)] if set, otherwise from HasPredefinedCronExpression::cronExpression() if implemented
• Group — from #[SchedulableJob(group:)] if set, otherwise from HasGroup::group() if implemented, otherwise from the folder name

All of these can be edited before saving. The cron field is required only when the job class does not define a default via the attribute or the interface.

Submitting the form without selecting a job shows a danger notification and highlights the Browse button in red.

The Create page also shows Cancel, Save & create another, and Create actions in the page header, mirroring the bottom form buttons.

Constructor arguments in the create/edit form

The Constructor Arguments section is always visible in the create and edit forms. Its content depends on the selected job:

• No job selected — shows "No job has been selected."
• Job has no parameters — shows "This job doesn't have any arguments."
• Job has scalar parameters — renders a typed input per parameter

The section sits left (2/3 width) in a grid alongside the Retry Policy section (1/3 width).

When a job has scalar constructor parameters, fill in the values in the Constructor Arguments section. They are stored on the job record and baked into the SQS payload every time EventBridge fires the recurring schedule.

The Edit form pre-fills the stored values so you can adjust them at any time. Saving re-syncs the updated payload to EventBridge automatically.

Field types rendered per parameter:

Labels and groups

Without any configuration, TaskBridge derives readable values automatically:

• Label: SendDailyReport → "Send daily report"
• Group: App\Jobs\Reporting\SendDailyReport → "Reporting" (from folder)

Override via attribute

The #[SchedulableJob] attribute is the most concise way to set label, group, and cron together:

Override via interfaces

The interfaces still work and are the right choice when the label or group needs runtime logic:

Priority order: #[SchedulableJob] attribute → interface method → auto-derived default. When both the attribute and an interface are present, the attribute wins.

Viewing structured job output

When a job implements ReportsTaskOutput and uses the HasJobOutput trait, execution metadata is stored on the run record. In the Run Logs table, the Output action opens a modal showing:

• Status badge (Success / Error / Warning / Info)
• Message text
• Key/value metadata table

Example:

Run Logs in the job view

Opening a job's detail page (View) shows the run history inline via the Run History relation manager. Same columns and actions as the standalone Run Logs page.

This package was fully built with Claude Code.