Decide what success looks like at record level.
A useful admin change needs more than a button that looks selected.
Separate a selected batch from a visible page
A user can choose an item, move to another page and choose another item. The selection must follow stable record identities rather than row positions. In BS96, selecting T102 and T105 produces one 70-minute batch even though the two items appear on different pages.
Distinguish browsing changes from scope changes
Pagination changes which rows are visible; a filter changes the working set. This exercise preserves selection when paging and clears it when the eligibility filter changes. Agree the corresponding rule with your users so a bulk action never silently includes forgotten records.
Check the receiving capacity before changing status
The ready queue needs 110 minutes, exceeding the default 90-minute batch capacity. T102 and T105 need 70 minutes and fit. Blocked items cannot enter the batch. The allocation receipt retains the two IDs, minutes, capacity and acting role for the receiving operator.
Make the selected batch visible before it changes records.
BS96 starts with six work items: four ready items need 110 minutes and two blocked items need 55. Select items across two pages, inspect the selected minutes and allocate a batch within its capacity. Changing the filter clears selection; moving between pages retains it. The final receipt identifies the exact items allocated.
Give the programmer a small queue with an unambiguous result.
Try the selection rules and use the platform references to discuss their implementation in your application.
Try cross-page selection before writing the development brief
Work through the ready queue, choose T102 and T105, and preview the 70-minute batch. Try selecting all ready items, changing the filter or using Observer authority to expose the refusal rules.
Open the batch selection demoKeep pagination tied to the filtered data
The CodeIgniter 4 pagination reference describes model pagination, query conditions and multiple paginator groups. Give the programmer the relevant installed-version documentation and the filter state that each pager must preserve.
CodeIgniter primary reference: paginationSpecify the boundary of a bulk database change
CodeIgniter documents commit and rollback behavior for databases and table types that support transactions. Ask how the commissioned bulk action rechecks eligibility and handles a failure before any selected record is accepted as allocated.
CodeIgniter primary reference: database transactionsGive a CRM integration its own acceptance case
If the application also feeds SugarCRM, distinguish queue allocation from account synchronization. Map external identity and field ownership separately, then include both tasks in the development priorities and release plan.
Scope a SugarCRM integration engagementCommission the change from application baseline to operator handover
Use a reproducible task and a named business approver to settle the development scope.
Identify the application and the change owner
Provide the CodeIgniter major version, PHP runtime, database, hosting and source repository arrangements. Name the person authorized to share a development copy and the operator who will accept the change. Explain the existing page, its users and the problem to reproduce.
Specify a finite development request
List the screens, input records, intended action and expected output. Mark integrations and existing permissions that the change touches. Request a quotation covering assessment, programming, review, release assistance and support, with the allocation and acceptance checkpoints written down.
Build the six-item acceptance queue
BS96 uses T101 10 min, T102 25 min, T103 35 min, T104 30 min, T105 45 min and T106 20 min. T103 and T106 are blocked. The remaining four items total 110 minutes. Start from the Ready filter with two rows per page and a 90-minute capacity.
Challenge selection across pages and filters
Select T102 on the first Ready page, then T105 on the second. Inspect the two retained IDs and 70-minute total. Moving back to the first page keeps both selections. Switching to All clears them. A blocked row remains unavailable for selection.
Preview and allocate an eligible batch
Review the selected IDs against capacity before confirming. The Planner role may allocate the prepared batch after acknowledgement; Observer may inspect it. A capacity or selection edit clears preparation. The successful example moves T102 and T105 to Allocated and leaves 40 ready minutes.
Accept the implementation and operating handover
Run the same cases in the commissioned application with its actual authorization and database behavior. Receive the source revision, configuration, acceptance evidence and recovery instructions. Agree the release approver, rollback decision, support period and ownership of the remaining backlog.
Access, development scope and commercial terms
- Provide a small representative dataset, a reproducible user journey and the relevant source revision. Share access through an authorized development environment; agree how confidential data will be replaced for implementation and review.
- Separate a contained feature from continuing maintenance capacity. Ask for the work included, allocation, review points, billing, availability and treatment of additional requests. Confirm source delivery and the responsibilities attached to the engagement.
- Identify authentication, tenant boundaries, uploads, scheduled tasks, exports and external services affected by the change. Supply their existing contracts and permission rules so the quote includes the necessary checks rather than assuming a connector or access path.
Migration, release and support boundaries
- For legacy applications, assess the installed CodeIgniter and PHP versions together. Treat an upgrade or framework migration as an explicit scope decision with its own compatibility and regression checks; agree whether it is required for the requested feature.
- A browser selection is an input to a bulk action. Require the server to authorize each ID, re-read current eligibility and reject an oversized or stale batch. Decide whether a failed item cancels the whole operation or returns a clearly defined partial result.
- Agree the staging copy, database backup owner, release window and rollback criteria. The receiving team needs configuration instructions, log and exception handling, completed acceptance cases and a support contact. Price hosting, licences and future changes explicitly where they are required.
Six records that make a paginated batch change quotable
Use the BS96 work queue to describe what selection means, when it expires and what the operator receives.
| Record | Example inputs | Required output and control |
|---|---|---|
| Application baseline | CodeIgniter/PHP releases, source revision, roles and deployment environment | Match the programming scope and implementation checks to the application that will receive the change. |
| Work item | Stable ID, label, estimated minutes and Ready/Blocked/Allocated status | Use the ID for selection; blocked and allocated items cannot be selected as ready work. |
| Filtered page | Ready or All; two rows per page; explicit page navigation | Retain selected IDs across pages and clear selection when the filter changes. |
| Selected batch | T102 25 min + T105 45 min = 70 min | Preview the complete selection, including records outside the visible page. |
| Capacity and authority | 90 min capacity; Planner role; acknowledgement | Reject an empty, ineligible or oversized selection and clear preparation after edits. |
| Allocation receipt | BS96-B1; T102/T105; 70 of 90 min; Planner | Retain the accepted IDs and minutes; ready work falls from 110 to 40 min without a second allocation on repeat. |
Choose T102 on Ready page 1 and T105 on page 2. The selected total is 70 minutes, leaving 20 minutes within the 90-minute capacity. Preview the batch and confirm as Planner. BS96-B1 records those two IDs, and their status becomes Allocated. T101 and T104 remain ready for 40 minutes; T103 and T106 remain blocked for 55. Selecting all four ready items before allocation would require 110 minutes and must stop at the 90-minute limit.
Ask each development provider to quote the same change.
Compare the actual engagement and receiving evidence, alongside the provider’s published service scope.
| Option | Published focus | Ask in your demo |
|---|---|---|
| Innvonix | Offers part-time, full-time and hourly programming, plus migration and integration work. | Which access, source delivery and bulk-action acceptance cases belong in the agreed scope? |
| Pennine Technolabs | Describes developer levels, project and hourly engagement, modules, migration and API work. | Who will verify cross-page selection, eligibility and capacity with the business approver? |
| Digis | Offers short-term or continuing developer capacity, migration, APIs and application maintenance. | What implementation evidence, release responsibilities and support will the receiving team get? |
Request the same installed-version assessment, finite task and acceptance cases from each provider. Confirm who writes and reviews the change, how source delivery works, and how additional scope is authorized. A capacity agreement should state the time reserved and review arrangement; a feature quote should state the result it covers.
Category reference: CodeIgniter 4 primary reference: filtered model pagination. The platform references inform implementation questions. Use the exercise to agree the selection and allocation behavior your commissioned application must demonstrate.
Turn the next application change into a clear engagement.
Explore Codeblix development services and prepare the source access, records and business approval your project needs.
Explore marketplace development servicesSettle the programming request before the engagement starts
Bring the application baseline, one concrete task and the responsibilities your team needs covered.
What should we provide when requesting CodeIgniter programmers?
Provide the framework and PHP versions, hosting arrangement, authorized source access and a concise description of the first change. Include representative records, affected roles and an acceptance owner. Request the scope, allocation, review points, source handover and support terms in the quotation.
Can we commission one change rather than an ongoing allocation?
Describe the result you want and its boundaries. A contained administrative change can be assessed as a defined task; a continuing backlog needs an allocation and priority process. Agree the commercial arrangement after the codebase and access requirements have been assessed.
Does paging select every record in the results?
No. In BS96, the operator explicitly chooses individual stable IDs. Moving between pages keeps those selections, while switching the filter clears them. The preview identifies all selected items, including any outside the visible page, before allocation is permitted.
Why does selecting the entire ready queue fail at 90 minutes?
The four ready items require 110 minutes. The default capacity is 90, so that batch exceeds it by 20. Selecting T102 25 min and T105 45 min produces 70 minutes and fits. Their successful allocation leaves T101 10 min and T104 30 min ready.
Can an observer or a blocked work item enter an allocation?
Observer can inspect the workspace but cannot allocate a batch. Blocked rows cannot be selected. The Planner role must preview a valid selection and acknowledge it before allocation. The real application should enforce its own authorization and eligibility checks on the server.
What happens if the selection or capacity changes after preview?
The exercise clears preparation and acknowledgement. Preview the current selection again so the operator accepts the IDs and limit that will actually be used. An item placed on hold also leaves the selection and requires a fresh decision.
How will legacy versions, integrations or migration affect the quote?
The installed framework, PHP runtime and existing dependencies determine the assessment. List the integrations and permission boundaries the change touches. Agree any compatibility repair, upgrade, data migration, vendor access or additional testing as explicit work with its own acceptance criteria.
What should our team receive at handover?
Receive the agreed source revision, configuration and deployment instructions, acceptance results and exception-handling steps. Identify the release approver, backup and rollback responsibilities, defect support period and future maintenance arrangement in the engagement.