Test Alpha Version

[fhomberg]

Overall feedback

• [x] Include version numbers in the UI so that the feedback can be tracked by version
• [x] Change order of sections to: 1=General information, 2=Discount Models, 3=Signatures

Contract View

• [x] Actions column: Remove for now
• [x] Create space for general workspace configuration: Implement TADIG grouping function @sgerhardt-trilobyte
• [x] Adapt columns to template T3 on Github: https://github.com/GSMA-CPAS/BWRP-UI/issues/40#issue-755980587 - but without listing all TADIGs. Instead: Don't list TADIGs but make search by TADIG possible in the contract view. Use TADIG list from the common adapter.

General information:

• [x] Contract Date: Not possible to enter specific day, e.g. 31.12.2020 or 2020-12-31. Should be possible.
• [x] Contract type is useless for the alpha, can be removed (might be requested in the future)
• [x] Contract parties check box is useless for the alpha, can be removed (might be requested in the future)
• [x] Format of the values shall be represented with a thousands separator (Space)
• [x] Decimal character is a dot '.'
  Ex.: value = 123 456.78
• [x] Currencies pre-defined for the selection could be limited to EUR, GBP, USD Note that once the currencies are selected, the selection will be pre-provisioned (cfr discounting models)

Signatures:

• [x] Role field should be pre-populated with e.g. (user, administrator, viewer ...)
• [x] Partner names (DTLABMSP / ORLABMSP) are difficult to see on screen. Should have a different color. Alternatively, the color of the heading description (SIGNATURES) could be made in lighter grey.

Discount Models:

• [x] Most agreements are symmetrical (conditions are the same for both parties). It should be possible to only fill in e.g. the left side of the agreement and then copy it to the other side. Would avoid having to enter things twice.
• [x] Partner names (DTLABMSP / ORLABMSP) are difficult to see on screen. Should have a different color. Alternatively, the color of the heading description (DISCOUNT MODELS) could be made in lighter grey.
• [x] Copy function: Should be possible to only fill in the left side (own conditions vs. partner) and copy it to the other side (except for the TADIGs).

Contract Revenue Commitment

• [x] Value field: Numbers should have separation of 1000s
• [x] Currency: Could be pre-filled with currency of agreement selected earlier. If a different currency than the contract currency is entered, a validation window could occur, e.g.: "The currency for the revenue commitment differs from the contract currency. Are you sure?"

Services

• [x] Service list to be checked. Should contain the list of default services collected here #29
• [x] Standard services are defined here: StandardServices_01.xlsx Units linked to the services are enclosed in the file above, it shall be use to -pre-fill fields when the service is known.
• [ ] Should be possible to add new service to overall list

Usage pricing model

• [x] Adapt list to the list of most common discount models:
• Flat rate (independant of the volume)
• Linear rate
• Threshold - back to first
• Tiered with Thresholds
• Balanced/unbalanced (Linear rate) The current UI models are missing the 'To' thresholds. (Threshold back to first models are not correctly supported in the UI)

Unit

• [x] pre-fill unit depending on service selected according to the file Standard services (here above)

Rate

• [x] Include 1000s separators for numbers
• [x] Not possible to indicate whether a tiered charging model is incremantal or "back to first" > must be possible!

Access pricing

• [x] Shall only be present for M2M, NB-IoT and LTE-M services (default unit is IMSI count)

[fhomberg]

@andswk @Pad-135 @zkong-gsma: I started collecting issues for the current alpha version here ...

[hochbergg]

@fhomberg @Pad-135 "Should be possible to add new service to overall list" - I'm not sure what this means in the context of discount agreement services. Should I allow any service the user wants to type in even if its not on the list?

[Pad-135]

@fhomberg @Pad-135 "Should be possible to add new service to overall list" - I'm not sure what this means in the context of discount agreement services. Should I allow any service the user wants to type in even if its not on the list?

Hi Gal, I think you can skip it for now (no additional services foreseen on top of the standard services). We agreed for now to focus only on services defined in the xls sheet above - Standard services.. Tx.

[fhomberg]

@hochbergg @Pad-135: It means that right now we have services like MOC, SMS, Data ... for which we can configure discount schemes. This service list should be part of the workspace and configurable so that we can add new services like LTE-M, ViLTE etc. if required. But Pascal is right: If this is too much effort - we leave this for later. Thank you for checking back Gal!

[hochbergg]

@fhomberg @Pad-135 Thanks for the quick response! The way I'm implementing it is that in the future we could make it part of the workspace, but right now its a static list in the frontend.

[hochbergg]

@fhomberg @Pad-135 regarding "To" thresholds, they were removed as its easy to create inconsistent models with them - you must have each "To" field be equal to the "From" field after it, or your model is not well defined.

What did you mean by re-adding "To" fields?

[hochbergg]

PR for UI fixes available here: https://github.com/GSMA-CPAS/BWRP-UI/pull/55