Skip to content

2.0.1
Compare
Choose a tag to compare
@tom-rm-meyer-ISST tom-rm-meyer-ISST released this 27 May 06:50
· 329 commits to main since this release
2.0.1
c043892
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

The following Changelog lists the changes. Please refer to the documentation for configuration needs
and understanding the concept changes.

The need for configuration updates is marked bold.

Added

  • Added Footer

Changed

Frontend updates

  • Labels are now above and not on the border of elements
  • updated icons for catalog, negotiations, transfers, logout
  • Font update for Role switching elements in stocks and dashboard view
  • Handled modal dialog behavior to always let failed validations prevent closing
  • Modal Dialog Demand
    • Day is marked as mandatory
    • Reset data when reopening
  • Catalog View
    • Updated header itle + usage policy naming (previously Asset Action)
    • Added table view
    • increased responsiveness by loading animation
  • Negotiation view
    • Added table view + Subheader
  • Logout button now logs out again

Fixed constraints to exactly match on leftOperands during consumer side offer evaluation

Removed

  • EDR Endpoint as removed for edr api usage in appVersion 2.0.0

Known Knowns

Security

The Backend is currently secured via API Key while the Frontend already uses an API-KEY.
See Admin Guide for further information.

Upgradeability

As currently no active user was known migrations of data are not yet supported. The chart technically is upgradeable.

Data Sovereignty

For productive use the following enhancements are encouraged

  • User FrontEnd available: Role Company Admin is able to query catalogue and see negotiations and transfers
    But company rules / policies need to be configured upfront in backend (via postman) to enable automatic contract
    negotiations, responsibility lies with Company Admin role
    --> add section in the User Manual describing this and the (legal) importance and responsibility behind defining these
    rules
  • Currently only one standard policy per reg. connector / customer instance is supported (more precisely one for DTR,
    one for all submodels), negotiation happens automatically based on this
    --> enhance option to select partner and define specific policies (to be planned in context of BPDM Integration)
    --> UI for specific configuration by dedicated role (e.g. Comp Admin) and more flexible policy configuration (without
    code changes) is needed
  • As a non-Admin user I do not have ability to view policies in detail --> transparency for users when interacting with
    and requesting / consuming data via dashboard / views on underlying usage policies to be enhanced
  • ContractReference Constraint or configuration of policies specific to one partner only not implemented -->
    clarification of potential reference to "PURIS standard contract" and enabling of ContractReference for 24.08.
  • unclear meaning of different stati in negotations --> add view of successfull contract agreeements wrt which data have
    been closed
  • current logging only done on info level --> enhance logging of policies (currently only available at debug level)
  • in case of non-matching policies (tested in various scenarios) no negotiation takes place -->
    enhance visualization or specific Error message to user
  • no validation of the Schema "profile": "cx-policy:profile2405" (required to ensure interop with other PURIS apps)

Styleguide

Overall

  • Brief description at the top of each page describing content would be nice for better user experience.

Dashboard

  • Create Demand
    • Upon entering data and closing, SOME (not all) entries are preserved (and so are warnings for mandatory fields) --> upon closing and re-opening information should be reset to default
    • UOM fields have different opening behaviors. Some have a default like pieces, some have a "Select unit" (preferred)

Stocks

  • user needs better guidance to click on a stock to update it (else error prone to enter one
    slightly different attribute and Add instead of update)
  • Refresh -- update request has been sent successfully. -> more information regarding data transfer needed for user

Catalog

  • No action possible -> unclear to user when and how user will consume an offer
  • Rows can be selected but not deselected

Negotiations

  • Add filters for transparency (bpnl, state)
Assets 2
Loading