Runcutting

Version	Type	Description	ID
19.1.0.0	ENH	When adding a new run type, you must fill in the Number of Operators field so that BlockBuster Web can determine how to use the run type. (This value is applied when you also have Trapeze OPS.)	BLOC-948
19.1.0.0	ENH	The User Driver Blocks property has been removed since BlockBuster Web only cuts driver blocks if used. (The driver blocks are set in Trapeze FX.)	BLOC-945
19.1.0.0	CORR	The issue of being unable to import and/or match runs from another sign-up period and runcut scenario has been fixed.	BLOC-936
19.1.0.0	CORR	The issue of login failure due to having the SSL protocol enabled for encryption purposes has been fixed.	BLOC-931
19.1.0.0	CORR	The issue of users not being able to assign new run numbers when manually runcutting has been fixed.	BLOC-1113
19.1.0.0	ENH	When attempting to copy travels, users are now prompted to confirm the action they want when there are no travels and when there are existing travels of the selected type and context to be copied. If there are travels to be copied, users are asked if they want the existing travels to be overwritten. If they click Yes, the existing travels are deleted and travels of the source sign-up period are made.	BLOC-940
19.1.0.0	ENH	The All option has been added to the Block drop-down list in the Update Reliefs screen allowing users to update all blocks that belong to the selected Line group.	BLOC-937
19.1.0.0	ENH	The issue of not being able to save any costing changes when the Override cost option was toggled Off has been fixed. (The issue occurred when using an Oracle database.)	BLOC-1188
19.1.0.0	ENH	Users can now view and select Exc Combo scenarios in the Run Scenarios screen.	BLOC-1199
19.1.0.0	CORR	The issue of Run Type violations not being shown in the Costing summary while run costing has been fixed. Any violation is now shown in red text or highlighted in red.	BLOC-1129
19.1.0.0	ENH	Runcutting with driver blocks can now be performed successfully.	BLOC-1296
19.1.0.0	CORR	Improved the performance of the Run Cost feature.	BLOC-1504
19.1.0.0	ENH	When users attempt to shift reliefs on entirely uncut blocks, the fields in the Shift Reliefs pane appear shaded and a message now appears advising them that the task cannot be performed.	BLOC-1486
19.1.0.0	CORR	The issue of multiple piece runs not being created or swapped while manual runcutting has been fixed.	BLOC-1534
19.1.0.0	CORR	The data refresh issue that sometimes occurred after applying Uncut Pieces to runs has been fixed.	BLOC-1123
19.1.0.0	CORR	The issue of duplicate run numbers being produced when runs were being renumbered has been fixed.	BLOC-1165
19.2.0.0	CORR	The Modify Standby option has been added to the Runs screen to allow users to make changes to standby times.	BLOC-1625
19.2.0.0	ENH	In the Modify Standby window, the options for Start Standby and End Standby are None, Depot, and Road. These options are equivalent to: blank, SD, and SR in BlockBuster (Legacy version in Trapeze5). If a node is a garage in either the Start or End node, the only available option in Standby types is Depot. If otherwise, the options are Depot and Road.	BLOC-1660 This task is related to BLOC-1625.
19.2.0.0	CORR	The issue of not being able to create extra pieces as standalone runs has been fixed.	BLOC-1626
19.2.0.0	CORR	The Run Scenarios grid now includes the Straights column, which shows the percentage of straight runs in the runcut solutions.	BLOC-1629
19.2.0.0	CORR	The issue of incorrect formats for the Adjusted Platform and Adjusted Break times has been fixed.	BLOC-1630
19.2.0.0	CORR	The exception error that occurred when the costing of a run, which was manually runcut, was updated has been fixed.	BLOC-1669
19.2.0.0	ENH	The User Name of the user who saved a scenario, and the date and time when the scenario was saved have been added to the Run Scenarios grid.	BLOC-1692
19.2.0.0	ENH	When users create a scenario or select one in the Run Scenarios screen, a working scenario is now also available where the users can test their changes before saving.	BLOC-1691
19.3.0.0	CORR	The issue of Run Names not being saved into a new scenario after running the Import/Export Runs feature has been fixed.	BLOC-1782
19.3.0.0	CORR	The issue of runs not appearing in a new scenario after using the Generate Exception Runs feature for a Service Group Exception Combination has been fixed.	BLOC-1777
19.3.0.0	CORR	The issue of changes to relief locations and times not showing after running the Update Reliefs feature in the Runs, View Reliefs, Manual Runcut, and Shift Reliefs screens has been fixed.	BLOC-1749
19.3.0.0	ENH	Added Load option to the Waits and Travels dialog box.	BLOC-1751 This task is related to BLOC-1767.
19.3.0.0	ENH	Improved behavior of options in the Wait and Travel dialog box: When applying the Add or Edit options and there is only one Sequence for the Wait and Travel, users can edit the From Node, To Node and Type fields. If the Sequence value is more than 1, these fields are automatically filled in with the values of Sequence 1 of the same Wait and Travel. (There can be multiple Waits and Travels between the same nodes using different Numbers even if the Travel Type is the same for all of them because there may be different routes to get from point A to point B.) The Sequence field is only automatically filled in. When adding a Wait and Travel and users pick an existing Number, the Sequence is automatically set to the next available one for the record. The Delete option is only available on the last Sequence of a Wait and Travel Number.	BLOC-1767
19.4.0.0	CORR	The issue of the Start Travel Type and End Travel Type values not being shown properly in the Run Cost screen has been fixed.	BLOC-1757
19.4.0.0	CORR	Users are now prompted to save the scenario after performing a manual runcut if they wish to save their changes. The Context field also now appears with an orange background if the changes have not yet been saved.	BLOC-1762
19.4.0.0	CORR	The following issues with the Created Pull Out and Pull In feature have been fixed: When applied in relief locations, runs are not costed properly. Applying created pullouts/pullins to Blocks failed when using the Apply Created Pullouts/Pullins option.	BLOC-1808
19.5.0.0	ENH	Validation messages that are shown will now include general descriptions of the issues found when Blocks or Trips data is not loaded properly. Possible issues include: less than two garage events on a block, first block event is not PO, last block event is not PI, From time of first trip is earlier than PO time, To time of last trip is later than PI time, and trip has no trip times.	BLOC-1761
19.5.0.0	ENH	Users can now move pieces into a new run by entering the run number in the Run Number fields in the Run and Block panes of the Runcut screen. After entering the run number, users must click the Apply Changes option in the drop-down menu.	BLOC-1747
19.5.0.0	CORR	The issue of runs appearing uncut after users pressed the Refresh (F5) button after runcutting has been fixed. The issue occurred after users uncut some runs in an existing scenario and then runcut them using the "Cut all and add uncut blocks" option.	BLOC-1881
19.6.0.0	CORR	The issue of manual runcutting not working on driver blocks has been fixed.	BLOC-1941
19.6.0.0	CORR	The issue of deadhead time being added to the platform time when Created pull-ins and pull-outs were used in runcutting has been fixed.	BLOC-1947
19.6.0.0	CORR	The issue of the runs being uncut when the Import from FX option in the Import/Export Runs dialog was selected has been fixed.	BLOC-1952
19.6.0.0	CORR	The issue of all runs not being exported when the Export to FX option in the Import/Export Runs dialog was selected has been fixed.	BLOC-1953
19.10.0.0	CORR	The issue of runs with forced run types not retaining the run type after the runcut was performed has been fixed.	BLOC-2013
19.10.0.0	CORR	When users enter a travel record with an error, they are now able to edit and save the record. Previously, the record would have been deleted and users had to enter the record again.	BLOC-1735
19.10.0.0	CORR	The issue of not all reliefs being created when the Update Reliefs feature was applied has been fixed.	BLOC-2039
19.10.0	CORR	A new option, Clear Active has been added to the Run Scenarios footer to allow users to cancel the selection of the current active scenario. If the selected scenario is not shown as active, the Set Active option is shown instead.	BLOC-2081
19.10.0.0	CORR	Only the run scenario that is being used in the current context and matches what is selected in the main context is now displayed in the Run Scenarios screen. These scenarios are shown with an asterisk, for example, "test1*".	BLOC-2088
19.10.0.0	ENH	The Generate Schedule and Remove Schedule options have been added to the Shuttle Schedule feature.	BLOC-458 This task is related to BLOC-2077.
19.10.0.0	CORR	The issue of the supplementary data not being updated when users generated exception runs has been fixed.	BLOC-2083
19.10.0.0	CORR	The issue of pull-outs and pull-ins not being generated when the Created Pullout/Pullins feature was applied has been fixed.	BLOC-2121
19.10.0.0	CORR	The issue of the distance in the Travels screen not being shown in the selected Distance format has been fixed.	BLOC-2110
19.10.0.0	CORR	An error message is now shown when users attempt to generate exception runs and there is no active scenario and/or no default run exception set.	BLOC-2106
19.10.0.0	CORR	The issue of users being able to mark scenarios that have not been saved as Active has been fixed. The following changes have also been made to support this fix: A new permission, Activate Scenarios has been added to control the activation of scenarios. User scenarios (those marked with an *) do not have update or delete options. When users attempt to delete a scenario, the system now first checks if the scenario is an Active or User scenario. If the selected scenario is of either type, a message informs them that it cannot be deleted. Previously, the system asked the users to confirm the delete action before checking the type of the scenario being deleted. (Only scenarios that are not Active or User scenarios can be deleted.)	BLOC-2139
19.10.0.0	CORR	When users have not made changes to a scenario that they have already saved, they are no long prompted to re-save it. The prompt to save previously appeared every time users attempted to change the context of the scenario.	BLOC-2151
19.10.0.0	CORR	The issue of the desired Run Type Percentages not being calculated properly based on the run type percentage rules set has been fixed.	BLOC-2161
19.10.0.0	CORR	The issue of different values being shown for the cost of the same run in the Run Costing dialog and the Run screen has been fixed. Previously, the value in the Run Costing dialog showed the full amount while the value in the Run screen was rounded down. Both fields now show the full amount.	BLOC-2164
19.10.0.0	CORR	The issue of the Piece makeup time not being properly costed when the Start Travel is a shuttle with additional wait time has been fixed.	BLOC-2173
19.10.0.0	CORR	The issue of travels without waits being deleted when users applied the Generate Travels From Waits and Travels feature in the Travels screen has been fixed.	BLOC-2179
19.10.0.0	ENH	In the Travels screen, travels marked as Wait can no longer be edited. (When users turn on the Wait toggle of a travel record, the Edit button is no longer shown in the footer nor can they edit the travel record by double-clicking it.)	BLOC-2186
19.10.0.0	CORR	The issue of all shuttle pieces not being cut into the appropriate runs when the Create Shuttle Schedule function was applied has been fixed. The issue occurred even though the Leave Shuttle Pieces Uncut option was not selected	BLOC-2184 This task is related to FX-11509.
19.10.0.0	ENH	The issue of the Work and Pay Rules/ Piece Pay Rules/Piece Makeup parameter not including the end travel when costing has been fixed.	BLOC-2167 This task is related to FX-11332.
19.10.0.0	ENH	Improved the warning information that appears when blocks are missing block events in the selected context. When the error occurs, a warning message appears and an Error Details button in red is also now shown on the upper ribbon of the screen. Users can click the button to view details of the error. (When the data is fixed and there are no errors occurring, the button is not shown.)	BLOC-2044 This task is related to BLOC-1761.
19.10.0.0	CORR	The issue of duplicate index records in Trip times being created when created pull-ins/pull-outs are applied has been fixed.	BLOC-2209 This is related to FX-11662.
19.14.0.0	CORR	The issue of run type percentage rules that have names with special characters generating zero percentages has been fixed. Any character can now be used in run type percentage rule names.	BLOC-2213

