Skip to content

2.0.2

Compare
Choose a tag to compare
@tom-rm-meyer-ISST tom-rm-meyer-ISST released this 05 Jun 11:32
· 255 commits to main since this release
c2d02c5

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 backend implementation to CRUD Demand and Capacity
    Notifications (#415)
  • Added ERP response interface (#418)

Changed

  • Fixed check when answering delivery information request from a customer which prevented always to
    answer (#435)

Removed

N.A.

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

  • Similar for Create Delivery (here SOME entries are reset but warnings stay) (block)

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

Negotiations

  • Add filters for transparency (bpnl, state)