Dynamic Ignition Request Workflow
Budget: ₹100 – ₹400 INR
I want to take our paper-based project request form and rebuild it as a fully database-driven workflow. I am happy with Ignition, but I have no strict preference—if another compatible platform will meet the requirements, feel free to propose it.
Users will open a single “Request Project” screen, choose the Development task option (we may add other task types later), and the form should react instantly—showing or hiding the Priority Level field and auto-filling any data we can pull from existing records. They also need the ability to attach images, documents, or videos that stay linked to that exact request entry in the database.
Once a request is submitted, administrators or the designated project owner must be able to reopen it, update any details, add completion comments, and see a full, timestamped revision history for audit purposes.
Deliverables:
• A live Ignition (or equivalent) project with the dynamic “Request Project” screen
• Database schema and bindings for all fields, file uploads, and history tracking
• Admin interface for editing, reopening, and closing requests with automatic logging
• Documentation so we can maintain or extend the workflow ourselves
Acceptance criteria:
The system stores each submission as a unique record, preserves every edit in an immutable log, and supports at least 100 concurrent requests without noticeable lag. All uploaded files must remain retrievable directly from the related request record.
If you have existing Ignition modules, SQL tricks, or API integrations that will accelerate delivery, let me know—speed to production is important, but data integrity comes first.
Users will open a single “Request Project” screen, choose the Development task option (we may add other task types later), and the form should react instantly—showing or hiding the Priority Level field and auto-filling any data we can pull from existing records. They also need the ability to attach images, documents, or videos that stay linked to that exact request entry in the database.
Once a request is submitted, administrators or the designated project owner must be able to reopen it, update any details, add completion comments, and see a full, timestamped revision history for audit purposes.
Deliverables:
• A live Ignition (or equivalent) project with the dynamic “Request Project” screen
• Database schema and bindings for all fields, file uploads, and history tracking
• Admin interface for editing, reopening, and closing requests with automatic logging
• Documentation so we can maintain or extend the workflow ourselves
Acceptance criteria:
The system stores each submission as a unique record, preserves every edit in an immutable log, and supports at least 100 concurrent requests without noticeable lag. All uploaded files must remain retrievable directly from the related request record.
If you have existing Ignition modules, SQL tricks, or API integrations that will accelerate delivery, let me know—speed to production is important, but data integrity comes first.