Xytech 2026 Release - Release Log - 26.2

Deprecation Announcements

Smart Client for End Users

Smart Client is no longer supported for normal users in version 11.0 and beyond. Smart Client will still be supported for Layouts and Report Writer until a replacement of equivalent functionality in the web UX is made available in a future release.

Configuration

The Application Server configuration entry for SKY_BROADCAST_CHANGES is deprecated in version 11.0 and beyond. It has been determined that this setting was causing major, unnecessary performance issues in systems with 100 or more users. Going forward the system will not broadcast changes to all user sessions. Users will continue to receive changes from other users upon re-opening a particular Maintenance Document or Search List. This primarily affects refreshing of searches, and the population of dropdown lists when new values are recently added. Broadcasting of booking changes into the Schedule Book will remain active.

REST API V1 (version 1)

The REST API V1 (version 1) has been deprecated as of 11.0. The API will not be removed from the product, but we will no longer enhance the capabilities of the deprecated API, and support for the deprecated version may be limited. It is strongly recommended you do not use deprecated APIs for any new development and begin now to port all API usage to the REST API V2 (version 2). While porting, we recommend taking advantage of the new Webhooks features available in the REST API V2 for outbound integrations.

Pre-Announcing Deprecations in Future Releases

APIs

The SOAP API will be deprecated in a future version. The API will not be removed from the product, but we will no longer enhance the capabilities of the deprecated API, and support for the deprecated API may be limited. It is strongly recommended you do not use deprecated APIs for any new development and begin now to port all API usage to the REST API V2 (version 2). While porting, we recommend taking advantage of the new Webhooks features available in the REST API V2 for outbound integrations.

Additions and Enhancements

Framework, Dashboards, Fundamentals

Contacts - Change Alternate Address in Maintenance Document

To resolve performance issues caused by the exponential growth of address records, we have decoupled Alternate Addresses from the main Contact document. Previously, address data was stored directly within the Contact record; it has now been moved to a standalone related list.

• Decoupled Architecture: The sys_alternate_address table has been removed from the Contact document (SysAddressBase). This change ensures that the high volume of address snapshots created by Library, Rental, and Invoicing movements no longer impacts the loading speed of the primary Contact record.
• New Standalone Document: Alternate Addresses are now managed via a dedicated list document (SysAlternateAddressList). This list can be accessed via Navigator > System > Alternate Addresses.
• Contact Screen Updates: Within the Contact Maintenance screen, the "Alternate Addresses" tab now functions as a related document list.
• The address grid is no longer editable directly.
• Users must click the ID to open the Alternate Address Maintenance form for edits.
• Use the (+), (-), and Duplicate icons within the related list to manage address records.

• API Impact: This is a breaking change. The sys_alternate_address table is no longer included in the Contact record API results. Integrations must now query the Alternate Address document separately.

Required Configuration Navigator Access: Admins should verify that *System > Alternate Addresses is visible in the Navigator for relevant user roles.

• Layout Review: Check standard Contact layouts to ensure the new SysAlternateAddressList related document is positioned correctly on the Alternate Addresses tab. 34660

Hide banner using DOC_BANNER_LOCATION=NONE

To help improve screen usage, the banner bar that was displayed in the header of most tabs has been removed. This frees up valuable space on the screen for use by layouts. Any sites that had a custom banner image, will still see it, until they decide to remove it, in which case please raise a ticket with our support team who will assist.

• Streamlined Interface: This change ensures that new users have more vertical screen space available for data grids and document headers immediately upon installation.
• Re-enabling the Banner: If a site requires the banner graphic, it must be manually enabled by adding the following parameter to the mediapulseappserver.config.txt file:
• SKYWEB_[SERVERNAME]_DOC_BANNER_LOCATION=Content/images/doc-banner.png (Note: Replace [SERVERNAME] with your specific server designation).
• (Note: Replace [SERVERNAME] with your specific server name. This parameter tells the application exactly which image file to use for the banner.) 38739

Smart Client OpenID Authentication

Xytech Smart Client has now been enabled for OpenID authentication.

Configuration: OpenID config in client side, ensure OPENID exists in the value of AuthMethod in MediaPulseClient.exe.config:

