For the Case V8.31.0 Release, targeted for February 13th, we're planning the following improvements.

Fixes:

• Parts Availability Accuracy: Parts availability will consistently display accurately across all operations.
• Operation Approval Details: View details for the operation approvals will display correctly. 
• Audit Trail Attribution for Purchase Orders: If the Fleet user includes the PO # during the Service Request, the audit history will show that user's name.

Enhancements:

• API transition - Login server for Portunus to Portal

Case V8.31.0 (Targeted for February 13th):

Parts Availability Accuracy:

Resolved an issue where operations were incorrectly marked as “No parts available” when at least one required part was available.

• When some parts were unavailable, but others were available, the system now correctly displays “Some parts unavailable.”

This update ensures accurate and consistent parts availability status across environments.

Operation Approval Details:

Resolved an issue where “View Details” for approval status did not display after a customer approved an operation line item.

With this fix, approval status details now correctly appear once the customer completes the approval, ensuring transparency and proper visibility into approval outcomes.

Audit Trail Attribution for Purchase Orders:

The system now consistently records when a Fleet user adds a Purchase Order (PO #) during the creation or update of a Service Request, ensuring clear and accurate attribution in the audit history.

API transition - Login server for Portunus to Portal:

We are preparing to transition to a new Login server for API authorization. This change is being implemented to enhance our authentication infrastructure and ensure continued reliability and performance.
What you need to know:

• This transition will be transparent to all API consumers.

• No changes are required from your end at this time.

• We expect zero interruptions of service during the migration.

While the switch is designed to be seamless, we wanted to proactively inform all users so you are aware of this infrastructure update. If you notice any unexpected behavior or have concerns, please reach out to our support channels.