Version 2.10.0 Changes

Content

DATE

2020.12.23 - PCS EC version 2.10.0 was deployed on production, test1, test3, and test4.

CHANGES/FIXES

  • Dossier wizard: Change of validity period is not saved
  • Fix issue with required time when pap is used in the subpath. Meaning Make sure that the required time is handled correctly when the user edits the subpath with PaPs.
  • Remove duplicate dossier archives. We have duplicate dossier archives in the dataBase. In most of the systems, the archives belong to PaPs. The reason for this is that we are receiving the same update request multiple times at the same time. To overcome this problem, we can add a unique constraint for the change number per dossier archive.
  • Excel import error improvements:
    • Throw Validation exception when:
      • All columns of a row are empty
      • The 'Null' row is encountered
    • Show errors in the following cases:
      • The PaP doesn't contain path sections or it contains only one
      • Duplicate locations (primary location code or name)
      • Duplicate directions
  • Implement excel import by the new template
  • Copy times - copy public/earliest/latest times. When the user applies the copy times option, he/she shall have the possibility to include the public/earliest/latest times in the copy. Earliest/latest and public times should be visible all the time.
  • Include Catalogue path number and Path number to PDF export
  • Parameter changes for removed values too - backend. Meaning showing the added and changed values are already implemented. Regarding the removed values, PCS will show the removed parameter with its value as strikethrough. The change will also be included in the PDF export. Note: In the presentation model we should add information for the type of change (remove, insert/update) and removed value.
  •  Parameter changes for removed values too - frontend. In the view, the removed parameters should be shown with their value as strikethrough.
  • Implement excel reader. Implement a general excel reader that reads and parses data from an excel document. The purpose of this reader is to parse the excel document, validate the data inside the cells, and produce a new intermediate result which later will be used to create the actual domain models. Also in case of validation errors, it needs to produce an appropriate result that will contain all errors and their corresponding row and cell numbers. The reader should support the processing of multiple sheets. To allow declarative processing of the data inside the excel document, we can create some kind of a composite structure and a builder to simplify the creation of the structure. For each cell, we can have basic data validation such as number, required, email, data, etc. The validation of the data consistency will be done after the input is parsed. This way we can have a specialized cell parser that can parse and validate a single cell and return parse results. The result may contain the data if it's parsed successfully or an error if it can't parse the data. The parse result should contain a row and cell number so we can use the latter while parsing the intermediate result.
  • Error handling. Keep all errors in an object that can be returned to the client in order to fix the errors. We will have three types of errors:
    • Parse Errors: Invalid cell data
    • Data Errors: Errors that can be fixed in the wizard (OperationPoint, LocoType, ActivityType, Parameter)
    • Data Warning: they can be ignored in the wizard. (OperationPointNotResolved, OperationPointInactive...
    • The parse errors will be detected early when parsing the excel document. And only when there are no parse errors, we can validate the structure further. To detect fixable errors, we can validate the intermediate result and validate the fields that can produce these kinds of errors.
  • Validate and save the intermediate result
  • Test excel import: Define excel test cases and check them in the application.
  •  Add comments in the PDF. In the PDF Export options add Comments in order user to decide what he/she wants to do. Fetch comments for export in the case when export option Comments is selected (take into account ACL rules - if the user is able to see given comments). Implement comment in PDF service - comments should be shown in the same way as we show them in UI
  • Last days of TTP: In case when we have a sub-path that does not belong to the last territory and the sub-path is running only on the last day of TTP and has an offset - the destination should be marked as an alternative destination
  • Cleanup the old excel import: delete all models and services that are used in the old import.
  • Import Slovakian translations
  • Pap import - fix errors
  • Pap import - persist pap dossiers
  • Define Direction on Dossier level
  • Validate that PaP import is working. Make sure that the async process for PaP import is started. Make sure that all data is converted and persisted properly.
    • What to check:
      • Existing Parameter Set Codes are updated, new is not created
      • Existing Distances are updated, new is not created
      • Existing Dossiers are updated, new is not created
  • Replace Catalogue prefixes on the application level with Pap prefixes. All application services, converters, models related to pap import should have Pap prefix. Make sure that adjustments are made on the frontend too.

(PCS EC Sprint 64 created to this release notes)