Description Description: The customer described this behavior: I have another bug fix/improvement for the OIDC integration. I have noticed that any exception that is thrown in a mapper or other Features are just swallowed. Example: public class SomeProfileapperImpl implements OIDCProfileMapper, TokenFeature<UserInfo>

Description Current Behavior The number does not always exists, e.g. with POBox or when streetname and streetnumber are saved together in street attribute. When such an order address is copied as customer address, editing it in the customer section is not possible without setting a number. Expected Behavior

Description REST call post /customers/<CustomerKey>/punchouts/<PunchoutKey>/users request body: { active: false, email: "punchout@test.intershop.de", login: "punchout@test.intershop.de", password: "!InterShop00!" } Current behaviour call returns with new user, but active flag equals true response body:

Description Description: When you configure a search filter with "Filter Mappings and Explicit Sorting of Values" you can use the "Populate Values" button to populate the mapping. However, if a new value is introduced, but no mapping is defined then a NPE is thrown and the filter navigation is not displayed

Description Description: When setting the intershop.session.TimeOut to a big value like 999999 minutes then there are errors in the backoffice like "Your session has been closed for security reasons, probably because you did not use the system for over -2160 min." Also errors in the error log can occur:

Description To change the payment method for a recurring order via REST, the old payment method must be removed first. After doing so, trying to add a new payment method returns an error. Removing the payment method has also a bad impact on the OPTIONS call. Before removing, the payment options are returned

Repro Steps Configure the shop to wait a while, so the bucket address can be edited in OMT. The validation rule (next point) must be executed syncr. before. Place an order via REST with a shippingAddressType AddressLocationPOBox(the shop must be bound to the OrderValidationRuleDefDO VALIDATE_SAVE_CUSTOMER

Description current behavior It is not possible to place an order using a POBox as shipping address type, when the address should be copied to the customer (through OrderValidationRuleDefDO.VALIDATE_SAVE_CUSTOMER). The customer address validation expect a street, which not exists for POBoxes. expected

Description Current Behaviour: Positions are not sorted somehow within a shipping bucket when listed in OMT or when returned by persistence-service. Expected Behaviour: The positions should be sorted according to the OrderPosDO.orderPosNo-/number-attribute. Repro Steps Current Behaviour: Positions are

Description Current Behaviour: a technical exception is thrown when trying to save a corrected return/ cancellation message in OMT Expected Behaviour: no exceptions and finally a stored corrected message Repro Steps Current Behaviour: a technical exception is thrown when trying to save a corrected return/