You can now use the newest Service SDK to comply with the requirements of personal data protection laws. This version contains a new Audit Library that integrates with the Audit Ingestion service, which helps you manage audit data in accordance with personal data protection laws.
The library allows you to create different types of audit events and asynchronously send them to the Audit Ingestion service. It also manages retries and error handling.
Here's an example use of the new functionality:
auditServiceClient.publish( AuditEventBuilderFactory .configurationChange() .serviceBasePath(serviceBasePath) .userId(userId) .source(source) .sourceType(SourceType.ACCOUNT) .time(timeStamp) .addConfigurationChange(dataName, oldValue, value, AuditEventOperation.CHANGE) .objectId(objectId) .objectType(objectType) .build(), new DiagnosticContext(requestId, hop));
Read more about the Audit Library here.
Support for the new
YaasAwareTrait class in the Pattern Support Library now contains a constant that corresponds to the new header.
The Logging Library logs the contents of MDC logging context, which the Logging Filters Library automatically fills with the value of the
hybris-user-id header. When you use the newest Service SDK with both libraries, they propagate the new header, just like they propagate the old
The Service SDK still supports the old
Library versions are updated, including the Spring and Spring Boot versions
1.5.6.RELEASE, respectively. Please update the versions in your project accordingly to avoid Maven conflicts and unpredictable behavior at runtime.
An issue with using the Logging Library with Scala is resolved.
If you find any information that is unclear or incorrect, please let us know so that we can improve the Dev Portal content.
Use our private help channel. Receive updates over email and contact our specialists directly.
If you need more information about this topic, visit hybris Experts to post your own question and interact with our community and experts.