5.1.1

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

• /

Changed

• /

Fixes

• deletes present data before creating new rows with rollback functionality(#1120)

Known Knowns

Running With Shared DTR and EDC

PURIS FOSS may not be run on a shared DTR and EDC with full scope. See Admin Guide for more information of possible scenarios.

Upgradeability

Data base migrations are performed but assets.

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 (withoutv 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 has notnot 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.

Catalog

• No action possible -> unclear to user when and how user will consume an offer

Negotiations

• Add filters for transparency (bpnl, state)

puris-6.1.1

A helm chart for Kubernetes deployment of PURIS

5.1.0

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

• Feature: Added update logic for operational information (#1069):
  • added update logic for Stock Modal (#1022)
  • added update logic for delivery information (#1004)
  • added update logic for demand Modal (#1028)
  • added update logic for production information (#1037)
  • updated user guide (#1070)
• Added component to copy text to clipboard for puris frontend (#1058)
• Added version to about license (#1067)
• Added update flow to Material Details View buttons (#1034)
• Add Update Partner Data Batch
  • Prepare backend for batch (#1105)
  • Incorporate scheduling service, controllers and test (#1106)
  • Implement frontend, cleanup scheduler and documentation (#1107)
  • Add missing frontend endpoint path in chart (#1112)
  • Fix typo in frontend endpoint path (in chart) (#1114)

Changed

• switch to ssi-dim-wallet-stub instead of own mock-util-service (now DCP 1.0 is used) (#1066)
• parametrize business partner identifiers in local deployment (#1073)
• Bump frontend dependencies (#1107)
  • rollup from 4.28.0 to 4.59.0
  • @remix-run/route from 1.14.2 to 1.32.2
  • minimatch (eslint) from 3.1.2 to 3.15
  • minimatch (eslint-plugin) from 9.0.5 to 9.0.9

Fixes

• /

Known Knowns

Running With Shared DTR and EDC

PURIS FOSS may not be run on a shared DTR and EDC with full scope. See Admin Guide for more information of possible scenarios.

Upgradeability

Data base migrations are performed but assets.

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 (withoutv 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 has notnot 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.

Catalog

• No action possible -> unclear to user when and how user will consume an offer

Negotiations

• Add filters for transparency (bpnl, state)

puris-6.1.0

A helm chart for Kubernetes deployment of PURIS

5.0.1

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

• /

Changed

• /

Fixes

• don't fail during startup if own partner already exists (#1062)
• in demo setup, skip setup if run has been performed before (#1065)
• Improved documentation, added option for persitent containers and a .env file for bruno (1024)
• fixed incorrect expected heading in E2E test suite (#1057)

Known Knowns

Running With Shared DTR and EDC

PURIS FOSS may not be run on a shared DTR and EDC with full scope. See Admin Guide for more information of possible scenarios.

Upgradeability

Data base migrations are performed but assets.

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 (withoutv 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 has notnot 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.

Catalog

• No action possible -> unclear to user when and how user will consume an offer

Negotiations

• Add filters for transparency (bpnl, state)

puris-6.0.1

A helm chart for Kubernetes deployment of PURIS

5.0.0

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 Master data page for viewing all materials and option to add material as an admin (#1044)
• added Partner table and creation modal to Master data page (#1054)
• added Material-Partner Relation table and creation modal to master data page (#1059)

Changed

• /

Fixes

• /

Known Knowns

Running With Shared DTR and EDC

PURIS FOSS may not be run on a shared DTR and EDC with full scope. See Admin Guide for more information of possible scenarios.

Upgradeability

Data base migrations are performed but assets.

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 (withoutv 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 has notnot 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.

Catalog

• No action possible -> unclear to user when and how user will consume an offer

Negotiations

• Add filters for transparency (bpnl, state)

puris-6.0.0

A helm chart for Kubernetes deployment of PURIS

4.1.1

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 detailed error messages for formulas in excel imports (#1036)

Changed

• bump spring boot from 3.5.4 to 3.5.7 (#1040)
• ci(quality-checks.yaml): configure notice file checks (#1041)
• bump dtr version to 0.10.0-RC1 (#1043)
• bump edc version to 0.10.2 (#1043)

Fixes

• /

Known Knowns

Running With Shared DTR and EDC

PURIS FOSS may not be run on a shared DTR and EDC with full scope. See Admin Guide for more information of possible scenarios.

Upgradeability

Data base migrations are performed but assets.

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 (withoutv 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 has notnot 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.

Catalog

• No action possible -> unclear to user when and how user will consume an offer

Negotiations

• Add filters for transparency (bpnl, state)

puris-5.1.1

A helm chart for Kubernetes deployment of PURIS