April 2025 Hotfix

Enhancements

API versioning implementation
To enhance flexibility and ensure seamless updates, API versioning has been implemented across key Developer Portal APIs:
  • Versioning Support: With this implementation of versioning, APIs will be able to process new features and modifications added to OTP effectively. This will allow Thomson Reuters to introduce updates without altering the existing functionality that clients currently rely on.
  • Version-specific Routing: Requests are automatically directed to the appropriate API version.
  • Updated Documentation: API documentation now details available versions, differences, and upgrade steps.
  • Impact Assessment: Changes have been tested to ensure no impact on previous versions.
Updated APIs

Resolved issues

  • Resolved an issue where upon a new instance creation, the value for ‘
    Current State Tax Provision
    ’ on the State Support Provision Summary Report was incorrectly calculated when the parameters ‘
    ENHANCED_DEFBAL_RPT_PERF
    ’ and ‘
    ENHANCED_REGEN_PERF
    ’ was set to ‘0’ under Administration > System > Manage Restricted Features.
  • Resolution of User Role Discrepancy in Exported User Template:
    The mismatch between user roles in the Administration Tile | User | Export | All Enterprise Role Users and the exported user template has been resolved. Previously, the export incorrectly displayed a "Read Only" role, which did not match the actual OTP permissions. The export functionality has now been updated to accurately reflect the user roles as configured in the system. The underlying issues in role mapping and export processes have been identified and corrected. Users can now export user templates with role information that precisely matches OTP permissions.
  • Resolved an issue regarding Workpapers:
    1. Dataset Type dropdown was only showing Provision datasets for GET/SET functionalities in PTBI formul Now it currently displays all dataset types.
  • Fix for SignOff Transition API Returning No Results:
    The SignOff Transition API issue, where it returned an empty result set despite existing SignOff actions, has been resolved. The API now correctly retrieves and displays SignOff data for datasets, ensuring accurate reporting and tracking of SignOff actions.
API