<applicationSettings>
    <Xytech.XE.Client.MDI.Properties.Settings>
      <setting name="AuthMethod" serializeAs="String">
        <value>OPENID:DB</value>
      </setting>
      <setting name="AuthControl" serializeAs="String">
        <value>Y</value>
      </setting>
    </Xytech.XE.Client.MDI.Properties.Settings>
  </applicationSettings>

39050

UX update to light themes with a light navigation pane

Light themes (Default and Bootstrap) now includes a light and cleaner navigation panel. 39130

Add passing of auth token and restBaseUrl to the web gadget

The Xytech Web Gadget feature has been enhanced so that you can optionally pass an authentication token to the app within the iFrame.

This enables 3rd party app developers to embed apps as extensions to the main Xytech app that call the Xytech REST API authenticated as the currently logged in user. 38050

Media Order

Media Order usability tabbing sequence re-working

We have updated the tabbing logic to ensure a "contained focus" within multi-tab layouts.

• Old Behavior: Pressing Tab on the final field of a page forced the browser/application focus to the next physical tab header or its contents.
• New Behavior: Navigation now stays localized. When a user reaches the last field and presses Tab, the focus returns to the first field of the current page. This prevents "grid jumping" and keeps the user on their intended layout screen.

We have reworked the tabbing sequence and focus logic within all system grids to ensure a seamless, "circular" navigation experience.

• Focus Retention: If a field loses focus (e.g., clicking outside the specific input), the focus now remains anchored to the active row. Pressing Tab will simply restart the sequence from the first field of that same row.
• Row-to-Row Navigation: Tabbing out of the final field in a row now automatically advances the cursor to the first field of the next row.
• Grid-to-Grid Navigation: If a user tabs out of the very last field of the final row in a grid, the focus will now advance to the next available grid on the layout.
• Blank Space Interaction: Clicking into any empty space within a grid container will now automatically set the focus to the first column of the active row.

The Media Order standard layout has been updated with a corrected field tab sequence.

• User Impact: Navigation now follows a consistent, predictable flow across each page.
• Custom Layouts: This fix is applied to the Standard Layout only. Because tab sequences are embedded in the layout definition, existing Custom Layouts will not automatically inherit this update. To apply this consistent tabbing to a custom view, the layout must be re-created. 28611

Payroll Rules, Scheduling Counters & Personnel Rules

Display Grouped Scheduling Counter Rule Amounts in the Counter Rule Evaluator List [20178]

The Counter Rule Evaluator List (CREL) has been enhanced to improve how scheduling counter amounts are grouped and displayed. The system now identifies and aggregates data based on the unique combination of the resource and their specific group rules.

• Unique Row Logic: Each row in the CREL Resource Block now represents a unique combination of Resource Description + Group Resource Scheduling Counter Rule.
• Rule Aggregation: When multiple groups share the same counter rule for a single resource, their amounts are now displayed together. This ensures the total counter amounts are accurately reflected and visible in a single view.
• Export & Reporting Consistency: This new grouping and display logic has been applied to the CREL Export functionality and the generated Reports, ensuring data parity between the on-screen view and exported files.

The logic for checking Scheduling Counter Rule conflicts has been expanded. Previously, conflict calculations for bookings (Quick Holds, Transactions, and Rosters) were only performed using rules set at the Resource level.

• Dual-Level Validation: The system now checks for Counter Rule conflicts at both the Resource level (SchResource) and the Resource-in-Group level (SchGroupResource).
• Multi-Group Tracking: When a resource belongs to multiple groups, the system will now calculate weekly counter amounts per group. This ensures that bookings respect the specific limits and thresholds defined for each role or group the resource is assigned to. 35824

Scheduling Counter Rules - Apply Rules from Both Resource and Group Levels [20255]

The system now enforces scheduling limits across multiple levels simultaneously. This allows for a global annual limit for a resource while also enforcing stricter, lower limits for specific roles or groups.

• Global Enforcement (Resource Level): Rules set on the Resource (SchResource) apply globally. All penalties and limits are enforced regardless of which group the resource is booked under.
• Role-Specific Enforcement (Group Level): Rules can now be applied to the Resource-in-Group (SchGroupResource) or the Group itself. These limits only trigger when that specific group is assigned to the transaction (Work Orders, Quick Holds, and optionally Rosters/OTO).
• Tiered Validation: The system checks limits in a specific order:
• Global Resource Rule (Primary usage tracker).
• Resource-in-Group Rule (Specific to that person in that role).
• Group Rule (Applies to everyone in that role).