19.1.0.0

ENH

When adding a new run type, you must fill in the Number of Operators field so that BlockBuster Web can determine how to use the run type. (This value is applied when you also have Trapeze OPS.)

BLOC-948

19.1.0.0

ENH

The User Driver Blocks property has been removed since BlockBuster Web only cuts driver blocks if used. (The driver blocks are set in Trapeze FX.)

BLOC-945

19.1.0.0

CORR

The issue of being unable to import and/or match runs from another sign-up period and runcut scenario has been fixed.

BLOC-936

19.1.0.0

CORR

The issue of login failure due to having the SSL protocol enabled for encryption purposes has been fixed.

BLOC-931

19.1.0.0

CORR

The issue of users not being able to assign new run numbers when manually runcutting has been fixed.

BLOC-1113

19.1.0.0

ENH

When attempting to copy travels, users are now prompted to confirm the action they want when there are no travels and when there are existing travels of the selected type and context to be copied. If there are travels to be copied, users are asked if they want the existing travels to be overwritten. If they click Yes, the existing travels are deleted and travels of the source sign-up period are made.

BLOC-940

19.1.0.0

ENH

The All option has been added to the Block drop-down list in the Update Reliefs screen allowing users to update all blocks that belong to the selected Line group.

BLOC-937

19.1.0.0

