Improving Integration and fixes for Orders and Payments

Explore a number of improvements that significantly enhance and optimize integrations:

• Ensure accurate destinations for courier services by specifying

  `street2`

  for Return Orders, Fulfillments, and Billing Accounts, eliminating the risk of invalid address failures in return label booking.
• Adapt your return processes to digital product specificity with an email address available for the Return entities mentioned above, bringing address information consistency within the Order domain.

📖 Get step-by-step instructions for Return Order creation with an extended address in the Configuration Guide.

• Create Orders across multiple Retailers with a single integration user, simplifying and accelerating cross-retailer order management and related integrations. Previously, the Order creation was tied to the particular primary Retailer of the user.
  Activate and manage this feature with a correspondent

  `fc.graphql.order.create.event`

  setting.

📖 Get step-by-step instructions in the Setting Editing Guide.

• Store and update a Fulfillment Estimated Time of Arrival (ETA) in the way you need for any scenarios when the standard pattern

  `\d*([H|D]?)`

  is not applicable, using the complete flexibility to meet any specific requirements.
  This restriction removal is a fully backward-compatible change, and as previously, the data transformations will be executed for all the ETA inputs following the reference format.
• And fixes for:
  • Overwriting of existing Payment entity attributes via the Update Payment mutation.
    Now, the original attributes not specified in the update request remain untouched and will not be lost, ensuring a consistent update mutation behaviour.
  • Financial Transactions created as part of the Create Order mutation now contain workflow Reference and Version essential for GraphQL operations, leading to equal to Create Financial Transaction mutation behavior.
  • Data fetching errors while using Create Network mutation with multiple Retailers input, eliminating duplicated entities in the response.
  • Concurrency issue when multiple

    `NO_MATCH`

    Events are sent to the same Workflow at the same time. 

Returns Module

• The Address has been extended with

  `street2`

  and

  `email`

  for Return Order, Return Fulfillment, and Billing Account entities at Database and GraphQL levels.

Order Domain

• The GraphQL API has been extended to allow creating Orders independent of the primary Retailer of the user creating the Order. Previously, Orders could only be created for the user's primary Retailer.
  The ACCOUNT level

  `fc.graphql.order.create.event`

  setting with

  `normal`

  and

  `disable-cross-retailer`

  possible values has been introduced to activate the feature.

• `eta`

  field validation by

  `\d*([H|D]?)`

  pattern has been removed for the Fulfillments, allowing to set it as a date or use other formats.

Bug Fixes (Mutations and Orchestration Engine(Rubix))

• `updatePayment`

  mutation has been fixed to merge attributes instead of overwriting.

• `createOrder`

  mutation has been extended to add

  `workflowRef`

  and

  `workflowVersion`

  to the Financial Transactions created. 

• `createNetwork`

  mutation with multiple Retailers input and the related GraphQL queries (

  `network`

  ,

  `networks`

  ,

  `networkById`

  , and

  `retailerById`

  ) have been fixed to eliminate duplicated Network entities while fetching data.

• `NO_MATCH`

  Events concurrency issue has been fixed with a new array initialization, eliminating the simultaneous contrary operations against the same data array.

• Order creation across multiple Retailers feature requires activation as fc.graphql.order.create.event setting value is set to "disable-cross-retailer" for all the customers