
Portal Bulk Actions: Preview the Scope and Report Every Outcome
Build bulk portal workflows with explicit selection scope, per-record authorization, clear partial-failure reports, and retries that avoid duplicate effects.
Custom Portals
Design portal list reordering with non-drag controls, stable item identities, clear save feedback, and conflict handling that preserves the intended shared order.

LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.
A coordinator rearranges a portal checklist by dragging an item upward. The animation succeeds, but refreshing the page returns the old order. Another user cannot perform the drag at all on a small touchscreen. A third person changes the list at the same time and unknowingly overwrites the coordinator’s arrangement. These are different failures within one apparently simple feature.
Reliable reordering needs three things: an accessible way to express the move, a clear definition of the order being changed, and a persistence protocol that confirms the result. Start by deciding what ordering means for the product. A personal display preference and a shared processing priority have different consequences, permissions, and review needs. The controls should make that distinction understandable.
Specify whether the list order belongs to one user, a project, or the whole organization. Decide whether it affects only presentation or also execution. Moving a task to the top of a personal view should not quietly change a worker’s processing priority. If the order controls operational behavior, explain that relationship before the user saves and apply the relevant authorization rules on the server.
For a shared onboarding checklist, the order may describe the recommended reading sequence without enforcing completion dependencies. For a dispatch queue, priority may have operational consequences. Document those differences. Do not use a generic reorder endpoint for both without a clear model of what is changing. Support staff should be able to explain the effect of a move using the product’s own language.
W3C’s guidance on dragging movements explains that applicable dragging functionality needs a single-pointer alternative that does not require dragging. It also distinguishes this from keyboard accessibility. A keyboard-only shortcut does not automatically solve the touch user’s difficulty. Provide controls such as Move up, Move down, or a destination chooser that users can activate by ordinary clicks or taps.
For a short checklist, adjacent move buttons may be sufficient. For a long list, a Move before item control can avoid dozens of repeated actions. Give controls accessible names that identify the item and action. Keep their touch targets usable and their placement predictable. The alternative should perform the same meaningful task as dragging, rather than offering a reduced feature that cannot reach all valid positions.
After a keyboard or button-based move, keep focus associated with the item or control the user was operating. Do not send focus to the beginning of the page every time the list updates. Provide a concise status message describing the item’s new position when useful. The visible order, keyboard sequence, and accessible reading order should agree.
At the first and last positions, make unavailable actions understandable. If Move up is disabled for the first item, avoid a state change that makes the focused control disappear unexpectedly. Test repeated moves and moving an item across the visible viewport. A user should be able to continue operating the same item without repeatedly searching for it after each update.
Identify records by stable IDs. A row index is a position in one view at one moment, not the identity of the item. If the client says move row three while another item is inserted, the server may move the wrong record. Express the intended move using the item identity and a defined destination, together with the version or context needed to validate it.
For example, a command can mean move checklist item A before item D in checklist C at version V. The server confirms that both items belong to the authorized checklist and that the requested move is still valid. The database representation might use explicit ranks or another ordering scheme, but that implementation detail should not leak into confusing customer-facing labels.
Reordering a filtered subset is ambiguous unless the product defines what happens to hidden items. Moving a visible item from third to first could mean first among matching items or first in the entire list. Pagination creates a similar question. Write an explicit rule and show enough context for the user to predict the result.
One practical choice is to allow shared ordering only in a dedicated full-list view, while filters remain available for ordinary browsing. Another is to offer a destination chooser that includes the relevant items beyond the current page. Either approach can work if its result is clear. Avoid persisting a partial visible array as the entire shared list, which can accidentally omit hidden records.
Choose between explicit saving and immediate persistence. With explicit saving, show that the new arrangement is a draft and offer Save and Cancel. With immediate persistence, indicate when a move is pending, confirmed, or failed. An optimistic animation can make the interface responsive, but it is not proof that the server accepted the change. Provide recovery if the request fails.
Consider a failed save after several moves. Preserve the proposed arrangement long enough for the user to understand the problem and retry or discard it. Do not show a saved banner merely because the animation completed. If the response is uncertain, read the current authoritative order and reconcile it with the operation identity or version before issuing another mutation blindly.
Two authorized users can reorder the same shared list at once. A simple last-write-wins replacement may silently discard one person’s work. Use a version check or another concurrency approach appropriate to the product. If the underlying list changed, explain the conflict and show the current arrangement. Give the user a way to reapply the intended move after reviewing that change.
A relative move can sometimes be applied safely despite unrelated changes, but define those conditions explicitly. What if the destination item was removed? What if the moved item is now locked or archived? The server should validate membership, permissions, and current state within the operation. Do not rely on the client having loaded a valid list earlier in the session.
An Undo action should reverse the relevant move without unexpectedly overwriting later work by someone else. Record enough context to determine whether the reversal is still valid. If it is no longer safe, explain why and offer a review of the current order. A shared list is not a private local text editor where every prior state can be restored without considering other actors.
For operational ordering, record the actor, list, move, result, and time where the product requires an audit trail. Avoid logging only the final numeric ranks without a readable relationship to the intended action. AI can suggest a useful sequence for a checklist, but present that sequence for review and save it through the same permission and conflict checks as a manual arrangement.
Test mouse dragging, touch alternatives, keyboard operation, and assistive technology. Include a long list, narrow screen, filtered view, repeated moves, failed save, reload, and concurrent editing. Verify the persisted order from a second authorized session. Check that unauthorized moves are rejected and that unrelated records remain in the list. These scenarios test the actual promise of the feature, beyond a successful animation.
Portal reordering becomes dependable when users can express a move clearly and verify that it was saved. Define the scope, provide alternatives to dragging, use stable identities, and handle filtering and concurrency explicitly. Consistent focus, status feedback, and careful undo behavior keep the interaction understandable even when the shared list changes around the user.
LET’S BUILD SOMETHING USEFUL
Talk to Ataraxy Developers about your website, app, or custom software.