ENH

The issue of not being able to save any costing changes when the Override cost option was toggled Off has been fixed. (The issue occurred when using an Oracle database.)

BLOC-1188

19.1.0.0

ENH

Users can now view and select Exc Combo scenarios in the Run Scenarios screen.

BLOC-1199

19.1.0.0

CORR

The issue of Run Type violations not being shown in the Costing summary while run costing has been fixed. Any violation is now shown in red text or highlighted in red.

BLOC-1129

19.1.0.0

ENH

Runcutting with driver blocks can now be performed successfully.

BLOC-1296

19.1.0.0

CORR

Improved the performance of the Run Cost feature.

BLOC-1504

19.1.0.0

ENH

When users attempt to shift reliefs on entirely uncut blocks, the fields in the Shift Reliefs pane appear shaded and a message now appears advising them that the task cannot be performed.

BLOC-1486

19.1.0.0

CORR

The issue of multiple piece runs not being created or swapped while manual runcutting has been fixed.

BLOC-1534

19.1.0.0

CORR

The data refresh issue that sometimes occurred after applying Uncut Pieces to runs has been fixed.

BLOC-1123

19.1.0.0

CORR

The issue of duplicate run numbers being produced when runs were being renumbered has been fixed.

BLOC-1165

19.2.0.0