IMPORTANT NOTE: The decision was made to not include a preference -- module, user or otherwise -- to maintain the current workflow that uses only one Rule. 36133

Scheduling Counter Penalty - Minimum Rest Period after X Consecutive Days [20554]

A new penalty type, Minimum Rest After Consecutive Days Penalty (MINRESTCONDAY), has been introduced to enforce mandatory rest periods after an employee works a defined number of consecutive days. This enhancement ensures scheduling compliance and provides flexible penalty handling.

• Configure the rule to apply after a specified range of consecutive days (using From/To)
• The minimum rest period is defined using the Threshold field
• The rule can be applied to specific transaction types (Rosters, Orders) using the Applies to Type field
• Penalty action is configurable: flat fee, hourly rate, or entitlement increment 36394

Transmission

Visual Path - Resource Search - Ability to unselect a resource to remove it from the order

The visualiser resource search display has been enhanced so that users can now unselect a resource to unassign it from the operation.

• Resource Unselection: While editing a Visual Path resource, users can now click to unselect the currently assigned resource.
• Persistent Structure: Removing a specific resource assignment leaves the Group and Task intact, allowing the order structure to remain while the specific labor or equipment is cleared.
• Search List Integration: This functionality is integrated directly into the Resource List display within the search modal, making it easier to manage assignments without leaving the visual workspace.

Required Configuration Resource Group Settings: To successfully save a task without an assigned resource, the Resource Group must be configured with *Resource Required = No.

• Note: If this is set to Yes, the system will trigger a warning and require a resource selection before the record can be saved. 29596

Visualizer - selecting nodes and displaying menu UX improvement reducing clicks

The visualiser has had a UX improvement, so the user now only has to hover-over an item to bring up the contextual menu as opposed to clicking on the item. This makes building a transmission path flow better with reduced clicks.

• Menu Display: Hovering the mouse over a node (including Service and Service Header text) now displays the contextual menu. Moving the cursor away from the node or the menu hides it.
• Node Selection & Grid Sync: Clicking a node still performs the standard selection actions. It selects the matching row in the data grid and triggers any established layout visibility rules.
• Menu Switching: Users can move the cursor directly from one node to another to display the next menu without clicking. 36354

Transmission order layout that includes visualiser

A new standard transmission order layout has ben created that includes the visualiser canvas on the primary tab. 38085

Resolved Issues

API & Web Hooks

Loading WO Templates via API Deletes Existing Transactions [21359]

Resolves an issue where applying a Work Order Template via the REST API automatically deleted all existing transactions on a Work Order. The Web UI provides users with a prompt to either "Append" or "Replace" transactions, the API lacked this toggle and defaulted to the "Replace" action, resulting in the unintended loss of pre-existing data. The save argument LoadTemplateOption has been fixed so that option 1 will append transactions. e.g. --header 'saveArgument: {"LoadTemplateOption":1}' See API user guide for more information. 38418

POST API calls in v11.3 returning code 200 (OK) as opposed to 201 (Created) in v10.4 impacting Integrations. [21607]

Version 11.x introduced a response body for both POST and PATCH requests. As a result, the success response codes for these operations have changed from 201 (Created) and 204 (No Content) to 200 (OK).

This change may impact existing integrations that rely on specific success codes, such as expecting 201 when a record is created.

To support backward compatibility, a feature flag, use_legacy_api_v2_response, has been introduced. When enabled, it returns an empty response body and restores the previously expected response code. 38706

Bids / Budgets

Error When Editing Bid Details [14747]

Resolves an issue where, when editing a bid, a user sometimes received an error 'Cannot read properties of undefined (reading 'getTopBarLeftSelector')'. 28122

Running 'ActualCostDetailReport' with Episode Detail No Does Not Return Results [15167]

Resolves an issue in the Actual Cost Detail Report where adding an Episode filter did not return results. 28430

Bid - Copy Bid Detail and Dates Are Initially Editable When They Shouldn't Be

Resolves an issue where, after copying a bid detail row, the Begin and End Dates were initially editable when normally they are not. 28459

Date Mismatch Between Transactions and Bid Detail Rows on Work Orders Created from Bids [15525]

A change has been made so that order transactions created through the bid approval process will be assigned the dates defined on the bid detail if present. If not, dates will be assigned by the bid detail header or overall header as previously.

