This website requires JavaScript.
Explore
Help
Sign In
AS1024
/
itflow
Watch
1
Star
0
Fork
0
You've already forked itflow
mirror of
https://github.com/itflow-org/itflow
synced
2026-11-18 02:17:27 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
Files
de9544ffc66a7ec6b06e98597bee911f91e1b521
itflow
/
cron
History
johnnyq
de9544ffc6
Recurring tickets book each ticket for its run day at a set time, remote or onsite, and can be raised a number of days ahead of the run or of the 1st of its month; recurring invoices can be made a number of days ahead, due on their date plus the client's terms or on their date; database 3.7.7 adds the columns; 26.11.9 changelog entries
2026-11-17 17:56:00 -05:00
..
custom
Copy crons from /scripts to /cron, added custom directories for api/v1/, /setup, /cron and /scripts
2025-10-07 13:55:54 -04:00
includes
Fix Cron Schedule and new directory includes created inside cron for the cron lock
2026-07-30 17:06:07 -04:00
.htaccess
Add .htaccess in cron
2025-10-08 17:25:03 -04:00
ai_triage.php
AI stage 2: AI on tickets - Draft button in the ticket reply editor that writes the next reply from the ticket or from typed notes, for the reply type picked, leaving internal notes out of anything the client reads, with undo; richer ticket summary from the whole ticket with Save as a note, Copy and Again; Triage with AI suggesting a category and priority shown on the ticket to apply in part or dismiss, logged in the ticket history; automatic triage of new email, portal and API tickets with a Settings > Tickets mode of off, suggest or fill in and a new AI Triage cron job; Write up as a document drafting a knowledge base document from a ticket into the New Document form for the client or the company's own client record, linked to the ticket's asset, with passwords and keys left out as [removed]; new ticket features shown by name in AI Usage; database 3.3.9 adds config_ticket_ai_triage and ai_ticket_triage
2026-10-20 18:58:14 -04:00
app_update.php
Make Maintenance > Update easier to follow - it opens with where the install stands (up to date, an update available, updating, the database still to finish, checking) and the one button for it, Update ITFlow in place of Queue Update, with what's new below it (the release notes between this install and the latest, read from the changelog by the update check, developer notes and commits folded away), what to do first including the ITFlow files changed on this install that updating would put back, the update shown running with the page refreshing itself and then when it finished or what stopped it, and this install's version, branch, database, commit, last check, last update, cron and the command to update from a shell alongside; database 3.5.7 adds settings.config_update_details, written by cron/update_check.php through the new updateCheckDetails(), updateChangelogSections() and updateChangelogHtml() render the release notes escaped, cron/app_update.php asks for a fresh check after an update, changelog updated
2026-11-05 14:25:19 -05:00
backup.php
More sweeps to replace select * with actual returned column names dramatically reduces php memory usage and speeds up processing dramatically especially in the crons since they run all the time
2026-08-06 13:10:23 -04:00
certificate_refresher.php
Quieter App Logs from cron: the email parser no longer logs a run summary every minute mail comes in or is left in the inbox, and echoes its counts and time instead; with no IMAP or SMTP provider set up the email parser and mail queue stop with a reason Maintenance Cron shows instead of an App Logs entry every minute; the mail queue, ticket SLA monitor, domain refresher and certificate refresher stop without an App Logs error while cron is switched off, as the email parser already did; 26.11.9 changelog entries
2026-11-16 17:38:51 -05:00
cron.php
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00
demo_reset.php
Add demo mode for a public demo like demo.itflow.org - $config_demo_mode = true; in config.php puts one-click sign-in buttons for Admin, Technician, Accountant and a client portal contact on the sign-in page and a demo notice on every page, and the new Demo Reset cron job rebuilds the demo nightly at 2:00 AM from db.sql with all starter content, the demo clients and the demo accounts, empties uploads except the logo and signs everyone out, keeping the company details, timezone and cron schedules; visitors can try everything except users and roles, their own sign-in details, mail, payment, AI and texting settings, API keys, backups, updates, cron, log forwarding, company, module and portal settings, custom links, starter content and share links, Debug is closed, guest links open only for someone signed in, queued email is cancelled with the reason, no sign-in alert emails are sent, certificate checks reach only public addresses on port 443, and the domain and certificate refreshers are left out; new functions/demo.php and cron/demo_reset.php, no database change, changelog, CONTRIBUTING and README updated
2026-11-06 17:46:40 -05:00
domain_refresher.php
Quieter App Logs from cron: the email parser no longer logs a run summary every minute mail comes in or is left in the inbox, and echoes its counts and time instead; with no IMAP or SMTP provider set up the email parser and mail queue stop with a reason Maintenance Cron shows instead of an App Logs entry every minute; the mail queue, ticket SLA monitor, domain refresher and certificate refresher stop without an App Logs error while cron is switched off, as the email parser already did; 26.11.9 changelog entries
2026-11-16 17:38:51 -05:00
mail_queue.php
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00
managed_instances.php
Set up a hosted instance and connect it in one command - Add Instance takes the address it will have, and the instance page gives a ready setup_cli command with the connection code and the client's company name, address, phone, website, tax ID, currency and primary contact as the first admin; setup_cli gains --manager-code and --manager-required (connects after setup, writes the managed line to config.php, exits 3 if it set up but could not connect), --ask-missing, --generate-password, --json and ITFLOW_SETUP_ environment variables for any option, and shows the cron job as a crontab line and for a hosting panel with the full PHP path; Managed Instances shows a connected instance whose cron has never run as Waiting for its cron job with the command to add, and the Managed Instances job says so in its notification; new managedSetupCommand(), the cron command in the instance report and the waiting state in managedInstanceHealth(), changelog updated
2026-11-06 14:29:27 -05:00
manager_checkin.php
Make managed mode off by default and turned on per side in config.php - $config_enable_managed_instances = true; adds Admin > Managed Instances, the api/managed endpoints and the Managed Instances cron job, and $config_enable_managed_by = true; (or $config_manager_required = true;) adds Admin > Managed By, the Manager Check-in cron job and support sign-in; with a side off its menu entry, pages, modal, post handler and cron job are gone, the manager endpoints answer 503 so instances keep their connection and retry, a connected instance stops checking in and its locks, read-only and suspended lift while its connection is kept, any open support session is ended, and the support user still takes no seat; new managerEnabled(), managedEnabled() and managedConnected(), the cron registry and health check leave out the jobs of a side that is off, changelog updated
2026-11-05 20:17:42 -05:00
nightly_tasks.php
Recurring tickets book each ticket for its run day at a set time, remote or onsite, and can be raised a number of days ahead of the run or of the 1st of its month; recurring invoices can be made a number of days ahead, due on their date plus the client's terms or on their date; database 3.7.7 adds the columns; 26.11.9 changelog entries
2026-11-17 17:56:00 -05:00
payment_provider_fees.php
Record Stripe fees every 15 minutes instead of once a night - a new Payment Provider Fees cron job runs the fee recorder that Nightly Tasks used to, Nightly Tasks no longer does, the recorder holds a lock so the job and Record fees now can't both record the same fee, and the payment provider screens no longer say fees are recorded each night
2026-11-04 14:38:32 -05:00
rmm_alerts.php
Add RMM alerts opening tickets: a provider's Edit picks which alerts open tickets (errors, errors and warnings, or every alert) and their ticket category, and the new RMM Alerts cron job looks every minute - a new alert on a device of a linked client opens a ticket on its client and asset with priority by severity, the same alert again goes on its open ticket and reopens it if resolved, and a cleared alert notes and resolves its ticket unless someone has written on it, it was moved to another status or another of its alerts is still open; the first look after turning alerts on, or the provider back on, takes open alerts as known, as does an alert raised before its device came into ITFlow; Tactical alerts read from PATCH /alerts/ and GET /alerts/id/ with no setup in Tactical; open alerts and their tickets on the asset's RMM card, an Alerts column on the providers list, the RMM ticket source on the ticket page and list, and the new-ticket address email; database 3.6.8 adds the alert columns to rmm_providers and the rmm_alerts table; 26.11.9 changelog entries
2026-11-13 18:33:38 -05:00
rmm_sync.php
Add RMM Providers under Admin > Integrations to bring devices in from an RMM as assets, with Tactical RMM as the first kind: a providers list (search, sort, add, edit, test, sync now, turn off and on, delete), a Clients page per provider to link its clients to ITFlow clients with same-name suggestions, devices matched to existing assets by serial or unique name or made as new ones, each asset field following the RMM until it is edited in ITFlow, removed devices marked and returned ones picked up, deleted assets left out until Bring back, a card per RMM device on the asset page with online state, last seen, signed-in user, reboot, patches and failing checks, Take Control and dashboard links, the state on the quick look, a status dot and RMM filter on the assets list, and the RMM Sync cron job every 15 minutes across every provider that is on; shared engine in functions/rmm.php and the Tactical adapter in functions/rmm_tactical.php so another RMM is one file and one registry line; database 3.6.7 adds rmm_providers, rmm_clients and rmm_devices; demo mode locks the new pages and handlers; 26.11.9 changelog entries
2026-11-13 18:13:58 -05:00
sms_queue.php
Add Skyetel text messaging with two-way ticket texting, text to ticket for contacts, Text reply on tickets, a Texts inbox for unmatched numbers, verification codes and spam (codes masked, limited to credential access, every reveal audited, wiped after a day), STOP/START/HELP handling, a text log with retry and cancel in Maintenance > Text Messages, the Text Messages cron job, and texts to clients about their tickets, visits, visit reminders and invoices with per-contact opt-in from the contact, by text or in the client portal, quiet hours, and new settings in Tickets and Notifications (database 3.6.0 and 3.6.1)
2026-11-06 00:08:10 -05:00
ticket_email_parser.php
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00
ticket_sla.php
Quieter App Logs from cron: the email parser no longer logs a run summary every minute mail comes in or is left in the inbox, and echoes its counts and time instead; with no IMAP or SMTP provider set up the email parser and mail queue stop with a reason Maintenance Cron shows instead of an App Logs entry every minute; the mail queue, ticket SLA monitor, domain refresher and certificate refresher stop without an App Logs error while cron is switched off, as the email parser already did; 26.11.9 changelog entries
2026-11-16 17:38:51 -05:00
update_check.php
Robustness: lists take page 1 at least and an open end date, portal sessions go to the portal from the main address, custom page forms no longer load a missing post/ai.php, cron jobs that stop with an error code show as Failed with the parser saying what the mail server answered, the mail queue keeps a refreshed OAuth token for the rest of the run, the update check keeps the newest 100 commits and counts them all, restore_cli works on a database with no settings yet, the API reads a non-JSON body as no fields and clamps limit and offset, API client delete removes the client's uploads, contact anonymizing redacts stored values longest first, the asset transfer log names the asset, the client duplicate check escapes wildcards, and Access Modules drops its dead buttons and sorts only on its own columns; 26.11.9 changelog entries
2026-11-17 16:15:23 -05:00