Self-Service Table View Now Available for End Users

Self-Service Table View Now Available for End Users

We're excited to announce that Xurrent's powerful table view functionality has been extended to self-service users. This enhancement brings the same advanced data management capabilities that specialists have been enjoying since 2025 directly to end users, transforming how they interact with their inbox and request pages.

The new table view option provides self-service users with unprecedented control over their request management experience. Users can now access this feature through a convenient table icon located in the inbox and request headers, while the familiar default list view remains unchanged for those who prefer it.

‍

What Self-Service Users Can Now Do

Once a user switches to table view, they gain access to powerful features that make request management more efficient:

• Custom columns: Personalize which information is displayed through the ellipsis menu, showing only the data that matters most to you
• Advanced sorting: Click column arrows to sort requests by any field, making it easy to prioritize and organize your workload
• Smart filtering: Use the header icon to filter requests based on specific criteria, quickly finding exactly what you need
• Persistent preferences: Your view selection is automatically saved between sessions, so you don't have to reconfigure each time you log in

Users can easily toggle back to the traditional list view using the list icon in the header, providing flexibility based on personal preference or specific tasks.

Coming Soon

This is just the beginning of enhanced self-service capabilities. Xurrent will soon be rolling out additional improvements including personal views for self-service users and table view support on the homepage, further empowering end users to work more efficiently.

Additional Platform Updates

Universal Data Connector (UDC) V2

UDC V2 is now available in the Xurrent QA environment as part of a required technical refactor. While this release introduces no functional changes to the existing UDC integration, it's important to note that all future enhancements, fixes, and updates will be delivered exclusively through UDC V2. The connector continues to support seamless integration between Xurrent data and Microsoft SQL databases for aggregation, reporting, and external system integration.

To migrate to UDC V2 in your QA environment, simply uninstall the existing UDC app, install the UDC V2 integration from the marketplace, and proceed with your standard validation and testing procedures.

Workflows: Related Request Restriction

Xurrent now offers enhanced protection for workflow-driven processes with a new configuration option that restricts who can change the status of requests linked to a workflow. When enabled, only the Workflow Manager can update request status, preventing premature or unintended status changes by other specialists.

This feature adds a new configuration option in workflow templates (also applicable to workflows without templates) that removes the "Complete" option from the status dropdown for specialists when active. All other applicable status options remain available, ensuring requests move through their lifecycle only when intended by the workflow. This update helps teams maintain consistent, controlled workflows while reducing the risk of accidental status changes that could disrupt carefully designed processes.

Retention Policy for Reservations

Customers now have greater control over reservation lifecycle management with configurable retention policies for completed and expired reservations. Through the Retention Policy console, administrators can set specific retention periods for canceled and ended reservations, with separate preferences supported for archiving and trashing.

If no retention preference is configured, the existing 24-month default remains in effect, and the 30-minute retention for provisional reservations continues unchanged. This enhancement provides organizations with the flexibility to align reservation data retention with their specific compliance and operational requirements.

Agile Board: Sprint Names

Teams using Xurrent's agile boards can now assign custom names to sprints, moving beyond the limitations of numeric naming conventions like "Sprint 1" or "Sprint 2." This enhancement allows teams to align sprint names with specific goals, themes, or objectives for greater clarity and context.

Users with sprint management permissions can edit sprint names at any time. New sprints still receive a default system-generated name (for example, Sprint N), which can be easily overridden. When a custom sprint name is applied, it fully replaces the system-generated name across all boards, backlogs, sprint selectors, and scrum views, providing consistency throughout the platform while maintaining familiar behavior where no custom name is applied.