Description Adding an expanded value to SalesPriceCalculatorBeanDefDO will result in an exception and stop the further checks of the expanded enum values during the deployment, without stopping it though. background: the enum check does not cope with name differences between the java attributes and the

Description The rebuild of the stored procedures that takes place during the migration contains some drop/create trigger statements. (background: there is no create trigger IF NOT EXISTS... statement in postgres.) It appears that these statements require an exclusive table lock which may cause dead locks

Description Steps to reproduce the bug: Prepare database: BEGIN; -- Event registry configuration --> Trigger Mail Event Manager INSERT INTO "EventRegistryEntryDO" ( "id","creationDate","modificationDate", "processesRef","version", "eventDefRef","shopRef","description") SELECT nextval('"EventRegistryEntryDO_id_seq"')

Description The OMT has no direct support for product shop name aliases. It display such aliases instead as a comma separated list. Trying to edit such a product leads to an exception (stack trace attached, in "log"): java.lang.NullPointerException: Cannot invoke \"bakery.persistence.viewobject.article

Description This might be a new bug introduced with the fix of #93998 steps to repeat: Configuration: no use of hierarchical stocks shop 1 bound to supplier 1 and supplier 2 BC files for supplier 1 only Create order with order approval (supplier 1) Check the evaluations in OrderSupplierEvaluationDO:

Description Configuration: shop 1 (supplier 1 and supplier 2) (Shop2SupplierDO are active) |_> shop 2 (supplier 1 and supplier 2) (allowParent=true) (Shop2SupplierDO are not active) |_> shop 3 (supplier 1 and supplier 2) (Shop2SupplierDO are active) product data and inventory A and N files for shop 1 and both supplier

Description A null value in Shop2SupplierDO."allowParentStock" will cause a jpa error when loading the entity as the setter/attribute expects a primitive boolean. The database column should hence be defined as not null (it has already a default set to false). Otherwise such errors will be triggered:

Description Configuration: shop 1 (supplier 1 and supplier 2) (Shop2SupplierDO are active) |_> shop 2 (supplier 1 and supplier 2) (allowParent=true) (Shop2SupplierDO are not active) |_> shop 3 (supplier 1 and supplier 2) (Shop2SupplierDO are active) product data and inventoryA and N files for shop 1

null User Story null Acceptance tests pass Closed null Major AdoWorkItem 91101 Release Products Products 91106 Parent 91114 Related iom-testframework/4.5.0 iom/4.5.0

Description When selecting potential suppliers , the DOSE process does not check if there is a corresponding active Shop2SupplierDO. (boolean Shop2SupplierDO.active) This may lead to order position being mapped to suppliers which are not visible at other places, like e.g.in atp responses. As a severe

Description @Alexander Rossudowski https://nvd.nist.gov/vuln/detail/CVE-2024-1597/change-record?changeRecordedOn=02/19/2024T08:15:07.740-0500 IOM is not affected in any way, as it is not using PreferQueryMode=SIMPLE. Nevertheless, in order to anticipate questions from our customers, the jdbc driver will

Description Configuration:shop 1 (supplier 1 and supplier 2) |_> shop 2 (supplier 1 and supplier 2) (allowParent=true) |_> shop 3 (supplier 1 and supplier 2) product data and inventoryA and N files for shop 1 and both supplierBC files for shop 1 and both supplierBC files for shop 2 only for supplier

Description Orders stay stuck in state DO_OPTIMIZE. This issue only affect installations NOT using the hierarchical stocks (https://intershop.atlassian.net/wiki/spaces/ENFDEVDOC/pages/48479109423/Concept+-+IOM+Hierarchical+Stocks+Visibility) This is caused by a syntax error in a postgres trigger function:

Description Editing the stock results in a Null pointer exception when the shop article No is empty in the formular. This is the case when the A/N product files where imported at a higher shop level thna the stock to be edited. Actual Behavior Expected Behavior Allow the stock editing in OMT in this

Description In IOM 4.1 countries were added to be supported by IOM. At least for "Falkland Islands" localization values are missing. Expected Behavior check all countries known in IOM. bug fix: added names for 137 countries null Bug null Verified Closed null Major AdoWorkItem 93367 Products Products

Description Due to a missing error check some files that get moved to share/importarticle/error are then immediately moved again to the share/importarticle/done folder Steps to Repeat define an article csv file for an non existing shop-supplier relation and start the import. An error like following is

Description When the article fact data (A and N import files) are defined in a higher level than the stocks within the shop hierarchy, then reserved and blocked quantities may be overseen. The issue does not affect installation using reseved stocks. (see doc on Shop2SupplierDO.allowParentStock) Steps

Description When creating new return requests via the RMA API, the request has to include a customAttributes field on header level, otherwise a 500 server error code is returned. The field is not marked as required in the API definition and should therefore not be mandatory. Failing request example:

Description see task number in code null Bug null New New null Major AdoWorkItem 92460 Products Products iom/5.0.0

null Bug null New New null Major AdoWorkItem 92464 Products Products iom/5.0.0