CORR

The Modify Standby option has been added to the Runs screen to allow users to make changes to standby times.

BLOC-1625

19.2.0.0

ENH

In the Modify Standby window, the options for Start Standby and End Standby are None, Depot, and Road. These options are equivalent to: blank, SD, and SR in BlockBuster (Legacy version in Trapeze5). If a node is a garage in either the Start or End node, the only available option in Standby types is Depot. If otherwise, the options are Depot and Road.

BLOC-1660

This task is related to BLOC-1625.

19.2.0.0

CORR

The issue of not being able to create extra pieces as standalone runs has been fixed.

BLOC-1626

19.2.0.0

CORR

The Run Scenarios grid now includes the Straights column, which shows the percentage of straight runs in the runcut solutions.

BLOC-1629

19.2.0.0

CORR

The issue of incorrect formats for the Adjusted Platform and Adjusted Break times has been fixed.

BLOC-1630

19.2.0.0

CORR

The exception error that occurred when the costing of a run, which was manually runcut, was updated has been fixed.

BLOC-1669

19.2.0.0

ENH

The User Name of the user who saved a scenario, and the date and time when the scenario was saved have been added to the Run Scenarios grid.

BLOC-1692

19.2.0.0

ENH

When users create a scenario or select one in the Run Scenarios screen, a working scenario is now also available where the users can test their changes before saving.

BLOC-1691

19.3.0.0

