Core 2.0.759

We are introducing a new setting which is required for all customers which integrate with Infrasec in Sweden.

• Auditing:Sweden:Shop:Number

This setting must be filled in for per OU operating in Sweden with a 4-digit number. This number is based on your OUID and should be prefixed with 0 to reach 4 digits..

For example. Your OU ID is 48. The value you put in this setting is 0048.

While New Black will be migrating all customers this currently applies to in Production environments, customers using it in Test/Acceptance will have to do so themselves.

Generating PDF Invoices for B2B Transactions in Romania​

Store operators in Romania can now generate PDF invoices for B2B transactions, essential for reporting to ANAF with unique and sequential invoice numbers.

• Automatic PDF Generation: A PDF invoice is generated for B2B orders alongside the fiscal receipt, which can be printed or emailed.
• Invoice Numbering: Uses a custom format: OU-999-XXXXXXXX for B2B transactions.
• B2B Customer Criteria: Requires a company name, VAT number, and billing address.
• Fiscal Receipt Reference: Includes a reference labeled Referință bon fiscal.
• Template: The CertifiedInvoice is used a basis, but translated to Romanian.

Note: Manual reporting to ANAF is still required.

The GetAvailableSettings service now returns functionality data for each setting, as matched and announced in our recent batches of Core drops.

Users will no longer be able to see only functionalities limited to what's already active on their OU, but all settings related to a functionality instead.

The update introduces two new properties: ManualUserIdentifiers and ResubscribeHandling, which are necessary for manually entering user identifiers within the App.

• Scenario Handling:

  • Scenario 1: When changing a subscription status from subscribe to unsubscribe, the subscription identifier will not be displayed.
  • Scenario 2: If ManualUserIdentifiers is set to true, subscribing requires a manual identifier. Depending on the ResubscribeHandling value:
    • (0): The user identifier is updated.
    • (1): The original user identifier is retained.
    • The app will automatically display an input view, requiring users to enter the identifier to activate the subscription toggle.
  • Scenario 3: If the subscription is set to block (i.e., ResubscribeHandling is 3), it cannot be edited, regardless of the ManualUserIdentifiers value.
  • Scenario 4: When ManualUserIdentifier is false, and changing status from unsubscribe to subscribe:
    • If ResubscribeHandling is (0) or (1), the App displays the automatically generated subscription identifier as is.

  This update enhances the App's flexibility and user control over subscription identifiers, making it easier to manage subscriptions without additional API calls.

What Has Changed​

Introduction of ShipmentIdentifiers Config Object
This new object allows the configuration of shipment identifiers, which are necessary for tracking and managing shipments effectively.

• Types and Properties

  • Types: Two types of identifiers have been introduced:
    • 0 (crate)
    • 1 (seal)
  • Flag Property RequiredFor:
    • This property determines whether scanning is mandatory. Current values are:
      • 0 (none) - Scanning is not required.
      • 1 (RTS) - Scanning is required for Ready to Ship (RTS) processes.

• CRUD Services

  • New services have been added to manage these identifiers:
    • CreateShipmentIdentifier
    • UpdateShipmentIdentifier
    • DeleteShipmentIdentifier
    • ListShipmentIdentifiers
    • GetShipmentIdentifier

How to Use​

• Creating Identifiers: Use the CreateShipmentIdentifier service to add new identifiers. Specify the type and set the RequiredFor flag as needed.
• Updating and Deleting: Modify existing identifiers using UpdateShipmentIdentifier, or remove them with DeleteShipmentIdentifier if they are no longer needed.
• Listing and Retrieving: Use ListShipmentIdentifiers to view all configured identifiers and GetShipmentIdentifier to retrieve specific details about an identifier.

What's Changed​

The latest update introduces the capability to filter event exports by user agent. This means you can now specify which user agents (browsers or devices) you want to include or exclude in your event data exports. This functionality is particularly useful for targeting specific platforms or isolating data from unwanted sources.

Technical Details​

• The EventExport extension point now includes the UserAgent property.
• Inclusion and Exclusion: The flow allows both inclusion and exclusion filters.

Available properties​

• UserAgent
  • .Name
  • .Version
  • .Stage
  • .Details
  • .Raw

Note: This UserAgent.x in the script uses the EVA-User-Agent of the request, not the regular User-Agent

extend EventExport
set export to false
if UserAgent.Name = 'EVA-TestSuite' then
  set export to true
end
output export

What's Changed​

• CustomFields in Data Object: The Data object now includes a CustomFields array with objects containing an ID and an IsValid property.

"Data": {
  "IDs": [616, 617],
  "CustomFields": [
    {"ID": 616, "IsValid": true},
    {"ID": 617, "IsValid": false}
  ]
}