20.11.03 Briefing Note

The sections below detail enhancements that will be deployed to acumen on the evening of Saturday 5 December 2020.

Users will need to clear the Chrome Browser cache (hard re-load) in order that the changes made to acumen function correctly. Instructions on how to do this can be found on the FAQ page.

The relevant User Guide pages will be updated in due course.

New Functionality

Drag & Drop - Platform Change

In addition to accessing platform re-plan options from the right-click context menu, users can now initiate a platform change within acumen simply by clicking on the train and dragging it to a different platform.

The drag feature is constrained to the platform axis so users do not need to worry about maintaining the arrival or departure times whilst they drag.

To enable the drag feature, a user must hold down the Alt key and then click on the train. The train will then display as faded as per 9M28 below. (The Alt key can be released once the train has been clicked on.)

Once in the drag mode, the train can be clicked on and pulled to another platform.

Its original position will be coloured white with a red outline for reference, as seen below.

Note: The option is provided to select multiple trains. To do this, hold down Alt as multiple trains are clicked on. They all then appear faded and can be dragged to new platforms as described above.

Once the train has been released, or dropped, a dialogue box pops up to confirm the change.

Note: An exception to this is if the train is moved to or from the TBC platform. In this case the re-platform processes immediately without need for the pop-up confirmation.

Note: The option is included to suppress the confirmation pop-up box for all platform changes. Users can turn this on and off via the Docker Viewing Preferences.

While the change is being processed and as part of the browser refresh cycle, you will temporarily see the coloured train return to its existing platform. The white box will indicate where the train is moving to. After approximately 5 seconds, the train will render as normal in its new platform.

As per standard platform changes:

• a (P) icon will be added to indicate the change,
• any associated outbound service will also move to the new platform,
• conflict detection will run so occupation conflicts, infrastructure restriction conflicts etc will be raised as applicable,
• the new platform will display in the Train Details View,
• the replan action will be recorded in the Alerts tab.

Note: The drag and drop feature recognises 'full' platforms only. Users are guided to use the right-click context menu if they wish to re-platform the train to a sub platform.

Note: While the drag feature is enabled (Alt has been pressed) the docker will not refresh. Therefore if a user decides not to undertake a platform change, they should either:

• hold down Alt and click the train again,
• drag the train away and then back to its original platform, or
• refresh the page.

Note: This functionality is not available on a mobile device.

Text Clipboard

Users can now right click on a platform change (P) icon to reveal a convenience feature that allows details of platform changes to be copied to other documents, such as a log or email.

This enhancement is following a request from Birmingham New Street SSMs who are required to keep a log of changes.

For example, below we see that a user has right clicked on the (P) icon for 1S52, and has been presented with the platform change information.

To copy the text, click on the pencil icon; the text is automatically copied to the clipboard and can therefore be pasted [CTRL+V] to any document as desired.

Bug Fixes - NIGEL CHECK PLEASE

JON IS WORKING ON BUG FIXES THIS WEEK. INFO ON GITHUB. RELEVANT ONES (AKA WHERE USER WILL NOTICE AN IMPROVEMENT) CAN BE LISTED HERE

These bug fixes have been pushed to the training and production servers since the 20.11.02 hot fix.

Split associations

The 20.11 upgrade introduced workarounds to improve how associations inferred by POINTA were displayed, and remove illogical associations from the docker. See 20.11 Briefing Note for more information.

However, where false split associations were removed from the docker, some split association conflict icons remained. An example is shown below.

Connection Editor

Improvements have been made to the formatting of the Connection Editor to ensure users can see the full list of available headcodes generated by the predictive text when searching for a headcode to connect.

Conflict Marker

The docker was not consistently displaying the yellow triangular conflict marker for all conflicts. This has been addressed.