When creating new orders from bid approval, order begin/end are set to the earliest begin and latest end of bid headers or details. If they're within the order time range, new transactions will use bid detail time, if present.

On bid approval, if user chooses 'Add to Existing Order' and bid detail begin/end times are out of the selected order's time range, then the new transactions will use order time range (existing logic) instead of using bid detail time.

NOTE: To date, order transaction dates were set by bid detail header dates, not the individual detail dates. 29094

Working Budget Already Exists' Error Discrepancy [15432]

Resolves an issue where an error may have led the user to believe more than one Working Budget can exist on a Job as long as one of them was closed. This isn't the case. Other Working Budgets can exist on a Job, but all but one must be cancelled. 29145

Missing Prompt for Recalculate Budget in Roles

Resolves an issue where the Role permission for the new Recalculate Budget action displayed the variable name (BaseListAndDocument.RightRECALCULATEBUDGET) instead of the appropriate Prompt. 31343

Export from Monthlies Export Throws Error [20432]

Resolves an issue where exporting Monthlies to Excel resulted in an error for certain users when choosing the “All” export option. 36399

Bid Occurrences count is not reflecting after selecting Occurrence Dates

Resolves an issue where the Bid Header 'Occurrence' field would remain null regardless of how many Occurrence Dates were selected and applied. 37970

Document Customizations

Work Orders - Grid Update [20318]

Resolves an issue where a dropdown/custom field added to the Media Order document was not editable via Grid Update on the Job Management > Work Orders list. 36170

Framework, Dashboards, Fundamentals

Incorrect Tab Focus on Multi-Document Default Dashboards [8465]

Resolves an issue where default dashboards containing multiple documents would open with focus on the right-most tab instead of the left-most tab. 22311

Pressing the tab button doesn't change the focused item after reaching the end

Resolves an issue where the cursor focus became trapped on the final field of a Media Order tab rather than returning to the first field to restart the sequence. 29732

View Only' Users Not Allocating to 'Current Read Seat' License Count [16617]

Resolves an issue where having Edit access to any related document in the system -- even search lists where there was no editing -- prevented a user from utilizing a Read Only license seat. 31036

Failing to save/warn on save when moving between records from a list [19250]

Resolves an issue where updates made to a record opened from a list were lost when clicking Next. The system did not prompt the user to save changes before moving to the next record. 33770

Users Not Seeing Dashboards without Super User Access [19958]

Resolves an issue where non–super users were unable to see or access dashboards they previously created and had been assigned. 34968

Auto-Login Triggers Immediately After Session Timeout, Re-Authenticating Logged-Out Users

Resolves an issue where the auto-login logic did not distinguish between a timeout logout and a normal page load. As a result, when a session timed out, the system still triggered the auto-login flow, causing the user to be immediately re-authenticated after the session ended. 35880

Unable to select Time Zone when UI is set to Full screen mode

Resolves an issue where the Display Time Zone dropdown menu opened beneath the Media Order > Services > Update Status pop-up while in Full Screen mode. 36569

Timecard>New >Time Entry, option should not display

Resolves an issue where a non-functional Time Entry document was available for selection in the navigator for the Time Card module. 38917

Jobs, Orders, Billing (Job Management)

Missing Job Reference on Project Billing Invoice [695]

Resolves an issue where the Job Reference field did not display data when generating reports from the Job Actions menu > Project Billing > View Invoice Form command. 11671

Parent W/O ID and Description Fields are Empty in Order Transactions List

Resolves an issue in the Order Transactions List where the Parent WO ID and Description were not showing. 25857

Actuals Links Disappear When Order Actualizing

Resolves an issue in Order Actuals where the visual indication of links -- green color in the 'Linked' column -- disappeared upon actualizing. 29731

Previous resource is retained when moving booking from one room to another (with new W/O Template loaded). [19606]

Resolves an issue where moving a Transaction to a Room associated with a Work Order Template did not prompt the expected “Replace or Append Transactions” dialog. Instead, the system retained the previous resource when transferring the booking from one room to another. 34345

Language Packs

Relative' on All Calendars is Not Translated into Any Language

Resolves an issue where the word "Relative" on all Calendars is not translated in any of the Language Packs. 31287

Media Order

MO Service Template: Services Not Linking to Title [14913]