CORR

The issue of Run Names not being saved into a new scenario after running the Import/Export Runs feature has been fixed.

BLOC-1782

19.3.0.0

CORR

The issue of runs not appearing in a new scenario after using the Generate Exception Runs feature for a Service Group Exception Combination has been fixed.

BLOC-1777

19.3.0.0

CORR

The issue of changes to relief locations and times not showing after running the Update Reliefs feature in the Runs, View Reliefs, Manual Runcut, and Shift Reliefs screens has been fixed.

BLOC-1749

19.3.0.0

ENH

Added Load option to the Waits and Travels dialog box.

BLOC-1751

This task is related to BLOC-1767.

19.3.0.0

ENH

Improved behavior of options in the Wait and Travel dialog box:

When applying the Add or Edit options and there is only one Sequence for the Wait and Travel, users can edit the From Node, To Node and Type fields. If the Sequence value is more than 1, these fields are automatically filled in with the values of Sequence 1 of the same Wait and Travel. (There can be multiple Waits and Travels between the same nodes using different Numbers even if the Travel Type is the same for all of them because there may be different routes to get from point A to point B.)
The Sequence field is only automatically filled in.
When adding a Wait and Travel and users pick an existing Number, the Sequence is automatically set to the next available one for the record.
The Delete option is only available on the last Sequence of a Wait and Travel Number.

BLOC-1767

19.4.0.0

CORR

The issue of the Start Travel Type and End Travel Type values not being shown properly in the Run Cost screen has been fixed.

BLOC-1757

19.4.0.0

CORR

Users are now prompted to save the scenario after performing a manual runcut if they wish to save their changes. The Context field also now appears with an orange background if the changes have not yet been saved.

BLOC-1762

19.4.0.0

CORR

The following issues with the Created Pull Out and Pull In feature have been fixed:

When applied in relief locations, runs are not costed properly.
Applying created pullouts/pullins to Blocks failed when using the Apply Created Pullouts/Pullins option.

BLOC-1808

19.5.0.0

ENH

Validation messages that are shown will now include general descriptions of the issues found when Blocks or Trips data is not loaded properly. Possible issues include: less than two garage events on a block, first block event is not PO, last block event is not PI, From time of first trip is earlier than PO time, To time of last trip is later than PI time, and trip has no trip times.

BLOC-1761

19.5.0.0

ENH

Users can now move pieces into a new run by entering the run number in the Run Number fields in the Run and Block panes of the Runcut screen. After entering the run number, users must click the Apply Changes option in the drop-down menu.

BLOC-1747

19.5.0.0

CORR

The issue of runs appearing uncut after users pressed the Refresh (F5) button after runcutting has been fixed. The issue occurred after users uncut some runs in an existing scenario and then runcut them using the "Cut all and add uncut blocks" option.

BLOC-1881

19.6.0.0

CORR

The issue of manual runcutting not working on driver blocks has been fixed.

BLOC-1941

19.6.0.0

CORR

The issue of deadhead time being added to the platform time when Created pull-ins and pull-outs were used in runcutting has been fixed.

BLOC-1947

19.6.0.0

CORR

The issue of the runs being uncut when the Import from FX option in the Import/Export Runs dialog was selected has been fixed.

BLOC-1952

19.6.0.0

CORR

The issue of all runs not being exported when the Export to FX option in the Import/Export Runs dialog was selected has been fixed.

BLOC-1953

19.10.0.0

CORR

The issue of runs with forced run types not retaining the run type after the runcut was performed has been fixed.

BLOC-2013

19.10.0.0

CORR

When users enter a travel record with an error, they are now able to edit and save the record. Previously, the record would have been deleted and users had to enter the record again.

BLOC-1735

19.10.0.0

CORR

The issue of not all reliefs being created when the Update Reliefs feature was applied has been fixed.

BLOC-2039

19.10.0

CORR

A new option, Clear Active has been added to the Run Scenarios footer to allow users to cancel the selection of the current active scenario. If the selected scenario is not shown as active, the Set Active option is shown instead.

