Eventos Aktum — Real-Time Audit Trail

Eventos Aktum operates as a full-lifecycle event management firm serving both corporate and social markets across Mexico. Their business processes involve managing complex financial workflows across every event engagement.

Key Business Operations

• Client quotation management (Cotizaciones) with multi-line pricing, discounts, and payment terms
• Event lifecycle coordination from initial proposal through post-event reconciliation
• Income and expense tracking per event (Ingresos, Egresos, Flujo reports)
• Advance payment and supplier management (Anticipos, Proveedores)
• Team-based editing of financial records across multiple users and roles
• Post-event financial reconciliation and margin analysis

Services Provided

• Diagnostic audit of existing 73,000+ line Deluge codebase
• Custom Cotizacion_Change_Log form and workflow development
• ChangeLog Dashboard built as a Zoho Creator page with embedded HTML/CSS
• Variable-scope collision resolution and best-practice documentation
• Null-handling hardening across all critical data paths
• Zero-downtime deployment into production workflow

Phase 1 — Week 1

Diagnostic audit of the existing "Edit on Success" workflow (16 processes), identification of safe insertion points for change logging, and development of the Cotizacion_Change_Log form with its triggering workflow.

Phase 2 — Week 2

ChangeLog Dashboard page development with embedded HTML/CSS, variable-scope collision resolution, null-handling hardening, testing, and production deployment.

Cotizaciones (quotations) are the financial backbone of Eventos Aktum's business — they define pricing, line items, expected profit margins, and client commitments. Multiple team members frequently edit these records throughout an event's lifecycle, but there was no systematic way to track changes.

Zero Audit Trail

No record of who modified Cotización fields existed. The "Edit on Success" workflow handled 16 distinct processes including orphan cleanup, financial recalculations, and event synchronization — but none captured change history. Post-event financial reviews were guesswork.

Financial Discrepancies

Unexpected changes to pricing, margins, or payment terms only surfaced during reconciliation — too late to investigate. The team would finish an event and discover final numbers didn't match what was originally quoted, with no way to determine when or why figures changed.

No Operational Dashboards

Management had no centralized view of team activity on quotations — no trending data, no per-user analytics, no way to identify unusual modification patterns. Zoho Creator's native audit trail was too coarse-grained for the business need: management required field-level change tracking with user attribution, aggregated into a visual dashboard.

The agreed statement of work encompassed a two-part solution delivered within a 2-week timeline:

1. Audit the existing "Edit on Success" workflow (16 processes) and identify safe insertion points for change logging
2. Design and develop a Cotizacion_Change_Log form capturing record ID, field name, old value, new value, user, and timestamp
3. Build an HTML/CSS dashboard as a Zoho Creator page with two lookback windows (7-day and 30-day)
4. Implement user activity bar charts, per-cotización change summaries, and detailed log tables
5. Resolve variable-scope collisions inherent to Deluge page scripts
6. Add null-handling guards for empty-string edge cases from ifnull() casts
7. Deploy with zero downtime — no disruption to existing 16 workflow processes

Technology Stack

Architecture: Two-Part Solution

Part 1 — Change Logging Engine: A dedicated Cotizacion_Change_Log form captures every field-level change to Cotización records. The logging workflow is triggered automatically on every save, comparing current values against stored originals and writing a record for each detected change. This was carefully inserted into the existing "Edit on Success" script to avoid disrupting the 16 processes already running on each save.

Part 2 — ChangeLog Dashboard: An HTML dashboard built as a Zoho Creator page using Deluge page scripts with embedded HTML/CSS. The dashboard aggregates change data across two time horizons (7-day and 30-day) and presents it through user activity bar charts, per-cotización summaries, and detailed log tables.

Key Technical Decisions

Variable-Scope Collision Resolution: All variables in a Zoho Creator page script share a single scope. The weekly and monthly dashboard sections initially collided — loop variables from the 7-day section were overwritten by the 30-day section. This was resolved by prefixing all monthly-section variables with m (e.g., mCotID, mUserName), a pattern now documented as a best practice for all future Creator pages.

Null-Handling Hardening: Some Cotización IDs came through as empty strings from ifnull() casts, which would pass != null checks but crash on downstream operations. Guards using != "" were added to all critical paths.

This project was intentionally self-contained within the Zoho Creator ecosystem:

No external APIs or third-party services were required beyond the icon CDN, keeping the solution lightweight and maintainable.

The ChangeLog Dashboard successfully achieved all project objectives and is now in active daily use by the operations team:

Performance Metrics

Key Achievements

• Complete Financial Transparency: Every modification to every Cotización record is now visible — who changed it, what field was affected, old and new values, and exactly when
• Real-Time Accountability: Dashboard became a daily operational tool for the management team
• Eliminated Disputes: Financial reconciliation disputes between team members resolved by audit evidence
• Pattern Detection: Management can identify unusual modification patterns and workload distribution

Operational Efficiency

• Eliminated post-event "who changed what?" investigations — answers now available in seconds
• Reduced financial reconciliation time by providing complete change audit trails
• Management gained instant visibility into team modification activity across all quotations

Financial Accuracy

• Zero unexplained financial discrepancies since dashboard launch
• Price changes, discount applications, and payment term modifications all tracked with full attribution
• Proactive anomaly detection through per-user and per-cotización activity analysis

Team Accountability

• Transparent modification history builds trust across team members
• User activity charts provide objective workload distribution data
• Change log serves as evidence base for training and process improvement

The implementation also produced two reusable best practices: the m-prefix pattern for avoiding variable-scope collisions in Deluge page scripts, and the != "" guard pattern for handling ifnull() empty-string edge cases. Both are now standard practice for all Creator Scripts projects.