Resolves an issue where detail within a Service Template created Service Rows with duplicate sequence numbers. Research into the cause of the duplication is ongoing but an error message has been inserted to alert the user to the problem. The user can fix the issue by manually dragging and dropping one of the Service Rows to trigger display sequence to update. 28644

Actualizing a Task does not properly filter the Actualize page to show the transaction associated with that task [19601]

Resolves an issue where the same resource was displayed for the first two operations when actualizing single operations from the Operations List. 34051

Action: Search and Add Assets : svc row rules not able to find existing assets to add as source to the order

Resolves an issue where the "Search and Add Assets" action on a Media Order created new assets for all target sources instead of identifying and adding existing assets that matched the service rule criteria. 34973

13282 Re: Usability | Service - Dependencies copied to other rows or removed [19845]

Resolves an issue where Media Order Service row Dependencies were not reliably entered or retained. Dependencies may have been removed on entry, changed unexpectedly, or copied to other service rows when navigating between rows in the Dependency column using the arrow keys. 34975

Cannot link source to service package header in Media Order. [20059]

Resolves an issue where users were unable to link a source to the Service Package header within a Media Order. 35587

Packaged Transactions Coming Unpackaged, resulting in incorrect Order Total/FC Totals. [19408]

Resolves an issue where, on a Media Order, packaged transactions may have become unpackaged when a service status was changed, and a service row was deleted before saving. 35810

Payroll Rules, Scheduling Counters & Personnel Rules

Counter Rule Conflict - Justification Value Not Saved

Resolves an issue where a Consecutive Days counter rule configured with the Maximum Consecutive Days penalty type and the “Warning w/ Justification” alert option did not retain Justification values on the first ten consecutive transactions. After updating transaction times, the Justification entries were cleared rather than saved. 36381

Orphan transactions keeping a resource booked [20654]

Resolves an issue where deleting a resource transaction configured with a Scheduling Counter Rule (such as Advance Notice) could cause subsequent scheduling of the same resource to incorrectly report a Double Booking conflict due to lingering, unexpected data persistence. 36523

Actual Unit not being Used in Counter Rule Evaluator List [20732]

Resolves an issue where Actual Unit was not being considered when calculating Counters within the Counter Rule Evaluator List. It appeared the Actual Begin and Actual End Dates were being used instead. 36566

Rental

Application Error and Missing Resource on Rental Package Check-out [15743]

Resolves an issue with Rental Packages where the lead resource in the package was not loading properly into the Check In/Out. 29383

Scheduling

W/O Transaction Email/Notify All Not Working [12985]

Resolves an issue where configuring an Event Trigger with Event Type: Notify, and Document: WO Transaction, and using the Actions > Transaction > Notify action to send a notification to "All" did not generate notifications for all Transactions in the Order. 26997

Schedule views with several groups & assigned resources intermittently not displaying or collapsing items as expected / configured [38036]

Resolves an issue where "ghost" duplicate Resource records appeared in the Schedule Book Items window, and when sorting or re-ordering the rows, the Y-axis became frozen, prohibiting the expansion and collapse of Groups.

Bundled Resources in W/O Template are Not Displaying as Transactions After Moving the Order From One Resource to Another on Schedule Book [10118]

Resolves an issue where changing the Resource on an Order Transaction was not always loading the linked W/O Template for that Resource. 27501

Schedule Book Views Open to the Previous Day When User Time Zone is Set to (UTC+12) [14277]

Resolves a known issue where users in time zones offset from the database time by 12 or more hours would find the Schedule Book opening on the incorrect day. 27884

Group Resource List' Dialog Pops Up When Selecting a Resource on Schedule View to Add to an Existing Booking [14316]

Resolves an issue in the Schedule Book for a Group where Resource Required = Prompt, where selecting resources while the Edit Order pop-up was opened did not add those resources to the Order. 28114

Rosters Outside of Date Range on Resource Off Time Report [14646]

Resolves an issue in the Roster Off Time Report where data is returned that is outside of the specified range. 28146

Roster Template Not Following the Day Rule [15230]

Resolves an issue where a Roster Template with a single detail specified for a day -- other than day 1 -- was not loading off time on just that day. Rather, it loaded that single detail every day. 28519

Application Error When Adding Items to a Schedule Book View [16890]

Resolves a known issue where an application error would occur when adding Items to a Schedule Book View. 30361