BLOC-2081

19.10.0.0

CORR

Only the run scenario that is being used in the current context and matches what is selected in the main context is now displayed in the Run Scenarios screen. These scenarios are shown with an asterisk, for example, "test1*".

BLOC-2088

19.10.0.0

ENH

The Generate Schedule and Remove Schedule options have been added to the Shuttle Schedule feature.

BLOC-458

This task is related to BLOC-2077.

19.10.0.0

CORR

The issue of the supplementary data not being updated when users generated exception runs has been fixed.

BLOC-2083

19.10.0.0

CORR

The issue of pull-outs and pull-ins not being generated when the Created Pullout/Pullins feature was applied has been fixed.

BLOC-2121

19.10.0.0

CORR

The issue of the distance in the Travels screen not being shown in the selected Distance format has been fixed.

BLOC-2110

19.10.0.0

CORR

An error message is now shown when users attempt to generate exception runs and there is no active scenario and/or no default run exception set.

BLOC-2106

19.10.0.0

CORR

The issue of users being able to mark scenarios that have not been saved as Active has been fixed. The following changes have also been made to support this fix:

A new permission, Activate Scenarios has been added to control the activation of scenarios.
User scenarios (those marked with an *) do not have update or delete options.
When users attempt to delete a scenario, the system now first checks if the scenario is an Active or User scenario. If the selected scenario is of either type, a message informs them that it cannot be deleted. Previously, the system asked the users to confirm the delete action before checking the type of the scenario being deleted. (Only scenarios that are not Active or User scenarios can be deleted.)

BLOC-2139

19.10.0.0

CORR

When users have not made changes to a scenario that they have already saved, they are no long prompted to re-save it. The prompt to save previously appeared every time users attempted to change the context of the scenario.

BLOC-2151

19.10.0.0

CORR

The issue of the desired Run Type Percentages not being calculated properly based on the run type percentage rules set has been fixed.

BLOC-2161

19.10.0.0

CORR

The issue of different values being shown for the cost of the same run in the Run Costing dialog and the Run screen has been fixed. Previously, the value in the Run Costing dialog showed the full amount while the value in the Run screen was rounded down. Both fields now show the full amount.

BLOC-2164

19.10.0.0

CORR

The issue of the Piece makeup time not being properly costed when the Start Travel is a shuttle with additional wait time has been fixed.

BLOC-2173

19.10.0.0

CORR

The issue of travels without waits being deleted when users applied the Generate Travels From Waits and Travels feature in the Travels screen has been fixed.

BLOC-2179

19.10.0.0

ENH

In the Travels screen, travels marked as Wait can no longer be edited. (When users turn on the Wait toggle of a travel record, the Edit button is no longer shown in the footer nor can they edit the travel record by double-clicking it.)

BLOC-2186

19.10.0.0

CORR

The issue of all shuttle pieces not being cut into the appropriate runs when the Create Shuttle Schedule function was applied has been fixed. The issue occurred even though the Leave Shuttle Pieces Uncut option was not selected

BLOC-2184

This task is related to FX-11509.

19.10.0.0

ENH

The issue of the Work and Pay Rules/ Piece Pay Rules/Piece Makeup parameter not including the end travel when costing has been fixed.

BLOC-2167

This task is related to FX-11332.

19.10.0.0

ENH

Improved the warning information that appears when blocks are missing block events in the selected context. When the error occurs, a warning message appears and an Error Details button in red is also now shown on the upper ribbon of the screen. Users can click the button to view details of the error. (When the data is fixed and there are no errors occurring, the button is not shown.)

BLOC-2044

This task is related to BLOC-1761.

19.10.0.0

CORR

The issue of duplicate index records in Trip times being created when created pull-ins/pull-outs are applied has been fixed.

BLOC-2209

This is related to FX-11662.

19.14.0.0

CORR

The issue of run type percentage rules that have names with special characters generating zero percentages has been fixed. Any character can now be used in run type percentage rule names.

BLOC-2213