Description Provide possibility to create a CustomerCreationContext via API. The CustomerCreationContext was introduced in ICM 7.10: CustomerCreationResult createCustomerBO(CustomerCreationContext context) At the same time, the existing signature in the CustomerBORepository to create a new CustomerBO

Description Actual behavior: Enable Organization Hierarchies service in Managed Services but with wrong Endpoint. Then go to a SMB Customer > Users and click New. Enter the mandatory values and click Apply. User is not created, no green message that an e-mail has been sent, no error message indicating

Description Description: customer has configured Azure b2b AD They login into the backoffice via the OIDC feature Steps to repeat: I log into the Edit system with AD. Backoffice user is created. I replicate the user to the live cluster When u try to then login to the live cluster u get the attached error

Description Missing default parameter lead to long time loading page Description: The pages called by ViewChannelLink*.pipeline load very long in case the pipeline lacks parameters Investigations: <configurationValues name="Recursive" value="false"/> <configurationValues name="UnitDirectory" value="IMPEX_DIR"/>

Description Actual behavior: Enable Organization Hierarchies service in Managed Services but with wrong Endpoint. Then try to create a new user of existing SMB Customer - endpoint: https://host:port/INTERSHOP/rest/WFS/inSPIRED-inTRONICS_Business-Site/-/customers/ {CustomerID} /users User is not created

Description Current Behaviour: User with permission to cancel an order assigned to internal supplier still fails because of missing permission validation. Note: run test 9210-02 and see, that the validator fails for the cancellation because of missing permissions... Repro Steps Current Behaviour: User

Description Current Behaviour: NPE in OMT when trying to save modified cancellation Steps to Repeat: Create an order Cancel the order with erroneous data via WebAPI, f.e. with more items than ordered See an erroneous cancellation in OMT Open the modal to edit, correct the data, save See NPE More: run

Description A payment using an asynchronous flow of AutoCapture may stuck in "Captured (Pending)" when a FAILURE Notifcation comes in. Reason: State transition from CAPTURED to AUTHORIZATION_VOIDED is not allowed. Status is not updated. Repro Steps A payment using an asynchronous flow of AutoCapture

Description Description: Promotion imports will lead to audititem table entries w/o DOMAINREF, OBJECTTYPE and OBJECTREF information ( null values ) Steps to repeat: - setup ICM system with enabled audit feature inside appserver.properties intershop.auditing.enable=true intershop.cartridges.bc_auditing

Description Steps to repeat: generate OpenAPI model of REST API auth resource /users/processtoken Actual result: descriptions of HTTP response codes (besides other texts) are missing Expected result: descriptions from file /bc_platform_rest/src/main/resources/resources/openapi/UserTokenResource.properties