Long W/O Note in Hover Text on booking bar causing display issues. [17710]

Resolves an issue where Work Order Notes that wrap due to the size of the note entry window did not wrap in the Schedule Book Transaction Hover window. Only manual line breaks (carriage returns) are respected in the hover display, while automatic wrapping based on window dimensions is now carried over. 31693

Off Types Setup Screen Freezing/Hanging, Slow Response Time [20199]

Resolves an issue where the Off Types setup screen experienced freezing, hanging, or slow response times during use. 35879

Scheduling->Setup->Group Classes document throws Client-Side error of Range Error

Resolves an issue where a "Maximum call stack size exceeded" error (RangeError) occurred in the Group Classes setup module, triggered when a user attempted to view a large number of filtered groups by utilizing the vertical scrollbar within the right-hand view pane. 36288

Schedule Book: Filter/Customize Buttons Not Restored After Switching Back from Blank View

Resolves an issue where conditional "Customized Buttons" (Filters) would incorrectly disappear or persist on the Schedule Book based on the state of the previously viewed tab. 37668

Grey drag selection box misaligned issue in full screen mode

Resolves an issue where in Schedule Book, the drag/selection box didn't show when dragging to create bookings in Full Screen Mode. 37707

Application throws unique constraint error and page gets stuck on loader when duplicating resource second time in Scheduling Group document

Resolves an issue where the duplicate function was visible and accessible in the Group Resources grid, even though the system does not support resource duplication in this view. 37817

Scheduling Resource - After the validation error, the entire screen becomes unresponsive and no UI actions work

Resolves an issue where attempting to save a Resource created from the Group Resources tab without populating required fields caused the record to lock for editing after the validation message was dismissed. 37979

Roster creation is allowed via Navigator for grayed dates

Resolves an issue where rosters could be created and deleted via the Navigator on grayed-out dates despite the 'Show Bookings in Future Days' restriction, resulting in inconsistent rules between the Navigator and Schedule Book. This inconsistency extended to Quick Holds, which—while correctly restricted for creation everywhere—could still be deleted from the Quick Holds list on those same restricted dates. Rosters could be duplicated from and to restricted dates. 37980

Schedule Book Hover Not Showing All The Group/Resources Within The WO Transaction [20817]

Resolves a known issue where the 'Group/Resource All' setting on the Schedule Book's Work Order Transaction Hover did not correctly display the full list of Resources associated with a transaction. When users hovered over a transaction in the book, the tooltip would omit certain Resources or Groups, even though the configuration was set to display all relevant data. 38017

Transmission

MCR Resources Path Field Limited to 255 Characters [7058]

Resolves an issue in the Transmission MCR list where the Resource Path field was limited to 255 characters, which truncated some of the resources and prevented accurate filtering. 21247

Visual Path - 'Remove to End' should not be available on last node

Resolves an issue where the right-click menu of the Visualizer control in a Transmission Order displayed the Remove to End action for the last operation in a transmission path. (For the last item only, this action was redundant to the Remove action.) 24833

Rapid Update Tx Order Times does not update operations [18867]

Resolves an issue where updating an Order’s time via Rapid Update—without changing the date—failed to update the Order and Transaction times, even though a confirmation message indicated the update was successful. 32694

Transmission: Scheduling Group Action 'Group Import Transmission Bandwidth Plans' not available to non-super users [19222]

Resolves an issue where non-super users with full access to Scheduling Groups, Scheduling Group, and Group Import Transmission Bandwidth Plans could not access the Import Transmission Bandwidth Plans option from the Actions menu in Scheduling Groups. 33755

Visualizer - adding an Operation to a service fails to generate a Row ID when Service Profile has a 'Manual add default' row

Resolves an issue where a Row ID was not populated when a user manually created an Operation row on a Transmission Order using the Visualizer. 36333

Infinite loading on selecting Duplicate option in the Visualizer

Resolves an issue where an infinite loading state occurred when attempting to duplicate a Transmission Service in the Visualizer after using the "Select with Contents" option. 38609

Visualizer - nodes overlapping making the visualiser unusable

Resolves an issue in the Transmission Visualizer where nodes were overlapping, rendering the Visualizer unusable. 39006

Transmission - Availability Range – Save Fails Due to Missing trx_type_no

Resolves an issue where an error would result when creating an Availability Range either from the navigator or via the Schedule Book. 39040