Release Notes | YaaS Dev Portal

Builder

Thu Dec 07 2017 00:00:00 GMT+0000 (UTC)

New General Data Protection Regulation views

This release includes views for GDPR management. Now, you can manage, inspect or delete your data or data belonging to your end customer following the General Data Protection Regulation.

hybris techne v1.5.9

Tue Oct 31 2017 00:00:00 GMT+0000 (UTC)

Patch Release

This is a patch release to fix NPM package delivery. Bower component dependencies are now excluded as they were causing issues with npm shrinkwrap from locking down version numbers.

Service SDK 4.17.1

Wed Oct 11 2017 00:00:00 GMT+0000 (UTC)

Dependency updates

Library versions are updated, including the Spring and Spring Boot versions 4.3.11.RELEASE and 1.5.7.RELEASE, respectively. Please update the versions in your project accordingly to avoid Maven conflicts and unpredictable behavior at runtime.

Resolved issues

An issue with using the Audit Library, in which the service-sdk-audit-base library was missing in Maven central, is resolved.

hybris techne v1.5.8

Tue Sep 19 2017 00:00:00 GMT+0000 (UTC)

Patch Release

This is a patch release to fix icon rendering issues there were released in previous version 1.5.7

hybris techne v1.5.7

Tue Sep 19 2017 00:00:00 GMT+0000 (UTC)

Additional Icons

This release contains some additional icons. These Icons are used for an internal library for Enterprise Commerce platform, and not meant for external use.

Builder

Mon Sep 18 2017 00:00:00 GMT+0000 (UTC)

This release includes extended definitions for authorization rules.

Improved authorization rule definition

Now, you can extend authorization rules to include a list of projects (tenants) that have permission to use the resources matched by the rule. Previously, authorization rules were only defined using methods and required scopes.

There are more changes and improvements on the way. Check back soon for the latest updates.

SAML2 Adapter v1

Fri Sep 15 2017 00:00:00 GMT+0000 (UTC)

The SAML2 Adapter service allows you to create and register custom SAML 2.0 identity providers for your projects and organizations.

By creating and registering custom identity providers, you can enable your customers to access your organization's resources in YaaS without the need to create new accounts.

The SAML2 Adapter service allows you to:

Get the technical information required to establish a successful connection between your custom SAML 2.0 identity provider and the YaaS OAuth2 service.
Register your custom SAML 2.0 identity provider and obtain its identifier.
Manage the custom identity providers registered for your organization. You can fetch the list of all providers available for your organization, update the configuration of an already existing custom SAML 2.0 identity provider, or delete a custom SAML 2.0 identity provider registered for your organization.

You can use the custom SAML 2.0 identity providers you register with the SAML2 Adapter service, using the Authorization Code Grant and the Implicit Grant authorization flows available in YaaS.

To use your custom SAML 2.0 identity provider, pass the generated custom identity provider ID as the value of the hybris_id_provider parameter in your requests to the OAuth2 service.

Learn more:

For more information about the SAML2 Adapter service, see the SAML2 Adapter service documentation in the Dev Portal.
For technical details, see the SAML2 Adapter service API console.
For more information about the authorization flows available in YaaS, see the Grants section of the OAuth2 service documentation.

HERE Map Tile Service v1

Tue Sep 05 2017 00:00:00 GMT+0000 (UTC)

The new HERE Map Tile Service provides access to worldwide map tiles from HERE map data. You can use the map tiles in front-end applications as backgrounds for the visualization of geospatial data. This API also allows custom display options and multiple tile resources and color schemes.

Use the HERE Map Tile Service to:

Access map tiles for interactive applications
Choose from many viewing schemes and display options
Specify the location, zoom level, and resolution of map tile images

For more information, see the Mapping service documentation.

Point of Interest Service v1

Tue Sep 05 2017 00:00:00 GMT+0000 (UTC)

The new Point of Interest (POI) service offers the capability to search for nearby points of interest for any location on earth. You can use this service to quickly find cities, lakes, and public buildings by supplying longitude and latitude coordinates and a radius in meters.

For example, you can locate all the hotels within 300 meters of Madison Square Garden in New York City by sending the request /search?lat=40.75066&long=-73.99347&radius=300.

For more information, see the Point of Interest service documentation.

Transparency v1

Fri Sep 01 2017 00:00:00 GMT+0000 (UTC)

The new Transparency service allows you to fulfill requirements imposed on privacy-compliant services running on YaaS. The service provides a report that informs data subjects about the personal data that YaaS stores about them.

See the full Transparency service documentation for more information.

OAuth2 v1

Fri Sep 01 2017 00:00:00 GMT+0000 (UTC)

Proof Key for Code Exchange (PKCE) is an optional security mechanism that you can use with the Authorization Code Grant flow.

It allows you to send either a plain, non-encoded string or an encoded string along with the authorization request. The OAuth2 service verifies this string when the client attempts to exchange the authorization code for an access token.

Using this mechanism ensures that no third party intercepts any of the calls in the Authorization Code Grant, which could comprise the security of your implementation of this flow. The recommended uses for the PKCE mechanism are mobile applications, as well as scenarios where the clients can't store secrets in a secure manner

Learn more:

Read the related section of the Authorization Code Grant documentation, part of the YaaS OAuth2 service documentation.
Read the related section of the OAuth2 specification.

Service SDK 4.17.0

Mon Aug 28 2017 00:00:00 GMT+0000 (UTC)

Audit Library

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));

Support for the new `hybris-user-id` header

The 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 hybris-user header.

The Service SDK still supports the old hybris-user header.

Dependency updates

Library versions are updated, including the Spring and Spring Boot versions 4.3.10.RELEASE and 1.5.6.RELEASE, respectively. Please update the versions in your project accordingly to avoid Maven conflicts and unpredictable behavior at runtime.

Resolved issues

An issue with using the Logging Library with Scala is resolved.

HERE Map Tile Service v1

Mon Aug 21 2017 00:00:00 GMT+0000 (UTC)

The new HERE Map Tile service provides access to worldwide map tiles from HERE map data. You can use the map tiles in front-end applications as backgrounds for the visualization of geospatial data. This API also allows custom display options and multiple tile resources and color schemes.

Use the HERE Map Tile service to:

Access map tiles for interactive applications
Choose from many viewing schemes and display options
Specify the location, zoom level, and resolution of map tile images

For more information, see the HERE Map Tile service documentation.

Identity v1

Thu Aug 17 2017 00:00:00 GMT+0000 (UTC)

The newest functionality of the Identity service allows you to choose where you want to manage the scopes assigned to the users who use your solutions. The newly introduced scopesGrant parameter lets you can decide whether you want to manage user scopes directly in your custom identity provider, or to leave the scopes management to the Builder.

You can make this decision when you create a new custom identity provider. Simply include the scopesGrant parameter in the request body, along with the other data required to create a new custom identity provider.

If you already created a custom identity provider, you can start using the new functionality by updating your custom identity provider configuration. Simply include the scopesGrant parameter in the body of the PUT request you send to the /providers/{id} endpoint of the Identity service.

Learn more:

To find out more about the scopesGrant parameter and how to use it, read the related section of the Identity service documentation.
For more technical details on the Identity service, see the Identity service API console.

Earth Observation Analysis v1

Mon Aug 14 2017 00:00:00 GMT+0000 (UTC)

The Earth Observation Analysis service now provides satellite images in PNG format. Additionally, you can download specified subsets of an image using the dimensionTrim parameter in the getCoverage call. To handle the non-georeferenced PNG image format, retrieve the coverage metadata for any coverage, even subsets, using the new WCS call, describeCoverage. These enhancements are described in this release note.

Image subsets

The dimensionTrim parameter now extends the getCoverage call to trim a coverage along latitude and longitude. This way, images become smaller in size and you can request images of interesting regions without downloading more data than necessary.

Example of a subset of Key West (Florida, USA)

/wcs/getCoverage?coverageId=RGB_ESAS2_T17RMH_S2A_OPER_PRD_MSIL1C_PDMC_20161111T124314_R097_V20161110T160502_20161110T160502&dimensionTrim=long(-81.78,-81.52)&dimensionTrim=lat(24.5,24.62)

WCS function call `describeCoverage`

Use this call to describe single coverages. This call supports the same parameters that getCoverage supports. Use it to handle subsets of the non-georeferenced PNG image format.

Example describing a coverage subset

/wcs/describeCoverage?coverageId=RGB_ESAS2_T17RMH_S2A_OPER_PRD_MSIL1C_PDMC_20161111T124314_R097_V20161110T160502_20161110T160502&dimensionTrim=long(-81.78,-81.52)&dimensionTrim=lat(24.5,24.62)

New image format PNG

Request a full image or a subset in PNG image format with the parameter format=image/png. This format allows a direct depiction in a web browser. The compression of the images is lossless to reduce web traffic without loss of precision.

Please note that PNG images are no longer georeferenced. To use these images in GIS tools, request additional reference data through the describeCoverage call.

Example of a subset of Key West (Florida, USA)

/wcs/getCoverage?coverageId=RGB_ESAS2_T17RMH_S2A_OPER_PRD_MSIL1C_PDMC_20161111T124314_R097_V20161110T160502_20161110T160502&dimensionTrim=long(-81.78,-81.52)&dimensionTrim=lat(24.5,24.62)&format=image/png

For more details about any of these updates, refer to the Tutorial section in the Earth Observation Analysis API Documentation.

Builder

Fri Aug 11 2017 00:00:00 GMT+0000 (UTC)

This release includes:

The project landing page in the Builder now features the notification widget that allows you to receive information related to your project. Notification types include:

Package updates - Confirm an update to a package subscription directly from the notification.
Project member management - Accept or decline requests from users seeking to join the project.

Check back soon for the latest changes, improvements, and updates.

Dev Portal

Thu Aug 10 2017 00:00:00 GMT+0000 (UTC)

Publishing new documentation topics requires creating their registries. This can be difficult because of the number of available properties to include in a registry .json file, and you cannot forget about the required properties.

If you want to publish your content and you need to use the registry, you can find all the details in one place. Go to the JSON Schema section of the Documentation SDK, and examine the sample service .json file. Also take a look at the newly created JSON schema and its description.

Thank you for your feedback. Let us know how we can improve.

API Management v1

Fri Aug 04 2017 00:00:00 GMT+0000 (UTC)

A new security feature is introduced in the API Management service. Using the new tenants property you can specify the tenants that can access your resources. You can use this property similarly to other authorization options that are already available in the Builder.
Currently this feature is available on the API level.

The tenants property allows only the specified tenants to access your resources. You can set this property when you create a service, or at any time later.

This is a sample request to the API Management service to create a new service with an authorization rule that allows only the two user-defined tenants to access the specified resources. Line breaks are added for better readability.

curl -X POST https://api.eu.yaas.io/hybris/api-management/projects/myProject/services \
-H "Content-type: application/json" \
-H "Authorization: Bearer 0918th3-t0k3nz18eU-u09810n33d-1337eet" \
-d '{
  "name": "myservice",
  "version": "v1",
  "state": "DRAFT",
  "sourceUrl": "https://my.service.com/",
  "authorizationRules": [
        {
          "path": "/myservice/pathiwannasecure",
          "methods": ["POST", "DELETE"],
          "tenants": ["mytrustedtenant1", "mytrustedtenant2"]
        }
    ]
}'

As result, the newly created service allows only the mytrustedtenant1 and mytrustedtenant2 tenants to access the resources located under the /myservice/pathiwannasecure path.

If you want to use the tenants property and create a new authorization rule for a service that already exists, send a PUT request to the projects/{projectID}/services/{serviceID} endpoint of the API Management service.

Learn more:

Read about the authorization rules in the related section of the YaaS Security documentation in the Dev Portal.
For more information about the API Management service, see the related documentation and API console.

RAML Patterns 2.0.3

Thu Jul 27 2017 00:00:00 GMT+0000 (UTC)

The yaasAware trait now reflects the new hybris-user-id Hybris-specific header. Additionally, the hybris-user header is now deprecated.

Refer to the Hybris-specific headers documentation for more information about these headers.

Dev Portal

Fri Jul 21 2017 00:00:00 GMT+0000 (UTC)

Due to feedback from the community, the filtering functionality in the API Docs and Release notes sections of the Dev Portal is extended. Before now, you could not share a link to filtered API Docs or Release notes pages. For example, if you tried link to a filtered API Docs page showing only services with "cart" in the name, the link would show the full, unfiltered page. Now the URL in the address bar adjusts to contain the information you enter in the Filter by keyword field, so it is really easy to share specific content.

This is an example of a URL with filters specified:

This is an example of a filtered API Docs page:

Your comments are very valuable. Use the feedback icon to submit feedback.

Builder

Fri Jul 21 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements

New widgets for the organization dashboard

New widgets have been added to the Builder. You can add them to the organization dashboard.

My account - Easily access your account information with this widget.
Last available bill - View your most recent invoice.
Accumulated cost for current month - See how much your organization has accumulated in YaaS costs for the current month.
Whole organization cost per month - A historical chart displays monthly costs.

Check back soon for the latest changes, improvements, and updates.

PubSub Builder module v1

Fri Jul 14 2017 00:00:00 GMT+0000 (UTC)

Manage PubSub topics and subscriptions more easily

You can now manage your PubSub topics and push subscriptions directly in the Builder without making direct REST API calls.

The PubSub Builder module is available through a subscription to the Events package in the YaaS Market. After you subscribe to the Events package, you can manage PubSub topics and push subscriptions.

To manage topics In the Builder, select your project and click PubSub. On the Topics tab you can:

Click + TOPIC to create a new topic.
Click DELETE to delete an existing topic.

To manage subscriptions In the Builder, select your project and click PubSub. On the Subscriptions tab you can:

Click + SUBSCRIPTION to create a new PubSub push subscription.
Click DELETE to delete an existing subscription.
Click PING to verify whether a subscription endpoint is accessible.
Click EDIT to modify a subscription.

The new Builder module makes PubSub much easier to use.
If you have any questions or feedback, please use one of the Feedback icons or links in the Dev Portal or the Builder.

Deletion v1

Tue Jul 11 2017 00:00:00 GMT+0000 (UTC)

The new Deletion service allows you to delete all personal data for a specified subject throughout all data privacy-compliant services with just one request.

To comply with data privacy regulations, the Deletion service stores information about the location of personal data throughout the YaaS services and propagates deletion requests to each service. In response, the services send their deletion statuses directly to the Deletion service, which allows you to see the statuses from all services in a single place.

To request the deletion of personal data, supply the subject's ID and type. Use the deletion ID and link provided in the response to perform a GET request to check the status of the deletion process from all services.

See the full Deletion service documentation for more information.

Keep in mind that a deletion request does not delete data immediately. If the specified data is subject to a transaction then data deletion is not possible. If the specific data is subject to a retention policy, the system deletes it only after retention period ends.

You can check all of the details for any request in the services array of the response, which can contain the following statuses:

no-data
can-delete
transaction-in-progress
blocked
deleted

See the Considerations section of the documentation to learn more about the Deletion service events and the possible responses.

Account v2

Wed Jul 05 2017 00:00:00 GMT+0000 (UTC)

The Account v2 service is released

YaaS is all about simplicity and productivity, and the Account service is one of the building blocks of the YaaS ecosystem. When you create an SCI account and sign in to YaaS for the first time, you find a user-friendly experience. The platform gives different options that allow you to be productive right away.

The new version of the Account service provides an API so you can quickly locate and work in the appropriate organizations or projects.
YaaS users can request to join an organization after the owner uses the service's new functionality and marks the project or organization as public. This allows people to quickly find their place in YaaS, join their groups right away, and not lose any time.

The owner of a project or organization can invite users to YaaS. The invitation email gives new YaaS users the opportunity to create a secure and convenient SAP Cloud Identity account, ensuring that they sign in to YaaS using the most secure way. Since collaboration is one of the keys to success, invite your colleagues!

The Account v2 doesn't leave anyone behind

If you still use your legacy YaaS account, you have the option to grant your roles to a new SCI account. To initiate the process, click Grant Roles to Alternate Account in your Builder account settings. This quick, simple, and secure process allows you to get the most out of YaaS and SAP Cloud Identity. Single sign-on allows you to use one account across SAP applications, and two-factor authentication provides increased security.
Read more about granting roles to alternate accounts in the related section of the Account v2 service documentation.

What about the previous version of the Account service?

Don't worry, Account v1 is not going away.
The Account v1 service still handles basic tasks such as creating projects and organizations, and managing roles within projects and organizations. Account v2 allows you to send join requests to projects and organizations, create SCI-enabled invitations to projects and organizations, and grant roles from legacy YaaS accounts to new SCI accounts.
The features of Account v2 are currently available only on the API level, and will be implemented in the Builder in the near future. Keep an eye out for more news and updates.

For more technical details, see the Account v2 service's API console.

Builder

Tue Jul 04 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

A dashboard on the organization level
A view to manage all of your bookmarks across organizations
Simplified project selection for new users

A dashboard on the organization level

The new dashboard for organizations provides a central location to view primary bits of data pertaining to your organization. The dashboard features widgets that each display different data. View information such as active projects, project costs, and organization members.

A view to manage all of your bookmarks across organizations

Bookmark management is now easier thanks to a new management page. Manage your bookmarks across organizations. Edit or delete individual bookmarks. Drag and drop bookmarks between categories that you create. Delete entire groups of bookmarks.

Simplified project selection for new users

In previous versions of the Builder, new users had to manually search for available projects to join. Enhanced organization visibility settings now make it easier for new users to locate and join projects after their initial login.

The organization owner sets up the organization to be visible to new users.

When the user logs in, the system recognizes the domain name of the user's email address and suggests organizations based on that domain name. Then, the user can select an organization and request to join a specific project belonging one of the suggested organizations.

Check back soon for the latest changes, improvements, and updates.

Service SDK 4.16.0

Tue Jul 04 2017 00:00:00 GMT+0000 (UTC)

To save processing time, you can now enable caching of rewritten RAML. To do so, add an expiry interval, in seconds, to your RamlRewriterFilter configuration in the web.xml file. For example:

    <filter>
        <filter-name>ramlRewriterFilter</filter-name>
        <filter-class>com.sap.cloud.yaas.servicesdk.ramlrewriter.filter.RamlRewriterFilter</filter-class>
        <init-param>
            <param-name>expireAfterSeconds</param-name>
            <param-value>1800</param-value>
        </init-param>
    </filter>

For details, see The RamlRewriterFilter.

Support for unencoded slash in URI parameter in Rammler

To use unencoded slashes in URI parameters, call a different constructor of the generated Rammler client, providing true as the value for the parameter encodeSlashInPath.

PubSub v1

Fri Jun 30 2017 00:00:00 GMT+0000 (UTC)

Allow the hyphen character (`-`) in the username of the Basic Authentication for Push Subscriptions

The username for Basic Authentication in the Push Subscriptions now allows the - character.

For more details, see the PubSub RAML contract, specifically the JSON schema for the /topics/{topicOwnerClient}/{eventType}/subscriptions and /topics/{topicOwnerClient}/{eventType}/subscriptions/{name} resource in the PubSub API console.

This change in the PubSub contract is backward-compatible, so existing clients are not affected by this new functionality.

Identity v1

Thu Jun 29 2017 00:00:00 GMT+0000 (UTC)

The Identity service is a new addition to YaaS that allows you to create and register custom identity providers for your projects and organizations.

By creating and registering custom identity providers, you can enable your customers to access your organization's resources in YaaS without the need to create new accounts.

The Identity service allows you to:

Get the technical information required to establish a successful connection between your custom identity provider and the YaaS OAuth2 service.
Register your custom identity provider and obtain its identifier.
Manage the custom identity providers registered for your organization. You can fetch the list of all providers available for your organization, update the configuration of an already existing custom identity provider or delete a custom identity provider registered for your organization.

You can use the custom identity providers you create and register with the Identity service, using the Authorization Code Grant and the Implicit Grant authorization flows available in YaaS.
To use your custom identity provider, pass the generated custom identity provider ID as the value of the hybris_id_provider parameter in your requests to the OAuth2 service.

The described functionality of the Identity service is currently available only on the API level, and will be implemented in the Builder in the near future. Keep an eye out for more news and updates.

Learn more:

For more information about the Identity service, see the Identity service documentation in the Dev Portal.
For technical details, see the Identity service API console.
For more information about the authorization flows available in YaaS, see the Grants section of the OAuth2 service documentation.

OAuth2 v1

Fri Jun 23 2017 00:00:00 GMT+0000 (UTC)

Single sign on allows you to use multiple applications and access different resources by signing in just once and gives the users the most seamless, easiest, and modern way to use your solutions. This functionality is now available in the Authorization Code Grant flow.

To use the single sign on, you need an id_token, which provides the identity of the user and/or resource owner. To get it in the Authorization Code Grant flow, you need to include the openid scope in the list of scopes included in your request to the OAuth2 service. After the client successfully exchanges the authorization code for an access token, you get the id_token value in the response body.

Pass the id_token in subsequent requests to the OAuth2 service to get access tokens for different tenants without interrupting the user experience with additional authentication screens.

To find out more about the single sign on:

Read the related section of the OAuth2 service documentation.
See the OAuth2 service's API console, paying special attention to the /authorizeendpoint.

Service SDK 4.15.0

Thu Jun 22 2017 00:00:00 GMT+0000 (UTC)

Multiple values and new fields available for the metric logging pattern

The metric part of the logging schema is adjusted according to updated YaaS requirements. It is recommended that you now log multiple values for a metric log entry with the support of the utility methods. There are also several new fields in the metric log schema, automatically filled in when available and when you use the Service SDK's Logging filters. Check out the logging schema for all the changes and the logging documentation for more information on how to log metrics using the Service SDK.

Error Message Servlet

Have you ever thought of securing your Web Service against information leakage on uncaught exceptions? If you have not secured your service yet, you might find the new Servlet Support utility useful: Error Message Servlet. Simply add it to your web.xml and enjoy nicely formatted, unified error responses on unexpected errors, always following the YaaS Error Message Schema. This utility is Jackson- and Jersey-independent. Refer to the documentation for more instructions.

If you are using the Service SDK Spring Boot starter library, you are already using the feature!

Resolved issue

An issue in the Jersey archetype caused failures when accessing the injected Jersey Context.

Customer v1

Thu Jun 22 2017 00:00:00 GMT+0000 (UTC)

New optimistic locking feature and personalized customer emails

The features available with this update of the Customer service include optimistic locking in support of updates, as well as the ability to add customer information variables to email templates.

Optimistic locking for customer updates

All new customers automatically receive a version ID for use in further updates. During customer updates, the version ID supports optimistic locking. This way, changes of the update have no effect on the latest version of the Customer service.

Customer information in the email templates

You can use customer data, such as sign-in email, firstName, lastName, or contactEmail to send personal emails to your customers. For example, you can add the customer’s first and last names to the address line of the email by inserting the following code:

${tools.esc.html(${d.customer.firstName})} ${tools.esc.html(${d.customer.lastName})}

For a detailed list of available attributes, see the Customer service documentation.

Velocity Template v1

Wed Jun 21 2017 00:00:00 GMT+0000 (UTC)

Validation of uploaded template variants

The service now automatically validates the content of the variants you upload. This ensures that all stored template variants are valid and that Velocity language syntax errors are detected as early as possible. You do not need to take any action to begin benefiting from this improvement.

Media v2

Tue Jun 13 2017 00:00:00 GMT+0000 (UTC)

The Media service allows you to upload a file with its original file name. The system returns the file name and the file together, therefore the browser can save your file with the original file name.

To store the name of your media file, provide the file name in the Content-Disposition header when uploading a file content.

Example:

Method: PUT
Request URL: https://s3.amazonaws.com/sap.yaas.us.stage.media.temp/507f191e810c19729de860ea?x-amz-security-token=AQoDYXdz...
Headers:
- Content-Disposition: attachment; filename="filename.jpeg"

When you retrieve your media file, the system returns the Content-Disposition header along with the response from the Media service.

To learn more, see the Manage media tutorial of the Media service documentation.

Builder

Tue Jun 13 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

The project dashboard is available by default

The project dashboard, previously hidden behind a feature toggle, is now openly available for easy access and oversight of project-related information. Widgets display the information. Examples of the data displayed include the number of project members, project user roles, and subscriptions used in the project.

There are more changes and improvements on the way. Check back soon for the latest updates.

Document v1

Thu Jun 08 2017 00:00:00 GMT+0000 (UTC)

Now, the GET requests on the /{tenant}/{client}/indexes/{type}/{name} and /{tenant}/{client}/indexes/{type} endpoints return new response bodies.

This change was announced in this release note and provides the response format that meets the highest standards of consistency between different types of requests.

Responses for GET requests, such as requests to the /{tenant}/{client}/indexes/{type} endpoint, look similar to the example shown:


  {
    "keys" : {
      "$text" : true,
      "name" : 1,
      "code" : -1
    },
    "options" : {
      "name" : "indexName",
      "unique" : true,
      "sparse" : true,
      "weights" : {
        "$all" : 1,
        "title" : 5,
        "description" : 3
      },
      "default_language" : "english"
    }
  },
    ...
]

To learn more, refer to the latest API console API console.

Knowledge Hub

Wed Jun 07 2017 00:00:00 GMT+0000 (UTC)

Headings in the Knowledge Hub panel notes have a new, adjusted font size. Thanks to the bigger font size, the headings stand out from the panel note content.

This is how headings in panel notes look now:

Your feedback is appreciated. Keep sharing your suggestions for improvement.

Document v1

Tue Jun 06 2017 00:00:00 GMT+0000 (UTC)

The Document service now supports a new location for JSON schemas and RAML patterns, pattern.yaas.io, which is a region-independent URL. For now, backward compatibility ensures that you can still reach the pattern at the old URL, api.yaas.io/patterns, as long as that domain remains supported. However, use the new domain whenever possible to ensure that you are using the latest version of the RAML patterns. Refer to https://pattern.yaas.io/ to see the latest pattern versions, or check within the documentation of your pattern to verify that it is not marked as deprecated.

To learn more, see the New domain for RAML Patterns at pattern.yaas.io blog post.

Document Backup v1

Fri Jun 02 2017 00:00:00 GMT+0000 (UTC)

New features

Going forward, you do not have to provide storage space for all your backups. The Document Backup service provides cloud-based storage for all your backups. The service conveniently allows you to list all your client's backups, and to check the details of the backups.

Backup to the cloud

To back up your Document service data to the cloud, perform a POST request on the /backup-jobs endpoint.

Request with a body

You can set:

include - specifies all of the tenants you want to back up. The default value for this field is *.
exclude - specifies the tenants which you do not want to back up. The default value for this field is "", an empty string.
skipIndexes - omits indexes from the backup. The default value of this field is false.

Example:

{
    "tenants" :            
        {
            "include" : "marketplace, toad",
            "exclude" : "marketdemo"
        },
    "skipIndexes": true
}

Request without a body

If you submit a backup request without a body, the system backs up the data and indexes for all the client's tenants.

Restore from the cloud

To restore your data from a backup stored in the cloud, perform a POST request on the /restore-jobs endpoint.

Request with a body

You can set:

backupId - restores the data from a particular backup. When the backupId is not specified, the restore operation is performed from the last available backup.
include - specifies all of the tenants to restore the data for. The default value for this field is *.
exclude - specifies all tenants you do not want to restore. The default value for this field is "", an empty string.
skipIndexes - omits indexes from the restore. The default value of this field is false.

Example:

{
    "backupId" : "591e953004e824001629cf26",
    "tenants" :            
        {
            "include" : "marketplace, toad",
            "exclude" : "marketdemo"
        },
    "skipIndexes" : true
}

Request without a body

If you submit a restore request without a body, the system restores the data and indexes from the latest backup, for all the client's tenants.

List your backups

To list all backups stored for your client, perform a GET request on the /backups/ endpoint.

Check the details of a backup

To view the details, such as the completion date or a list of backed up tenants, of a backup, perform a GET request on the /backups/{id}.

For all the technical details, see the Back up to the cloud and Restore from the cloud sections of the Document Backup service documentation.

New scopes

To ensure the highest standards of security and data protection, the Document Backup service requires new scopes when you call its endpoints.

The /data/{tenant}/{type} endpoint is not affected by the introduction of new scopes and does not require any scope.

From now on use the:

hybris.document-backup_view scope for all GET requests
hybris.document-backup_manage scope for DELETE operations on the /backups/{id} endpoint
hybris.document-backup_backup scope for POST requests on the /backup-jobs endpoint
hybris.document-backup_restore scope for POST requests on the /restore-jobs endpoint

Media v2

Fri Jun 02 2017 00:00:00 GMT+0000 (UTC)

Sorting your media results now possible

From now on, when you list multiple media files from the Media service, you can sort your results by Content-Type and/or metadata attributes.

Meet the sort query parameter

To sort your results, set the sort query parameter to:

Content-Type to sort by the type of media files you list
{key_name} to sort by the metadata attribute

Specify the sort order by providing the asc or desc value after the colon. The default sort order is ascending. See the examples that follow.

To combine multiple sort parameters, separate them with a comma.

Examples

Sort by Content-Type in descending order

?sort=Content-Type:desc

Sort by metadata attribute in ascending order

?sort={key_name}

Sort by multiple metadata attributes

?sort={key_name_1}:desc,{key_name_2}:asc,Content-Type:desc

Sort by both Content-Type and metadata attributes

?sort={key_name_1},{key_name_2}:desc,Content-Type:desc

Service SDK 4.14.0

Thu Jun 01 2017 00:00:00 GMT+0000 (UTC)

New domain for RAML Patterns

The RAML Patterns are now available on pattern.yaas.io, a new region-independent URL. Established customers can continue to use api.yaas.io/patterns for the foreseeable future. Always use the latest version of the RAML patterns. Refer to https://pattern.yaas.io/ to see the latest pattern versions.

Client Generation on demand

As there was demand for more Client Generation flexibility we have added examples and explanations on how to build clients on demand.

Knowledge Hub

Wed May 31 2017 00:00:00 GMT+0000 (UTC)

You can now open images in Knowledge Hub articles in a modal window. All pictures with img-click-modal class are clickable and, after clicking, display in the same way as images in the Dev Portal. Click an image to instantly open it in a modal dialog.

See the following example:

Your feedback is appreciated. Keep sharing your suggestions for improvement.

Dev Portal

Tue May 30 2017 00:00:00 GMT+0000 (UTC)

Content displayed in the Dev Portal and the Knowledge Hub now appears in frames. By default, a narrow frame appears around each image and graph. See the following examples.

This is how a frame around an image in the Knowledge Hub looks:

This is how a frame around a graph in the Dev Portal looks:

Your feedback is very important and valuable, so thank you and keep it up.

Dev Portal

Mon May 29 2017 00:00:00 GMT+0000 (UTC)

Due to feedback from the community, we extended the API filtering search engine. Before now, you could only filter services by keywords, markets, or packages. Now you can also search services, using a Service Url.

This is an example of a Service Url:

This is an example of a Service URL search:

Your comments are very valuable. Use the feedback icon to submit feedback.

Velocity Template v1

Fri May 26 2017 00:00:00 GMT+0000 (UTC)

Render templates using a locale

You can now specify a locale in the request to render a template. The locale is used to initialize the Velocity Tools, which support internationalization. For example, you can use the NumberTool to format a price as a currency, taking the passed-in locale into account, or you can use the DateTool to display a date in a locale-specific format.

You can read more about how to use the Velocity Tools in the Velocity Template service documentation.

OAuth2 v1

Fri May 26 2017 00:00:00 GMT+0000 (UTC)

From now on, the /end_session endpoint of the OAuth2 service verifies the post-logout redirect URIs. URIs have to be pre-registered for the client which you use to call the endpoint.

When you call the /end_session endpoint, the OAuth2 service expects to receive a post-logout redirect URI in the query string.
If you register only one redirect URI for the client, the OAuth2 service, by default, uses it as the post-logout redirect URI.
However, if you register multiple redirect URIs for your client, you must include the post_logout_redirect_uri parameter in the query string to avoid a 400 error response.
Additionally, you must pass the query parameter if the client has no registered redirect URIs. If you do not, the OAuth2 service stops the flow and returns a 400 error.
Furthermore, if you pass an unregistered URI in the query string, the OAuth2 stops the flow and returns a 400 error.

It is recommended that you pass the post_logout_redirect_uri parameter in all of your requests. This helps to prevent any situation where your code stops functioning because you registered an additional redirect URI for your client.

Find out more:

For more information about the /end_session endpoint, see the OAuth2 service's API reference
For more information about the post-logout redirect URIs, see the related release notes.

API Management v1

Fri May 26 2017 00:00:00 GMT+0000 (UTC)

Now you can define trusted post-logout URIs that the client can use when calling the /end_session endpoint of the OAuth2 service. To use the OAuth2 /end_session endpoint, define at least one post-logout redirect URI for the client that calls it.

For existing clients, define the postLogoutRedirectUris parameter by sending a PUT request to the /projects/{projectID}/clients/{identifier}.
You can also define the postLogoutRedirectUris parameter when when you create new clients using the /projects/{projectID}/clients endpoint.

This feature is not available in the Builder, which means that you can only set the post-logout redirect URIs directly in the API.

Find out more:

For more information about the post-logout redirect URIs, see the API-Management service's api reference.
For more information about the /end_session endpoint and how it verifies the post-logout URIs you set for your clients, see the related these release notes.

Email v2

Fri May 26 2017 00:00:00 GMT+0000 (UTC)

Send emails with templates using a locale

You can now specify a locale when sending an email that uses a template. The locale transmits to the Velocity Template service, which uses it for rendering. The locale is used mainly to initialize the Velocity Tools, which support internationalization. You can read more about how to use the Velocity Tools in the Velocity Template service documentation.

Events v1

Thu May 18 2017 00:00:00 GMT+0000 (UTC)

The Events service is scheduled for shut down on May 17th, 2018

Currently, YaaS offers two services with similar functionality:

The PubSub service is part of the the Events package. It offers the complete set of PubSub APIs to publish and consume events.
The Events service does not require a package subscription and offers a subset of the PubSub APIs to consume events, through both pull and push operations.

Over time, it became apparent that the naming similarity between the Events package and the Events service is confusing. To avoid this confusion, the Events service is scheduled for deprecation.

Migrate to the PubSub service

To use the PubSub service instead of the Events service, replace /events with /pubsub in all API calls. All topics and Push subscriptions are still available. Everything will continue to work as expected.
A subscription to the Events package is not required. All APIs available in the Events service are also available in the PubSub service without a subscription.
If you use the YaaS Service SDK client generator, update it to to use the PubSub RAML.

The Events service will not be available after May 17th, 2018.

Builder

Thu May 18 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Cross-organizational bookmarks
Default project avatars

Cross-organizational bookmarks

The initial implementation of organzational bookmarks required the user to be within an organization in order to see bookmarks pointing to pages belonging to that organization. With this update, this functionality is enhanced to allow you to access bookmarks of organizations outside of the one you are currently viewing.

Default project avatars

If you have not assigned an avatar to your project, the system will automatically assign one to it. This assignment lends a more complete aesthetic to the page.

There are more changes and improvements on the way. Check back soon for the latest updates.

OAuth2 v1

Mon May 15 2017 00:00:00 GMT+0000 (UTC)

The functionality of the Authorization Code Grant authorization flow is now improved with support for refresh tokens.

Refresh tokens are long-lasting credentials which you can use to fetch additional access tokens. Unlike access tokens, refresh tokens do not expire until you revoke them.

To allow the management of tokens, the /revoke endpoint now enables you to revoke multiple tokens in a single request. Using this endpoint enables you to revoke refresh tokens and access tokens.

Additionally, the /refreshtokens endpoint now enables you to delete numerous refresh tokens by posting a single request. Additionally, you can filter the refresh tokens by the client for which they are issued.

Learn more about the refresh tokens:

Read the OAuth2 specification.
See the Tokens section of OAuth2 service documentation.
Read the OAuth2 service API console for more detailed information on how to use the /refreshtokens and /revoke endpoints.

Hybris Marketing Consolidation Enricher v2

Fri May 12 2017 00:00:00 GMT+0000 (UTC)

Features

The Web Interaction Consolidation Enricher is now called the Hybris Marketing Consolidation Enricher. The Hybris Marketing Consolidation Enricher consolidates all of a user's non-e-commerce and e-commerce interactions per session. The Consolidation Enricher reads the configurations defined in the Profile Services for Marketing Configuration service to: * update default values for fields such as **digitalAssetSystem** and **sourceSystemType**. * filter contacts based on the interest affinity.

The Hybris Marketing Consolidation Enricher only consolidates data from the SAP Hybris Profile when the website is configured with **Profile Tag**. Update to the latest version of the Profile Core Services package to make use of **Profile Tag**.

Profile Services for Marketing Configuration v1

Fri May 12 2017 00:00:00 GMT+0000 (UTC)

You can now configure the data sent to the SAP Hybris Marketing system from SAP Hybris Profile. A marketer can configure the fields in the payload and also filter contacts based on the interest affinity.

See the Profile Services for Marketing Configuration documentation for more information.

Service SDK 4.14.0

Thu May 11 2017 00:00:00 GMT+0000 (UTC)

The RAML Patterns have moved from api.yaas.io/patterns to pattern.yaas.io. Please update your RAML files accordingly within 3 months from the date of this release note.

Client Generation on demand

In response to the demand for more Client Generation flexibility, new examples and explanations about how to build clients on demand are now available in the Service SDK documentation.

Coupon v1

Wed May 10 2017 00:00:00 GMT+0000 (UTC)

Features

Partial updates through PUT /{tenant}/coupons/{code}?partial=true have been deprecated in favor of using PATCH method. Full object replacement is not affected by this change.   KIWIS-3240 - Introduce PATCH for partial update and deprecate PUT

A version id is automatically added to all new coupons which can be used for further updates. If present, the version id is used during coupon updates to support optimistic locking. Otherwise, changes will affect the latest version of the coupon.   KIWIS-3258 - Implement optimistic locking the correct way

Loyalty Member v1

Tue May 09 2017 00:00:00 GMT+0000 (UTC)

###Loyalty member features

There are two ways to delete loyalty member accounts:

Soft Delete: Soft delete is performed by default. Soft delete updates the status of a loyalty member to CANCELLED. This feature is scheduled for deprecation.
Permanent Delete: Permanently delete loyalty member accounts by passing a header with the name hard-delete and the value true.

###Cancel points

Cancel points accrued in any previous activity by creating a new CANCELLATION activity. The system cancels points according to the cancellation rules configured in the Builder.

Loyalty Builder Module

Tue May 09 2017 00:00:00 GMT+0000 (UTC)

###Delete loyalty member profiles

You can delete a loyalty member profile from the loyalty program. Use the Delete feature on the Member screen to delete a loyalty member profile. You can also delete a loyalty member profile from the Member Details screen.

###New Rule Type - Cancellation introduced

The Loyalty Rule service now supports cancellations, using the Rule Type - Cancellation. This rule type supports the Member Activity Type - Cancellation. Use Cancellation to cancel points awarded for member activities. For example, a loyalty member earns points for an order activity, and later returns or cancels the order. The points awarded can be partially or fully cancelled through the Rule Type - Cancellation.

###Manual Deduct is now Cancel

The Assign Points button on the Member Details screen is now the Update Points button. The Assign Points dialog box is now the Update Points dialog box. In the Update Points dialog box, Deduct Points is now Cancel Points, the Deduct button is now the Cancel button, and the Deduct field is now the Cancel field.

The ability to view the Member Details user interface (UI) and the Analytics UI is not available in the Loyalty Core Services package any longer. See. for more details.

Community

Mon May 08 2017 00:00:00 GMT+0000 (UTC)

Showcases allow you to share your projects and business applications, built on YaaS, with the community.

When creating a showcase, you can specify whether to share it externally, by choosing the visibility level Public. You also have the option to choose the visibility level Private. Until now, selecting Private meant that the showcase would be visible within your development organization.

Based on your feedback, the functionality of private showcases changed. While these showcases no longer display in the Community, even within your organization, you can still create private showcases and edit them in the Builder for your personal use. Public showcases are not affected by this change.

Commerce Insights SSO API v2

Fri May 05 2017 00:00:00 GMT+0000 (UTC)

View Commerce Insights reports with the new Commerce Insights SSO service

/dashboard
/realtime
/insights
/merchandising
/marketing
/customer_summary_report
/orders

Checkout v1

Fri Apr 28 2017 00:00:00 GMT+0000 (UTC)

Due to a Document service change when handling long queries, preventative measures were made to the Checkout service. For more details about the change, see the Document service release notes.

The Document service returned an error when handling long queries because the HATEOAS header has a 8 KB limit. To ensure the Checkout service does not encounter this error, the service only retrieves 40 prices at a time where previously it retrieved 80. The Checkout service still retrieves 80 products from the Product service.

Document v1

Thu Apr 27 2017 00:00:00 GMT+0000 (UTC)

Improved error handling for too-long queries

The error handling is improved for queries sent to the Document service that are too long.

Background

When you send a query to the Document service it is sent in the HATEOAS header. The request fails if the total size of all headers exceed 8 KB. Formerly, the 400 Bad request response for too-long requests did not specify the issue, so a solution was not clear.

Solution

Now, when a query is too long and all of the parameters in the request are correct and valid, the 400 Bad request response includes the reason in the message body:

{
  "status": 400,
  "message": "Request URI too long. Please minimize your query.",
  "details": []
}

If you receive that error message, reduce the length of your query string and resend the request.

For more details, see the Considerations section of the Document service documentation.

Checkout v1

Thu Apr 27 2017 00:00:00 GMT+0000 (UTC)

Order service now supports product variants

The Order service now supports product variants. Corresponding updates to the Checkout service support the changes in the Order service.

During the checkout process, the Checkout service uses the Product service's search endpoint to validate that a given product variant is in stock. If this validation fails, the Checkout service returns an error. If this validation and the checkout process are successful, the Checkout service sends the product variant details to the Order service when the order is created.

Builder

Thu Apr 27 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features:

An improved login page
Bookmarks for the organization home page

The updated login page lets SAP Account holders as well as users with invitations log in to YaaS. New users can only sign in using the yellow sign-in button. Users that have not yet migrated to an SAP Cloud Identity should use the blue button.

Bookmarks for the organization home page

The top navigation in Builder now features and icon to bookmark pages of a project. After you bookmark a page, it appears in the drop-down menu of bookmarks, sorted by the project that it belongs to. To modify your bookmarks, click the link Manage Bookmarks in the dropdown. The user is then directed to the organization home to delete or edit bookmarks. You can customize bookmark settings with individual names and assigned, colored tabs that appear alongside the bookmark on the organization homepage.

There are more changes and improvements on the way. Check back soon for the latest updates.

Dev Portal

Wed Apr 26 2017 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, an issue with the display of headings is resolved. Unlike other heading styles, h5 headings displayed in capital letters. All headings now display in a consistent manner.

Your feedback is very important and valuable, so thank you and keep it up.

Service SDK 4.13.7

Wed Apr 26 2017 00:00:00 GMT+0000 (UTC)

Resolved issue

An issue in the Service Generator caused failures when attribute names started with an underscore. This issue is now resolved and you can begin attribute names with an underscore.

Community

Mon Apr 24 2017 00:00:00 GMT+0000 (UTC)

Thanks to your valuable feedback, the Community Showcases now includes these enhancements:

• The entry point for showcase documentation, the Create your own Showcase! card, now appears at the beginning of the showcase list, for easier access.
• The YaaS showcase documentation on Knowledge Hub now provides some suggestions about how you can enrich your showcase with detailed information to present it in the best possible light. Learn how to build a better showcase description and how to tell your story with images and media.
• The Contact Developer button is now named Contact Showcase Owner. The contact functionality allows you to communicate with the creators of showcases so you can better understand the technology or learn their best practices.

Media v2

Wed Apr 19 2017 00:00:00 GMT+0000 (UTC)

There is a change in the Media pricing model.

The beta and commercial packages have a new pricing model. For more information see the package descriptions in the YaaS Market.

If you have any questions about this announcement, click the Feedback button. In the meantime, stay tuned for more YaaS news!

Knowledge Hub

Fri Apr 14 2017 00:00:00 GMT+0000 (UTC)

The Knowledge Hub is now integrated with Facebook and Twitter. The new social media buttons display at the bottom of each article page. Use the buttons to share links to the Knowledge Hub articles on Facebook and Twitter. Click the relevant button to instantly publish new information on social media. See the following example of posting a tweet:

Your feedback is appreciated. Keep sharing your suggestions for improvement.

OAuth2 v1

Wed Apr 12 2017 00:00:00 GMT+0000 (UTC)

To further enhance the security of the YaaS ecosystem, the Authorization Code Grant flow is implemented. Use the Authorization Code Grant flow in scenarios where you cannot trust the client application, and you cannot allow the client application to store the client ID and client secret.

Learn more about the Authorization Code Grant flow:

Read the OAuth2 specification.
See the Authorization Code Grant flow diagram in the Overview of the OAuth2 service documentation.
Learn how to request an authorization code and exchange it for an access token in the Grants section of the OAuth2 service documentation.

Dev Portal

Wed Apr 12 2017 00:00:00 GMT+0000 (UTC)

The view of the yFactors DNA page in the Overview section in the Dev Portal is improved. The page has a simple, single-screen design now, without any hide and show functionality. Along with the new, simplified layout, the page content is also enhanced.

This is how the yFactors DNA page displayed before:

This is how the yFactors DNA page appears now:

OAuth2 v1

Tue Apr 11 2017 00:00:00 GMT+0000 (UTC)

New options are now available to fine-tune the authorization rules that secure the deployed services.

Optional authorization

The optional authorization option is suitable for securing mixed resources. It allows everyone to access the public set of resources, even without a token. If the user calls the service with a valid token, the service returns a different set of resources.

A good use case for this feature is a service that manages blog posts. When you enable the Optional Authorization checkbox in the Builder, the service displays published blog posts to everyone who calls it. Registered users that call the service with a valid token can see the published posts, as well as the unpublished posts that they created. The unpublished posts are the restricted resource in this scenario.

To achieve this behavior, create the following authorization rule:

Path: /myservice/v1/blogposts/

Methods: GET

Skip Authorization: not checked

Scopes: myservice.post_manage, myservice.post_create

Require all scopes for authorization: checked

Optional Authorization: checked

Skip Subscription Check: not checked

When the caller uses the GET method on the secured path, the API proxy verifies the caller's token for both of the defined scopes, and checks for an active subscription to the service. If the call meets the requirements set in the authorization rule, the service allows the user to access the restricted resources. If the call does not include a token, the service returns public resources to the caller.

For more information about the Optional Authorization option, see the Secure a Service section of the Security documentation, as well as the Anonymous Login deprecation blog post.

Skip subscription check

The skip subscription check option is suitable for essential services, but use it on any service you see fit. When you enable the Skip Subscription Check checkbox in the Builder, the API proxy checks the caller's token against any authorization rules that you set, but does not check for an active subscription to the given service. This means that you can require the caller to have an access token with specific scopes in order to access your service, but ignore the caller's subscription status altogether.

To achieve this behavior, create the following authorization rule:

Path: /hybrisservice/v1/resource/

Methods: GET, POST, PUT

Skip Authorization: not checked

Scopes: hybris.account_view, hybris.org_view

Require all scopes for authorization: not checked

Optional Authorization: not checked

Skip Subscription Check: checked

When the caller uses the GET, POST, or PUT methods on the secured path, the API proxy checks the caller's token for either of the two specified scopes, but ignores the user's subscription status. This means that the call succeeds as long as the user calls the service with a valid access token that includes at least one of the hybris.account_view and hybris.org_view scopes. The user does not have to subscribe to the service to access the secured path

For more information about the Skip Subscription Check option, see the Secure a Service section of the Security documentation.

Find these options and more in the Authorization Rules section of your service's settings. Go to Projects > {My Project} > Services > {My service} > Authorization Rules.

Customer v1

Wed Apr 05 2017 00:00:00 GMT+0000 (UTC)

New scopes make customer updates more secure

The new scopes further expand the currently available hybris.customer_update scope. Now you can update or delete a customer using two separate scopes. This makes customer updates more secure.

hybris.customer_manage to update a customer
hybris.customer_delete to delete a customer

Also, you can continue using the hybris.customer_update scope both to update and delete a customer.

Builder

Tue Apr 04 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Redesigned navigation
The feedback icon offers multiple options in a dropdown menu

The redesigned navigation spanning the YaaS website changes the way you navigate to the Builder. The top navigation in YaaS was previously dark blue and featured a light blue submenu. The top navigation is now a single bar. All of the navigation items from the former dark blue top navigation live in a new square pull-down menu accessible from the left of the new navigation bar. You can choose the Builder from the square pull-down menu.

The location of the feedback icon is now more visible and provides access to a number of options. Previously, the icon was on the bottom right of the page and only opened a feedback form when clicked. Now it appears in the top navigation. When you click it, you can choose to get help, give feedback, find out the status of YaaS or turn on page help.

There are more changes and improvements on the way. Check back soon for the latest updates.

Dev Portal

Fri Mar 31 2017 00:00:00 GMT+0000 (UTC)

Thanks to the community feedback, an issue was identified with interactive tutorials. Previously, an error occurred when you selected an existing project in an interactive tutorial. The issue is now resolved and you can select an existing project without an error.

Your feedback is very important and valuable, so thank you and keep it up.

Builder

Thu Mar 30 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Regrouped navigation nodes
Updated URL format for single project mode
Enabled SAP Cloud Identity sign-in with the Builder

The navigation nodes Builder Modules, Clients, Services and Packages previous were previously in the main left menu of the Builder. All of these nodes now appear as a group under the navigation point Development.

Updated URL format for single project mode

The URL that you use to access projects in single project mode has a simplified format. The URL allows you to enter your project directly by using this new format:

https://builder.yaas.io/project/{project name}

Navigate to My Account> in Builder to enable automatic SAP Cloud Identity sign-on. You can also choose to use the SAP Cloud Identity by default. Find more details at this link: https://devportal.yaas.io/rn/services/account/latest/2017-03-30-ReleaseNotesAccount.html

There are more changes and improvements on the way. Check back soon for the latest updates.

Service SDK 4.13.6

Wed Mar 29 2017 00:00:00 GMT+0000 (UTC)

Spring Boot Starter library

The Spring Boot Starter library is the newest addition to the Service SDK. It allows you to include Service SDK functionality, out-of-the-box, into your Spring Boot project. Refer to the documentation for more information.

Spring Boot service Maven archetype

The set of Maven archetypes now includes the Spring Boot archetype. The new archetype is based on the Spring Boot Starter library. You can find more information in the Archetypes topic.

Servlet Support library

The Service SDK contains a new library, called the Servlet Support library. It is part of the aggregating libraries, so if you already have a dependency on them, this library is automatically available for you. So far, it contains the ExcludableServletFilterWrapper which allows you to exclude paths from getting mapped to an existing Servlet Filter. You can, for example, prevent the Basic Authentication Filter from securing certain endpoints. Use this functionality carefully and responsibly.

JSON Merge Patch support

The new patch version of the Service SDK adds support for the JSON Merge Patch RFC 7386.

Support for the JSON Merge Patch in the Service Generator

This feature allows you to use the recommended Merge Patch flavor for partial updates in your API as described in JSON Merge Patch RFC 7386, as shown in this example:

@PATCH
@Consumes({ PatchMediaType.APPLICATION_MERGE_PATCH_JSON, MediaType.APPLICATION_JSON }) // application/merge-patch+json
public MyType patch(MergeDto mergeDtoType);

This method accepts application/merge-patch+json and application/json content containing the partial update entity.

More flexible Service Generator

You can now enable specific template types only when generating a service with the Service Generator.

The available template types include:

DTO: data transfer objects
RESOURCE: Jersey resource interfaces
RESOURCE_IMPL: Jersey resource default implementations
TEST: abstract test class for Jersey tests
TEST_IMPL: default test implementations
FILE: static files, including applicationContext.xml and package-info.java files

For example, to just generate code for DTOs, resource interfaces, and default resource implementations, add these lines to the POM:

<configuration>
   <outputTypes>
     <outputType>DTO</outputType>
     <outputType>RESOURCE</outputType>
     <outputType>RESOURCE_IMPL</outputType>
    </outputTypes>
</configuration>

By default, overwriting of generated sources by the Service Generator is disabled. To force overwriting of existing source files, add this configuration to your POM:

 <configuration>
   <forceOverwrite>true</forceOverwrite>
 </configuration>

You can configure overwriting for specific output types only. For example, to only overwrite DTOs, add this configuration:

 <configuration>
    <forceOverwrite>true</forceOverwrite>
   <outputTypes>
     <outputType>DTO</outputType>
    </outputTypes>
  </configuration>

For details, see Service Generation.

Dockerfile added to artifacts created by Service SDK archetypes

Service SDK archetypes now create a customized Docker file at the same time as they generate artifacts. Use the Dockerfile to create a Docker build image which contains your service. Run it locally, or publish and deploy it.

To build an image with the Docker CLI-tool, execute the following command in the project root directory:

     docker build -t ${artifactId} .

To run the Docker CLI-tool locally, execute the following command:

     docker run -it --rm -p 8080:8080 ${artifactId}

Improved archetypes

Customize generated code with the provided Service Generator configuration in the archetypes. The default configuration now includes:

 <configuration>
     <outputFolderMainGenerated>src/main/java</outputFolderMainGenerated>
 </configuration>

That value forces DTO and resource interface generation into the src/main/java folder instead of the default target folder.

The build no longer integrates service generation by default. To generate the Jersey code for the endpoints, run the following:

 mvn servicegenerator:generate-service

Improved generated code quality

To disable field name prefixes, which do not follow Java naming conventions, add this configuration for Service Generator to pom.xml:

 <configuration>
    <outputFieldPrefixEnabled>false</outputFieldPrefixEnabled>
 </configuration>

Generate code into different subpackages

To keep your code clean and organized, use Service Generator DTOs, and resource and test implementations, to generate into separate subpackages. Set the outputSubpackageNameDto, outputSubpackageNameImpl, and outputSubpackageNameParam configuration properties.

For details, see Service Generation.

Sample Cloud Foundry memory settings in archetypes

The manifest files created by the archetypes now contain sample memory configuration settings. These sample memory configuration settings are used by Cloud Foundry when you deploy your service. Developers can adjust the settings to match amount of memory that their application needs. Find more information about the available settings in OpenJDK JRE Memory. To help diagnose and resolve memory issues, see Troubleshoot Out of Memory.

Integrated API Console Redirect filter clickjacking protection

The API Console now has built-in protection to prevent clickjacking attacks using the X-Frame-Options HTTP response header, which indicates whether a browser can render a page in a frame, iframe, or object.

For example, if you use the Spring Framework to define and map the API Console redirect filter, you can disallow rendering of the page in a frame by using the following property:

API_CONSOLE_X_FRAME_OPTIONS_DIRECTIVE=DENY

For details, see API Console Integrated clickjacking protection.

Maven dependency updated

The Spring dependency is now updated to the 4.3.5.RELEASE version, which corrects a reported vulnerability. Please check your Maven dependency tree and update the version to mitigate the issue.

Downgrade of the Hystrix version in the Super POM

Previously, the Hystrix dashboard did not work with the newer version of Hystrix. To resolve this issue, and to match the current version of the Jackson library, the version of Hystrix provided in the Service SDK Super POM is now downgraded from 1.5.8 to 1.5.3.

Resolved issues

An issue in the Service Generator might have caused invalid class names for DTOs generated for nested anonymous schemas. This issue is now resolved.

ERP SD Configuration v1

Wed Mar 29 2017 00:00:00 GMT+0000 (UTC)

User mapping function switch

You can now map YaaS users to ERP users. For each YaaS user, the corresponding ERP user and password are used to set up the connection with the SAP ERP system through JSONRPC. If you switch on user mapping, the communal ERP user name and password are ignored when setting up the connection. The ERP user name and password are still used to automatically mark items for deletion. If you switch off user mapping, the communal ERP user and password are used in the connection.

After you switch on user mapping, you need to maintain the corresponding ERP user name and password for each YaaS user. To do this, send an HTTP PUT request to the ERP SD Configuration service URL and the {tenant}/me/credential endpoint. To call the RESTful API, get the access token for the Resource Owner Password Credentials Grant from the OAuth2 service by providing the user name and password. For more information, see the ERP SD Configuration service API documentation.

Restricted client access to endpoint

For security purposes, only the following clients have access to the endpoint /{tenant}/ERPSDConfig:

hybris.sdorderproxy
hybris.sdcustomerproxy
hybris.erpsdconfigcui
cecenterprod.utilityproxy

Document Backup v1

Wed Mar 29 2017 00:00:00 GMT+0000 (UTC)

The new Document Backup service allows you to back up and restore your documents and your indexes. Now you can easily back up and restore your data using either of these options:

the dbr command line tool, which automates the process
REST API calls to the Document Backup service endpoints

To use the new dbr tool for document backup and restore, first download the dbr tool:

Download the dbr tool

To backup and restore documents using REST calls, use the /data/{tenant}/{type} endpoint which allows you to:

back up your documents by performing a GET request
restore your documents by performing a POST request

Good to know

The dbr tool uses the extended JSON format. To learn more, see the Extended JSON format
The dbr tool splits your data and sends it in batches of 1000 items per request
The dbr tool organizes your backups into separate folders named according to the convention: backup-{timestamp}

Features

Following are the main functionalities of the Document Backup service:

Send and receive compressed data

Add the Accept-Encoding header and set the value to gzip in your GET request in order to receive compressed data
Set the Content-Encoding header value to gzipin order to send compressed data

Index support

To have your indexes backed up along with the data, you just need to use the dbr tool. The tool backs up indexes by default. If you want to use the dbr tool and still back up or restore the data without existing indexes, you can add the skipIndexes parameter to the command for the respective operation. You can also back up your data with indexes and then set the skipIndexes parameter to restore your documents without indexes.

Check the summary of your operations

You can find information about the total number of both the insert and replace operations, the number of inserted documents, and the number of replaced documents:

In the response body when using the service endpoints
In the log file and in the console when using the dbr tool

Limits

The Document Backup service allows you to import and export big data sets with simple API calls. Such availability without any constraints could cause overconsumption of resources, and therefore, serious performance loss or a potential service outage. That is why the Document Backup service introduces limits on the number of documents you can send with a single request, and on the number of requests the service processes at the same time, to mitigate those performance risks. To learn more, see the Considerations section of the Document Backup service documentation.

Enjoy the experience the Document Backup service provides! See the Document Backup service API documentation for more information.

Cart v1

Tue Mar 28 2017 00:00:00 GMT+0000 (UTC)

When a client application sends a POST request to the /cart endpoint to create a new anonymous cart, it may now include a new optional parameter, sessionValidated. By default, the parameter’s value is set to false. If the value is set to true, the Cart service validates that the session ID received in any cart request is the same as the session ID stored in the cart. This validation prevents a user who provides only the cart ID from performing any action on an anonymous cart.

This update does not break backward compatibility. If the cart creation request does not include the sessionValidated parameter set to true, the Cart service does not perform the session ID validation and completes the request accordingly.

Earth Observation Analysis v1

Thu Mar 23 2017 00:00:00 GMT+0000 (UTC)

Enhancements to the Earth Observation Analysis service include a new JSON response format and the ability to add a numerical suffix to the dimensionTrim parameter to support multiple instances of the parameter.

New response format

The standard response type for getCapabilities and describeEOCoverageSet is text/xml instead of application/xml, and the service now supports the JSON format, application/json.

New dimensionTrim parameter suffix

You can now add a numerical suffix to the parameter dimensionTrim in the describeEOCoverageSet request. Use this suffix if web clients cannot easily handle defining the same parameter multiple times.

Here is an example of a request without the suffix: /wcs/describeEOCoverageSet?eoid=DS_RGB&dimensionTrim=phenomenonTime("2015-08-12","2015-08-13")&dimensionTrim=cloudPercentage(0.0, 40.0)

Instead, you can now get the same information using this request: /wcs/describeEOCoverageSet?eoid=DS_RGB&dimensionTrim1=phenomenonTime("2015-08-12","2015-08-13")&dimensionTrim2=cloudPercentage(0.0, 40.0)

For a detailed description of the parameters, check the Dev Portal API Documentation.

Customer v1

Thu Mar 23 2017 00:00:00 GMT+0000 (UTC)

Features

Optimistic locking for customer updates

All new customers automatically receive a version id which can be used for further updates. During customer updates, the version id supports optimistic locking. This way, changes of the update have no effect on the latest version of the customer.

Customer information in the email templates

You can use customer data, such as sign-in email, firstName, lastName, contactEmail etc. to send personal emails to your customers. For example, you can add the customer’s first and last names to the address line of the email by inserting the following code:

 ${tools.esc.html(${d.customer.firstName})} ${tools.esc.html(${d.customer.lastName})}

For a detailed list of available attributes, see the Customer service documentation.

Dev Portal

Thu Mar 23 2017 00:00:00 GMT+0000 (UTC)

Duplicate release note emails

Recent feedback from the community indicated there was an issue with duplicate notifications about release notes. Recently, you might have received an email notification with a list of release notes published previously. For example, a notification sent on 2 February 2017, concerned release notes from May 2016 about the Loyalty Email service.

The issue was in the backup mechanism, which operates when generating documentation on the Dev Portal. As a result, the affected release notes disappeared from the Dev Portal and came back after the next document generation, which caused the resending of the release notes.

The issue is now resolved.

Thanks to the community feedback, an issue with navigation in the API Docs is resolved. Previously, when browsing through the services documentation, after choosing Europe or the United States as the preferred market, the link to the API Docs landing page changed at the same time, and did not work as expected.

The issue is fixed now, and you can smoothly navigate within the API Docs.

Your feedback is very important and valuable, so thank you and keep it up.

YaaS Events

Tue Mar 21 2017 00:00:00 GMT+0000 (UTC)

YaaS Events page discontinued

Dear YaaS Community,

Six months ago, the YaaS Events page launched, to help you find out more about YaaS-specific events and activities, events featuring YaaS, and where to meet the YaaS experts. During this time, active analysis of the usage and the number of events shared on the page spurred the decision to discontinue and remove the page from YaaS.io.

YaaS will still continue to be featured at and host events, but announcements will appear on more popular channels.

Regards, The Yaas Team

Document v1

Fri Mar 17 2017 00:00:00 GMT+0000 (UTC)

Now, the /{tenant}/{client}/data/{type} endpoint returns data with chunked transfer encoding.

What does this mean?

Using chunked transfer encoding, the service does not wait to get all the queried data from a database, but responds by transferring data in segments. This improvement helps the Document service manage its memory more efficiently.

Example: Previously, if you queried 100 documents with the /{tenant}/{client}/data/{type} endpoint, the Document service waited until the database returned all 100 documents and stored them in internal memory. Next, the Document service returned a full response. If you multiply this behavior by the number of tenants, the process can use a lot of memory.

In the improved flow, the service sends documents that the database returns in response chunks, without waiting for all of the documents.

For more information, see Chunked transfer encoding.

Impact of this improvement

You do not need to change anything. All REST clients supporting HTTP/1.1 can use chunked transfer encoding by design.

RAML Patterns 1.3.3

Thu Mar 16 2017 00:00:00 GMT+0000 (UTC)

Protection against clickjacking

The RAML Patterns site uses the X-Frame-Options HTTP response header to protect against clickjacking attacks. The response header indicates whether a browser can render a page in a frame, iframe, or object.

Cart Calculation v1

Fri Mar 10 2017 00:00:00 GMT+0000 (UTC)

Previously, the Cart Calculation service did not apply the rounding strategy until finalizing the cart total. This meant that each value, such as item price and tax, used to calculate the cart total, was not rounded until the calculation completed. In some cases, this caused the item price to calculate incorrectly. To resolve the issue, the service now applies the roundup strategy after calculating each item's price, as well as at the end of the cart calculation.

Knowledge Hub

Thu Mar 09 2017 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, an issue with the rendering of descriptions for Knowledge Hub articles is resolved. Until now, it was not possible to use HTML tags in the descriptions. HTML tags are enabled by default now. You can see the change in the example images:

This is how an article description rendered before:

This is how an article description renders now:

Your feedback is appreciated. Keep sharing your suggestions for improvement.

Product v2

Wed Mar 08 2017 00:00:00 GMT+0000 (UTC)

You can now use product variants to enhance the current features and functionality of the Product service.

Variants

With variants, you can introduce different types of a single product. Product variants help you to further differentiate items within a type.

Media in variants

Variants can also include media, providing highly-customized visualization, representing the specific qualities of a variant that might appeal to customers. With media in variants, customers can see images prepared specifically for each product variant you offer.

Query variants

The Product service supports querying, not only for products, but for variants, too. Knowing the variant's identifier allows you to run a simple query and retrieve any variant you want, no matter which product it comes from.

Query both products and variants in a single call

You can query for variants and products in one single call. By using additional parameters, you can also decide the amount of information you want to get for each product and variant that you query. The retrieval of non-public products requires authorization, while the retrieval of public products does not.

Search v1

Mon Mar 06 2017 00:00:00 GMT+0000 (UTC)

The Search service will no longer be supported after July 1st, 2017. It will be deprecated.

For full text search functionality, use the text search feature in the Document service instead: Full Text Search

If you have questions about this announcement, use the Feedback button. In the mean time, stay tuned for more YaaS news.

Customer v1

Mon Mar 06 2017 00:00:00 GMT+0000 (UTC)

Improvement

Additional scope hybris.sapcommunity_configuration_view for a logged in customer

The service grants the additional scope hybris.sapcommunity_configuration_view to a signed in customer. If you do not have subscription to the sapcommunity project, you may ignore it.

Builder

Fri Mar 03 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Bookmarking of organizations

Bookmark your favourite organizations

Use the star in the drop-down navigation to indicate your favorite organizations. The starred items will appear first in your list of organizations.

Checkout v1

Tue Feb 28 2017 00:00:00 GMT+0000 (UTC)

Previously, the Checkout service returned a 500 error when you tried to check out a cart with more than 100 items. Upon further investigation, the error occurred during the checkout process when the Checkout service called the Price service to retrieve the prices. If there were more than 100 items in the cart, the service returned a 500 error. This issue is resolved by retrieving a maximum of 80 item prices at a time. As a preventative measure, the Checkout service also retrieves 80 products at a time.

Order v1

Mon Feb 27 2017 00:00:00 GMT+0000 (UTC)

Product variants

To allow merchants to sell customized products, the order creation schema now includes product variants. Variants can define product attributes such as color and size to help buyers refine their selections. You can extend the variants further by using variant options and mixins.

Email notifications

Two new types of email notifications for shipments and cancellations contain information about the orders that buyers need. Buyers receive an Order Shipped notification email when the order status changes from CONFIRMED to SHIPPED. When the merchant or the buyer changes the order status to DECLINED, the change triggers an Order Canceled notification email. You can modify the email templates if you are subscribed to the Email service. The Order service API documentation on the Dev Portal lists and explains the variables you can use in the templates.

Use PATCH instead of PUT for partial updates

Now you can use the PATCH method for partial updates. The method works the same way as the PUT requests. Although both the PUT and PATCH methods provide the same functionality, it is recommended that you use PATCH. PATCH provides a clear separation of method semantics, is easy to use on the client side, and is well defined and fully compliant with all specifications. You can find more information in the blog post PATCHing the API guideline on partial updates.

New `lastStatusChange` field

A new field, lastStatusChange, is available in the order schema. It is a timestamp, and and each time the order status changes, the value of lastStatusChangeautomatically updates.

New `expectDeliveryOn` field

The new field `expectDeliveryOn, stores the expected delivery date for order shipments.

Engagement Center UI Configuration v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

The latest update to the Engagement Center UI Configuration service provides several updates, described in this release note.

New scopes endpoint and deprecated endpoint

Use the new endpoint /{tenant}/userScopes to retrieve all scopes that are granted to a user with specified role(s) in the Engagement Center, such as AGENT and SUPERVISOR. The endpoint /{tenant}/requiredScopes, that enables the Agent Home to acquire an access token, will be deprecated in May of 2017.

Delete custom tiles

Use the endpoint /{tenant}/tilesConfig/{id} to delete the tiles developed by customers. For more information, please see Remove Configurations

Side panel view configuration

Use a new endpoint with the GET, POST, PUT, and DELETE methods to configure the side panel views for the Engagement Center. The endpoint is /{tenant}/sidePanelConfig.

To configure a view for the side panel in the Engagement Center, maintain this data:

viewname – A unique name for the view
viewpath – A fully-qualified path that points to the view, including the name of the view
viewtitle – The I18N or text key that represents the view title
viewdescription – A description for the configuration record
order – A numeric value that determines the order of the views displayed in the side panel
active – A Boolean value of true or false that activates or deactivates the configuration

Update to language-dependent text support

There is a new endpoint /{tenant}/texts/default that returns the default text groups. To update or create a list of text groups using the endpoint /{tenant}/texts, include the default groups in your request. Otherwise, the system returns an error message.

Automatically collapsible Header Area

You can now configure the header area to automatically collapse when an account is identified by setting the configuration parameter HEADER_AREA_AUTOMATIC_COLLAPSE to true. You can read and change the parameter HEADER_AREA_AUTOMATIC_COLLAPSE using the endpoint /{tenant}/configParameters. To set the parameter, call the POST or PUT method of this endpoint using the provided example. By default, the value of the parameter is set to false. This means that the header area does not automatically collapse.

Account Searches

As part of the header area of engagement context, the account search provides functionality to search and confirm an account. As of this release, with this end points is now possible to customize the search services used in the account search.

GZIP format supported for content encoding

The Engagement Center UI Configuration service now supports the GZIP format for content encoding. To send compressed data to the Engagement Center UI Configuration service, set the Content-Encoding header with the gzip value. To retrieve your data in the GZIP format, use the Accept-Encoding header with the gzip value.

Security enhancement

When you send a POST, PUT, or DELETE request to the Engagement Center UI Configuration service, ensure that you provide the field hybris.user with a value.

ERP SD Sales Order Proxy v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

The ERP SD Sales Order Proxy service now supports the masked display of payment card numbers. When you activate this function in the SAP ERP system, the service returns the payment card number in the format you configure in the SAP ERP system. Otherwise, the service returns the number in the default format.

To use this function, enable payment card processing by calling the ERP SD Configuration service, and implement the SAP Note 2405050.

ERP SD Configuration v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

Switch flag for Payment Card Processing

You can now use the ERP SD Configuration service to manage the switch setting to enable/disable payment card processing. The switch indicates whether the payment card should be displayed in ERP Sales Order (switch on) or Not displayed (switch off).

Engagement Center Customer v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

In this release, two updates support the ability to automatically trigger the deletion of ERP customers in the system, as well as provide the ability to map the corresponding SD customer number.

Mark ERP customer for deletion automatically

After you delete a customer profile, the customer-deleted event automatically marks the ERP customer for deletion in the SAP ERP system.

Manage mapping between the customer number and SD customer number

After you delete a customer profile, the system automatically deletes the corresponding ERP customer and the mapping entries. If an error occurs in the automatic deletion process, you can retrieve the mapping entries to verify which entries failed, and repeat the action by calling the relevant API.

Engagement Center Indexing v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

Performance improvement

The Engagement Center Indexing service now adopts the push-based message delivery of the PubSub Service to improve the service's performance, and greatly reducing the processing time of delta indexing.

Dev Portal

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

The API Docs landing page is easier to read

The number of YaaS markets is continuously growing, and listing them all on API Docs landing page makes it long and cumbersome to read. Therefore, the market indicators are now removed from the page, and it is easier to read.

For example, this is how the market indicator appeared on the landing page before:
This is how the landing page appears now:

Your feedback is very important and valuable. Thank you and keep your feedback coming.

Configuration v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

Data compression

To improve the performance and lower the bandwidth usage within the Configuration service, this release introduces the capability to use the content encoding in the GZIP format, both while sending to, and receiving data from the service. The larger the amount of data to process, the greater the performance improvements you see.

The Content-Encoding header

For write requests, such as POST requests, use the new Content-Encoding header with the gzip value set and body compressed. This way, data transfer consumes fewer resources.

The Accept-Encoding header

For all requests, use the new Accept-Encoding header with the gzip value set. This way, the response body gets compressed and data transfer consumes fewer resources. The service response will include the Content-Encoding header.

Always use the GZIP encoding, both when sending big data sets to the service and when expecting the response body from the service to contain a large amount of data.

SAP Jam Communities v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

Retrieve access token

The SAP Jam Communities service now supports the retrieval of a generated access token. Use this token to connect with SAP Jam Communities.

Manage knowledge article references

The SAP Jam Communities service now supports to manage references between the knowledge articles and the user-defined objects, such as service ticket.

Interaction Recording v1

Fri Feb 24 2017 00:00:00 GMT+0000 (UTC)

Chat participants aliases in chat transcripts

The Engagement Center Interaction Recording service now supports a new field chatterDetails. You can use this field to retrieve the basic information of the chat participant, including id and default alias.

Builder

Wed Feb 22 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Drop-down navigation for organization and project selection
Customized cropping of the organization profile image
Relocation of development nodes in the left navigation

Selecting an organization or project is now easier thanks to a drop-down list, featured in the main menu, that allows you to find and select an organization or project to work on.

Customized cropping of the organization profile image

Previously, when you selected a profile image for your organization, the Builder automatically cropped and displayed the image in the profile with no additional options. Now, you can specify an area of the selected image to use as the profile image.

The navigation nodes that relate to development now appear at the bottom of the left navigation. These nodes include Clients, Services, Builder Modules and Packages.

There are more changes and improvements on the way. Check back soon for the latest updates.

Customer v1

Thu Feb 16 2017 00:00:00 GMT+0000 (UTC)

Improvements

Use PATCH instead of PUT for partial updates

Now you can use the PATCH method for partial updates. The method works the same way as the PUT requests. Although both PUT and PATCH methods provide the same functionality, we encourage you to use PATCH. PATCH provides a clear separation of method semantics, is easy to use on the client side, and is well defined and fully compliant with all specifications. You can find more information in our blog . The endpoints affected by this change are:

/{tenant}/customers/{customerNumber}
/{tenant}/customers/{customerNumber}/addresses/{addressId}
/{tenant}/me
/{tenant}/me/addresses/{addressId}

Performance improvements in the customer service

We have improved the performance of the customer service by optimizing the fetching and caching mechanism of the authentication tokens used by the customer service.

Migration from PubSub PULL event consumption to PubSub PUSH subscriptions

From now on, internal consumption of PubSub topics uses PUSH subscription. This way we have improved internal performance of PubSub events processing.

Bug Fixes

Problems of incorrectly formatted customer token fixed

In some special cases, after calling the /{tenant}/login endpoint, the customer token returned to a client was incorrect - it contained some extra characters which made the token unusable. We have identified the cause of the issue and successfully resolved it.

Dev Portal

Thu Feb 16 2017 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, the background color, and therefore the visibility of the HTTP verb PATCH in the API Reference section is improved.

Before:
After:
Your feedback is very important and valuable. Thank you and keep your feedback coming.

Email v2

Thu Feb 16 2017 00:00:00 GMT+0000 (UTC)

With the latest release, you can now send attachments with your outgoing emails. A new section of the Email service documentation describes how to use the new functionality.

Velocity Template Builder Module v1

Tue Feb 14 2017 00:00:00 GMT+0000 (UTC)

Velocity Template Builder Module

You can now create and delete your templates directly in the Builder. You can perform all template management tasks using the Builder web interface instead of having to make direct REST calls. To manage templates in the Builder, select your project and click Velocity Templates. Click + TEMPLATE to create a new template or select a template to modify.

hybris techne v1.5.5

Thu Feb 09 2017 00:00:00 GMT+0000 (UTC)

Multi-tab Editor

The former Localization Editor is now renamed to the more generic Multi-Tab Editor. You can use the Multi-Tab Editor to collect information with multiple dimensions, such as prices on different currencies and data in different regions.

Minor improvements

The Starter Page Details 1 now reflects changes for displaying and updating avatar images.
The header style is now the same for the Tree and Table patterns.
The Tree pattern now highlights any row when you hover over it with your cursor.
The Tone and voice guidelines are updated.
The Help bubbles pattern is improved and now appears on top of other elements on the page.
The padding of the Static Form Elements is improved to provide a more compact look.
The references to the CSS Icon-Font file now have a dynamic hash to prevent caching issues.
The Cards pattern is updated to display a nicer shadow effect, and looks less "bumpy" when interacting with the cards.

Deprecated Localization Editor

The Localization Editor is now deprecated. This component's CSS classes are still active but only for the next two releases. Use the new Multi-tab Editor from now on.

Email v2

Mon Feb 06 2017 00:00:00 GMT+0000 (UTC)

In this new major version of the Email service, several improvements allow it to focus on email sending operations, while connected functionality has been moved to helper services. You can also use the new helper services independently. See the Velocity Template service and the YaaS Verification service for more details.

This architectural split enables scaleable functionality for individual services, leading to better overall performance. This model also allows the delivery of new features faster, thanks to the reduced complexity of each service.

The email sending request is also optimized and, by design, provides you with the choice to send emails with content rendered using the Velocity Template service, or with email content that you provide directly in your request.

The new services have been introduced next to Email service v1 in the current Email package to enable a smooth transition to the new APIs, at the moment of your choice, until the future introduction of the new Email package which will no longer include Email service v1. Check out the documentation for the Email Service v2 and the step-by-step guide that describes how to adjust your service to use the new version.

Builder

Fri Feb 03 2017 00:00:00 GMT+0000 (UTC)

This release includes these new features and improvements:

Reorder projects by drag-and-drop
Developer Mode in the Builder
Invoice is available as a payment method

Reorder projects by drag-and-drop

In the past, projects appeared on the product overview page in the order of creation only. You can now change the order by dragging and dropping each project. Click REORDER at the top right of the screen to activate reorder mode. Simply drag-and-drop the projects in the order that you want them to appear.

Developer Mode in the Builder

Developer Mode makes it possible for developers to step away from the Builder CLI to preview content directly in the Builder. Switch on Developer Mode to see the navigation nodes that you created for your Builder module in the left-hand navigation. You can also preview your project directly in the Builder.

Open Developer Mode under Project > Administration > Development. Click OPEN PROJECT IN DEV MODE. A dark gray bar appears at the bottom of the screen indicating that you are in Development Mode. You can access Dev Mode settings or exit Developer Mode using this bar.

Invoice is available as a payment method

Under Settings > Administration > Contact & Billing, you can choose an invoice as a method of payment. As with other methods, you can set an invoice as the default. To use the invoice method, you must request it. After SAP Hybris approves the request, it is then available.

There are more changes and improvements on the way. Check back soon for the latest updates.

Document v1

Tue Jan 31 2017 00:00:00 GMT+0000 (UTC)

Now you can use a new, full text search feature in the Document service. The new feature allows you to search for text in string fields in your documents. You can even use text search in combination with regular query.

The Document service full text search feature supports:

case-sensitive and case-insensitive search
diacritic-sensitive and diacritic-insensitive searches to recognize or ignore text with accent marks
searching in a specified language
applying weights to text fields
scoring search results

To search for documents using the full text search feature, use the new text query parameter. Check out the Full Text Search documentation for further details.

Before using text search, you must create a text index. Because there are system limits on simultaneous index creation, refer to the tips in this release note to minimize your risk of exceeding those limits.

Document v1

Fri Jan 27 2017 00:00:00 GMT+0000 (UTC)

As previously announced in this blog post, from now on, there are new limits on the number of indexes you can create simultaneously. This change is dictated by the aim to constantly improve the resiliency and overall performance of the Document service, which is a shared environment.

From now on, you can create:

a maximum of five indexes simultaneously, per client
a maximum of 20 indexes simultaneously, per <%- @partial('document_storage') %>

When you exceed one or both of these limits, you receive a 429 Too many requests response from the Document service. In that case, you must wait until the current index build operation ends and clears the index creation pool.

You can minimize the risk of exceeding the limits by planning your indexes ahead of time, and creating them for empty or small collections, instead of building an index for a massive data set that could take a very long time to process.

Dev Portal

Tue Jan 24 2017 00:00:00 GMT+0000 (UTC)

Multi Select

The API Docs section of the Dev Portal is simplified, along with improvements to filtering on the Release Notes page. These changes make the Dev Portal consistent with Techne patterns, promoting a consistent user experience throughout YaaS.

These are the latest updates:

In the Packages drop-down list, you can click the checkboxes to select multiple packages.
The Filter menu takes less screen space when expanded.
The Country Availability filter is visible immediately when the page loads.

This screenshot shows the latest improvements:

The Dev Portal now has a third-level of navigation on the left-hand side, which makes content much easier to find in lengthy sections. Click on the third-level headings, to navigate directly there! Also, the play button for interactive tutorials in the API Documentation section is removed from the navigation because it was distracting to users. In addition, the clickable expand arrow is moved from right to left to be consistent with the existing tree structure.

For example, this is how the play button appeared in the navigation before:

This is how the navigation appears now:

Your feedback is very important and valuable. Thank you and keep your feedback coming.

Cart Calculation v1

Fri Jan 20 2017 00:00:00 GMT+0000 (UTC)

Previously, the addition of a second discount to a cart caused an issue if the value of the discount's sequence ID, an optional attribute, was null. In those cases, the calculation resulted in an error.

The issue is now resolved. Now you can add multiple discounts to the cart and the total calculates properly.

Verification v1

Thu Jan 19 2017 00:00:00 GMT+0000 (UTC)

The Verification service allows you to verify the validity of email addresses and domains. The service offers these features:

Domain Verification verifies that the domain name exists by checking whether there are DNS records of the type MX, CNAME and/or A, configured for the service, which makes receiving email theoretically possible.
Email Address Verification verifies whether the email is properly formatted, and whether the domain component of the email address is a valid domain for receiving emails from YaaS. This email address verification works with the Domain Verification feature. You can use this feature to pre-validate an email address before sending an email to it, or before starting any lengthy process that relies on an valid email address.
Project Custom Domain(s) verification retrieves the verification status of one or more domains registered for a project, including the projects' verification token(s). This verification is required to overcome current limitations when using the Email service with a FROM address that does not belong to the domain {yourProjectId}.mail.yaas.io, where {yourProjectId} is the ID of your project.
Project Custom Domain(s) registration registers one or more domains in YaaS as belonging to your project.

RAML Patterns 1.3.2

Wed Jan 18 2017 00:00:00 GMT+0000 (UTC)

Adjusted the resource-type-element pattern to use application/merge-patch+json as body Content-Type. This change is aligned with recent Service-SDK changes.

Velocity Template v1

Wed Jan 18 2017 00:00:00 GMT+0000 (UTC)

The Velocity Template service allows you to create and upload Velocity templates that you can render later by making a simple REST call. The service provides flexible template management using Velocity-based templates. It also allows you to specify placeholders inside the template that you can later fill with custom data.

Use the Velocity Template service to:

Create and manage templates for any use case.
Render templates using the Velocity Template Language.
Create multiple variants of Velocity templates for variable requirements, such as different languages and locations.

Document v1

Tue Jan 17 2017 00:00:00 GMT+0000 (UTC)

Now you can manage your documents in a Builder module for the Document service: The Document Explorer. The Document Explorer is a user interface that provides you with:

easy access to an overview of your documents
convenient and transparent index management
instant access to your statistics

The Document Explorer include these tabs:

The Data tab allows you to list all documents of a given type and display them, one-by-one, when necessary.
The Index tab allows you to list all indexes for a given type, along with corresponding details. You can also create or delete indexes in this tab.
The Tenants tab provides outstanding value for tracking and planning the costs that apply to Document service usage, as well as deciding which rate plan to choose, and making sure you don't exceed your quota. On the Tenants tab, you can view the total number of:
- tenants you currently manage
- types you store in the Document service
- indexes created for your tenants
- the size of your total Document service storage
Check out the Document Explorer documentation and the Document Explorer step by step guide for further details and screen shots.

If you are already subscribed to the Persistence package you need to update your subscription to have access to the Document Explorer. In order to do that, go to your subscriptions under the Administration tab for your project, choose the Persistence package and click UPDATE.

Dev Portal

Mon Jan 09 2017 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, an issue was discovered with broken links to specific service's release notes. The issue is now resolved.

Your feedback is very important and valuable. Thank you and keep your feedback coming.

hybris techne v1.5.4

Tue Jan 03 2017 00:00:00 GMT+0000 (UTC)

Hot Fix

This is a patch release to fix the Feedback Menu icons rendering issues on Windows machines

Knowledge Hub

Mon Jan 02 2017 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, an issue was discovered with sorting articles by date. If you sorted the list of articles by Newest, they didn't sort properly due to improper date format handling. For example, articles in September displayed before those in November. The issue has been resolved. See the Knowledge Hub to see the new sorting in action.

We appreciate your feedback. Keep letting us know how we can improve.

Storefront Template v1.0.7

Fri Dec 23 2016 00:00:00 GMT+0000 (UTC)

This release of the Storefront Template has the following new features:

Product fee displays on various pages
Product search related updates
AngularJS upgrade
Product variant information in the order details and the order confirmation page

Product fee displays on various pages

As a merchant, you can add fees to any of your products or items. An example of an additional charge on an item is a deposit fee on returnable bottles when you purchase beer. The fee can be one of the following types:

Absolute fee: An amount that is applied on an item or on the item quantity, such as a $5 fee for every six-pack of beer.
Percentage fee: An amount that is applied on an item, such as 5%.

When a customer selects an item in the Storefront, the Product Details page now shows the fee, if applicable, that is added to the item, such as a $0.60 fee for each beer bottle shown in the following screenshot:

The fee also displays in the customer's cart and in the Order Details page. The amount shown in the TAX line represents the taxes on the items, and the fee, if applicable.

To display the fees, define the URL of the Fee service in the Site service and create fees for the products using an external fee provider. For more information about the Site service configuration, see the Configuration page.

For information about the Cart Calculation service's supported fee types and how fees are calculated in the cart, see the Cart Calculation Process page.

This release includes updates that prepare the Storefront for upcoming changes to the product indexing with the Algolia Search service. Pull the latest Storefront updates as soon as possible to ensure that the upcoming Algolia Search service release does not interfere with the ability to use the search functionality in the Storefront.

Previously, product records sent to Algolia were indexed by the unique product ID value. With the new release, Algolia uses the value of the product's YRN property in the Algolia index instead of the product's ID property. You can use the search functionality regardless of whether your data is indexed by product ID or YRN. But to handle both types of Algolia indexing, it is strongly recommended to update as soon as possible, or the search functionality could cease to work in your Storefront.

AngularJS upgrade

AngularJS and its related libraries are now updated to the latest stable versions. The library base is renewed and the Storefront is adjusted to the features of the new libraries.

The following Angular, and Angular-related libraries are updated to the specified versions:

angular: 1.5.9

angular-mocks: 1.5.9

angular-sanitize: 1.5.9

angular-touch: 1.5.9

angular-animate: 1.5.9

angular-bootstrap: 2.3.0

angular-ui-select: 0.19.6

Product variant information in the order details and the order confirmation page

Support is added to display product variant information in the order details and the order confirmation pages. Although the support is implemented now, it becomes available only when the next version of the Order service is released, and the Storefront is linked to this new version.

Stay tuned for updates in future Storefront releases.

Community

Fri Dec 23 2016 00:00:00 GMT+0000 (UTC)

New card called "Create your own Showcase!" on Community Showcases

Want to know how to create your own showcase? Community Showcases now has a card on the list called, "Create your own Showcase!". Click on the card to get all the information on how to do it!

Document v1

Thu Dec 22 2016 00:00:00 GMT+0000 (UTC)

New with this release is the response body for all GET requests on the /{tenant}/{client}/indexes/{type}/{name} and /{tenant}/{client}/indexes/{type} endpoints.
The new format of the response body helps meet the highest standards of consistency between different types of requests, as shown in this example:

{
  "keys" : {
    "some_field" : "1",
    "another_field" : "-1"
  },

  "options" : {
    "unique" : true,
    "name" : "myIndex"
  }
}

Response body format changes

These changes appear in the new response body format:

The keys keyword is now added to meet the convention required for POST requests. This new keyword will completely replace the key keyword in next three months.
Unnecessary attributes, such as v, background, and ns are removed.
The values for the options parameter are included in the subdocument in exactly the same way they are required for write requests.

Do I have any time to adjust?

Because some implementations still expect the previous version of the response body format, response bodies will contain both formats for the next three months. This is to ensure backward compatibility and allow you to check and adjust before old deprecated format is removed from the response body.
The format that includes the old and new versions of the response body looks like the example shown:

{
  "keys" : {
    "some_field" : "1",
    "another_field" : "-1"
  },

  "options" : {
    "unique" : true,
    "name" : "myIndex"
  },
  "unique" : true,
  "name" : "myIndex",
  "key" : {
    "some_field" : "1",
    "another_field" : "-1"
  }
}

Please note that deprecated fields: key and options on the document level will be completely removed after March 22nd, 2017.

Cart Calculation v1

Wed Dec 21 2016 00:00:00 GMT+0000 (UTC)

Scaling and rounding logic updated

Previously, the scaling and rounding logic was applied at different parts of the cart calculation and it was not applied consistently across all monetary values. This created inconsistency in the values that were sent back to the Cart Calculation service. Not only were the values inconsistent, but applying scaling at various points also meant that the overall calculation lost some precision. To resolve these issues, the scaling is removed from various services and the roundup strategy is now only applied to the monetary values in the response of the cart calculation.

Removal of unneccessary attributes from the calculation response

Previously, if there were fees applied to a product, the Cart Calculation service returned various fee attributes that were of no value to the calculation response. These unnecessary attributes are removed and now only the pertinent attributes return in the calculation response.

Earth Observation Analysis v1

Wed Dec 21 2016 00:00:00 GMT+0000 (UTC)

Data Access

Improved availability and performance of data retrieval.

Cloud Filter

Satellite images can now be filtered for their cloud percentage, which helps users to find useful images. For more details, check Dev Portal API Documentation.

Normalized Burn Ratio (NBR)

NBR dataset series added for assessing fire severity.

Dev Portal

Wed Dec 21 2016 00:00:00 GMT+0000 (UTC)

Thanks to community feedback, the tables style no longer suggests that table cells are clickable. Now, when you hover over the table cells, you see the arrow cursor and not a hand cursor. See the Glossary table, which shows the current design.

Your feedback is very important and valuable. Thank you and keep your feedback coming.

hybris techne v1.5.3

Tue Dec 20 2016 00:00:00 GMT+0000 (UTC)

New Pattern

A new pattern defines how to display avatars and images on cards and tables -using standard sizes. This pattern also defines the HTML markup and the user interaction to follow when uploading or changing images.

Minor updates

The Tree Pattern HTML Markup is simplified. Complex use of CSS classes along with HMTL attributes is improved.
The Toggle buttons now have a stylized 1/0 label instead of on/off. This change provides a more universal, conceptual representation for the toggle buttons, so there is no need to translate the button labels.
Improved accessibility on the Expandable Button. The expandable options are now in a more accessible order. Secondary options are now at the bottom of the widget and do not obscure the primary options anymore.
Checkboxes and Radiobuttons components now represent the :focused and :active statuses visually.
The Localised Editor is extended to display static content.

Price v1

Thu Dec 15 2016 00:00:00 GMT+0000 (UTC)

An invalid date range now returns the correct error notification

Previously, if you used the date range attribute when creating a product price, and a value was invalid, for example, April 31, the service returned a 500 internal service error. With this update, the service returns the correct, and more informative, 400 validation violation, along with the message, The date format should be ISO 8601..

Checkout v1

Thu Dec 15 2016 00:00:00 GMT+0000 (UTC)

Updates in managing the language header to support the Product service V2

Because the Product service V1 will be deprecated by the end of December 2016, the Checkout service now uses the Product service V2. The Product service V2 changes the way the service handles the language header, in that it no longer falls back to an en locale. This change causes the Checkout service to retrieve, at times, incorrect data from the Product service. To resolve this issue, the Checkout service now provides a fallback locale of en when a request to the Checkout service does not include the en locale in the language header. This change maintains the current Checkout service V1 API contract.

For the Checkout service consumers who properly providing the language header, this update has no impact.

Dev Portal

Wed Dec 14 2016 00:00:00 GMT+0000 (UTC)

New improved API Docs and Release Notes search

We received feedback from the community, concerning unintuitive searching on API Docs and Release Notes. To provide the best possible experience for our users, we decided to improve search functionality, by adding magnifier icon into search field.

After filling search field, 'x' icon will apear, giving a posibility to quickly clear the search field.

Color of HEAD method

Thanks to community feedback, the background color, and therefore the visibility of the HTTP verb HEAD in the API Reference section is improved.

Before:
After:

Your feedback is very important and valuable. Thank you and keep your feedback coming.

Tax v1

Tue Dec 13 2016 00:00:00 GMT+0000 (UTC)

Rounding logic removed from the Tax service

Previously, the Tax service had a rounding logic when calculating the taxes for the cart. The rounding logic is applied to the calculated tax value before the Tax service passes the value to the Cart Calculation service. When the rounding logic is applied here, the Cart Calculation service loses some calculation precision.

To improve the precision of the cart calculation, the Tax service now passes its values without any rounding or scaling logic. Previously a tax of 1.9545 would be returned as 1.95. Now the Tax service takes the entire value (1.9545) and passes that value to the Cart Calculation service.

This improvement is also applied to the Tax Avalara and Cart Calculation services so there is consistency between all of the services.

Avalara Tax v1

Tue Dec 13 2016 00:00:00 GMT+0000 (UTC)

Rounding logic removed from the Avalara Tax service

Previously, the Avalara Tax service had a rounding logic when calculating the taxes for the cart. The rounding logic is applied to the calculated tax value before the Avalara Tax service passes the value to the Cart Calculation service. When the rounding logic is applied here, the Cart Calculation service loses some calculation precision.

To improve the precision of the cart calculation, the Avalara Tax service now passes its values without any rounding or scaling logic. Previously a tax of 1.9545 would be returned as 1.95. Now the Avalara Tax service takes the entire value (1.9545) and passes that value to the Cart Calculation service.

This improvement is also applied to the Tax and Cart Calculation services so there is consistency between all of the services.

PubSub v1

Fri Dec 09 2016 00:00:00 GMT+0000 (UTC)

Push-based message delivery

This release marks a major milestone for the PubSub service. Previously, it allowed you to consume events only by actively pulling them from topics. Now, the PubSub service additionally offers push-based message delivery. This means that PubSub pushes events to you on demand.

When to use push message delivery

If you need performance closer to real-time.
If you prefer a simpler solution to the pull approach.

Get started!

Set up an HTTPS-enabled endpoint, protected by Basic Authentication.
Use the new Push Subscription API to subscribe to a topic.
Wait for the events to arrive.

For more information, check out the completely revamped PubSub service documentation.

Customer v1

Fri Dec 09 2016 00:00:00 GMT+0000 (UTC)

When signing into the Customer service through Facebook or Google takes longer than two seconds, the service times out so that the users can try again.

Better error handling for the race condition when updating a customer

In rare cases, simultaneous updates of a customer profile causes a race condition, when the service is unable to complete the updates in the correct sequence. Previously, the service returned the error code 500 with an ambiguous message. With this update, the service now returns the error code 409 with an appropriate message.

hybris techne v1.5.2

Tue Dec 06 2016 00:00:00 GMT+0000 (UTC)

New Pattern

There is a new pattern that highlights new and unsaved data elements. This pattern can be applied to cards, tables, and trees. An example of this pattern used in a tree, is shown in the following screenshot:

Minor updates

A new modifier class added to the expandable button pattern prevents the expanded options from breaking the other elements in the layout.
There is a new Custom Select element added to the form components.
There are improvements to the documentation.
Vendor-specific CSS prefixes are now added automatically

YaaS Events

Mon Dec 05 2016 00:00:00 GMT+0000 (UTC)

Three new icons on the details page for each event allow you to share your events on Facebook, LinkedIn, and Twitter. Under those icons, some events might include a Twitter hashtag that you can use to share information. For example, #sapteched.

Service SDK 4.12.1

Mon Dec 05 2016 00:00:00 GMT+0000 (UTC)

This release of the Service SDK provides expanded functionality for the Rammler code generator, and a resolution to a previous issue involving overwritten DTOs.

Code generation for PATCH and OPTIONS in client generator

The Rammler code generator now supports using the PATCH and OPTIONS methods for clients generated from RAML files.

Resolved Issues

An issue in which the service generator might have overwritten DTOs with duplicate names is now resolved. A new renaming strategy appends digits to the class name when the service generator encounters duplicate names.

Document v1

Fri Dec 02 2016 00:00:00 GMT+0000 (UTC)

New headers to support data compression

New with this release is the capability to use GZIP content encoding while receiving data from, and sending data to, the Document service. Compressing data during transfer provides a significant reduction in bandwidth used, and thus, response times. The bigger the data set received from or sent to the Document service, the bigger the performance improvements. Two new headers enable the GZIP content encoding functionality in the Document service. To compress large data sets, include the new headers in your request and set the values to gzip.

The Document service supports these new headers:

Content-Encoding for write requests
Accept-Encoding for read requests

How to use the headers

To experience the benefits of this new functionality, set one additional header in your requests to the Document service:

For read requests, such as GET requests, use Accept-Encoding : gzip.
For write requests, such as PUT or POST requests, use Content-Encoding : gzip.

Cart Calculation v1

Fri Dec 02 2016 00:00:00 GMT+0000 (UTC)

Proper rounding is now applied to a discounted item price

Previously, when an absolute discount value applied in the cart caused the new item price to be a trailing decimal value, it resulted in a failed cart calculation. For example, when a discount amount of $10.00 is distributed proportionally across three items in the cart, it causes the new item price to be a trailing decimal value, which caused an error during the calculation.

To resolve this issue, a minimum precision of ten digits after the decimal is now applied. If the 11th digit is equal to, or larger than, a value of five (5), the 10th digit is rounded up.

Media v2

Tue Nov 29 2016 00:00:00 GMT+0000 (UTC)

Use the fallback query parameter along with the GET request to query on variants. For example: ?clip=300x200 on the:

/files/{fileId} endpoint
/public/files/{fileId}endpoint

The default value for the fallback query parameter is false. Set the value to true so that, when a particular variant does not exist, the Media service returns the master media file instead of a not found response.

Community

Mon Nov 28 2016 00:00:00 GMT+0000 (UTC)

Find out how often your Community Showcase was viewed

Showcase owners can find out now how often their showcases were viewed in the last seven days, and in the previous seven days before that.

As a showcase owner, you can use the statistics feature to see if the interest to your showcase increased. To see the statistics, go to the Builder and select Projects -> My Project -> Packages -> My Package -> Showcase. You may need to refresh your screen, as shown in the screenshot:

Engagement Center UI Configuration v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The Engagement Center UI Configuration mashup service offers two new features that provide the capability to manage language-depending text, extend field-level functionality in the Engagement Center, and automatically generate SAP GUI for HTML views.

Language-dependent text support

The first new feature gives you the opportunity to store and read the available language-dependent texts in the Engagement Center. For example, Engagement Center user interface (UI) texts. Call the endpoint /{tenant}/texts with the GET, POST, PUT, and DELETE HTTP-methods to manage these values. Use the endpoint /{tenant}/texts/{group} to group the texts and work with specific groups separately.

Object view extensions

The second new feature, with the endpoint /{tenant}/objectViewExtension, is the foundation for extending the service ticket view in the engagement context without any coding. Using this service, you can store configurations that contain information about additional fields.

In the engagement context, you can customize the service ticket view with additional UI elements, such as:

Input field
Label
Check box
Date picker
Time picker

SAP GUI for HTML integration

Updates to the SAP GUI for HTML integration, with the endpoint /{tenant}/sapguihtml, include new attributes in the service’s data model. The configuration table now has three new flags to configure the behavior of the SAP GUI for HTML, as well as views and menu items for the engagement context (Active, Action Area Link, and Autoclose). Additionally, a Text ID field is available to reference the language-dependent text objects.

New attribute for business document types

The existing business document type feature with the endpoint /{tenant}/businessdocumenttype is enhanced with a new attribute for the action area view. This attribute references to the action area views in the engagement context. Using this attribute, you can configure the automatic generation of action area views for SAP GUI for HTML. For additional information about SAP GUI for HTML configuration, see the Getting Started guide in your Engagement Center Settings.

Scopes prevent unauthorized access to the Engagement Center UI Configuration mashup service. The accepted scopes are:

hybris.cecenteruiconfig_view (for the GET-method)
hybris.cecenteruiconfig_manage (for other HTTP-methods)

Service Ticket Mashup v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The latest release of the Service Ticket Mashup service includes a new automatic ticket number generation feature, and an update to support deleted customer accounts in the Customer Engagement Center.

Generate service ticket number

The Service Ticket service now supports the automatic generation of ticket numbers. When you create or change a service ticket, and you do not specify a ticket number, the service automatically generates a unique ticket number.

Service ticket updates for customer deletion

The Service Ticket Mashup service now supports to update service tickets when the customer profile has been deleted.

Service Ticket v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The Service Ticket service now supports the automatic generation of ticket numbers. If you do not specify a ticket number when you create or change a service ticket, the service automatically generates a unique ticket number.

SAP Jam Communities v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The latest release of the SAP Jam Communities service includes enhancements that improve security for generating access tokens, and allow you to search the community for blog posts.

Improved security mechanism for generating tokens

The SAP Jam Communities service now supports a new method for generating access tokens. The new mechanism periodically refreshes an access token, before the previous token expires. You must apply for a new token every two hours to retrieve data from SAP Jam Communities.

To apply for a new token, configure these fields:

applicationID: ID of the application created in SAP Jam Communities
applicationSecret: Secret of the application created in SAP Jam Communities
userName: User name of the admin user for signing in to SAP Jam Communities
password: User password of the admin user for signing in to SAP Jam Communities

The permanent token generated before this release is no longer valid after December 31, 2016.

Blog searching enabled

New in this release is the endpoint /{tenant}/search. Use this endpoint to search for blogs from SAP Jam Communities by keyword. The service returns blogs sorted by matching degree, or relevance to the specified keywords, and the post time of each blog. The search results contain only the original blogs, without returning blog replies.

Product Support v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The Product Support service now supports localization settings for English and German users. Earlier, only English was supported. In addition, there was an issue with pagination on the store section. This issue has been resolved with server side pagination.

Interaction Recording v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Improve efficiency of your customer interactions with chat transcripts

Use the Interaction Recording service to store transcripts of chat interactions between customers and agents. By making these interaction recordings available to your agents, you improve the efficiency of your customer interactions. Every agent can access an overview of the interactions that occurred with a particular customer, whenever necessary.

Interaction Log v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The Interaction Log service now supports mixins in the interaction log. Specify the schema of a mixin in the metadata attribute. The mixin feature lets you define a set of reusable properties for use in different interaction logs.

For more information about mixins, see the Operate on Mixins documentation.

ERP SD Sales Order Proxy v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Help values retrieval supported for more fields

The ERP SD Sales Order Proxy service now supports the retrieval of help values for more fields, including payment card type, shipping conditions, sales unit, plant, item category, reject reason, schedule line category, incoterms, and delivery priority.

Retrieve help values for multiple fields

You can now retrieve help values for multiple fields by calling the API only once.

For example, see the API documentation for Retrieval help values for multiple fields.

Remove unnecessary query parameters

The unnecessary query parameters are removed, including:

qSalesOrganization, pageSize and pageNumber for the GET method at the endpoint /{tenant}/erpsalesorder/{salesorderId}
pageSize and pageNumber for the GET method at the endpoint /{tenant}/erpsalesorder/simulate

ERP SD Configuration v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Validation for the default configuration entry for SAP ERP connections

The ERP SD Configuration service now supports validation for a default configuration entry for SAP ERP connections. When you create or update a configuration for SAP ERP connections, the service validates the configuration only if one of them is marked as default. If not, an error returns.

Retrieve the default schema file name list

You can now use the ERP SD Configuration service to retrieve the name list of the mixin schema files which are delivered by SAP.

For more information about the mixin concept, refer to the topic Mixins.

Engagement Center Customer v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

You can now use the Engagement Center Customer service to delete customer profiles and associated accounts. This new feature is based on the same API endpoint of the Customer service. For more information about customer deletion, see Delete customer profile functionality.

Engagement Center Search v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Use the new query parameter, unpublishIncluded, to search for unpublished products, in addition to published products, in calls to the endpoint /{tenant}/product/advancedSearch. The default value for this parameter is false.

For more information, see the Engagement Center Search service documentation.

CECenter Mashup v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

The CECenter Mashup service now supports localization settings for English and German users. Earlier, only English was supported.

Engagement Center Indexing v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Several enhancements to the Engagement Center Indexing service support new indexing capabilities, the removal of data pertaining to deleted customer accounts, as well as upgrades to support version 2 of the Product service.

Price change indexing

The Engagement Center Indexing service now supports price indexing for products. When a product price changes, you can index the product with the new price.

Deleted customer data removal

After you delete a customer, the Engagement Center Indexing service removes related customer data and customer data contained in service tickets from the indexed data.

Customer login email change

The Engagement Center Indexing service now supports to index a customer’s new contact email if the customer changes their login email and synchronizes it with their contact email.

Order status indexing

The Engagement Center Indexing service now supports to index an order if the customer changes the status field of the order.

Support for renamed sku field in the Product service v2

The Engagement Center Indexing service now supports the upgrade of the Product Details service from version 1 to version 2. In Product Details service v2, the former sku field is now named code. Consider both the code and sku fields when you search by SKU.

SelfService Configuration v1

Fri Nov 25 2016 00:00:00 GMT+0000 (UTC)

Features

The Configuration service can be used to retrieve and load default settings needed for CECenter Self Service.

It enables you to configure and check default settings for:

Product Registration specific Settings.
Product Registration Email default Template.
CECenter Settings for self service.
Interaction Log reason settings for self service.
Load Required scopes for Agent Home.

The Configuration service lists out all of the configuration settings needed for the service and if all of the listed settings are appropriately configured. In addition, if any of the settings aren’t correctly configured, it visually highlights those settings, upon which the admin user can load all of the configuration with the single click of a button from builder ui.

Service SDK 4.12.0

Thu Nov 24 2016 00:00:00 GMT+0000 (UTC)

The YaaS Service SDK supports you in developing your own YaaS services. This release helps you achieve more in less time.

Added archetype without the `Wishlist` sample

Currently, the SDK includes a second archetype with the ID service-sdk-jersey-spring-base-archetype. It is similar to the existing one with the ID service-sdk-jersey-spring-archetype but does not include the Wishlist API sample. This makes it easier to start writing your own API without the need to clean up first.

Maven dependencies updated

Maven dependencies are updated, including the Jersey library version 2.24 and Spring dependencies version 4.3.4.RELEASE. Please check your Maven dependency tree and update the versions to eliminate the possible version conflicts.

hybris techne v1.5.1

Tue Nov 22 2016 00:00:00 GMT+0000 (UTC)

New Pattern

New way to display cards in groups. With the new modifier you can esily group cards into groups, with a more compact design.

Minor updates

Resolved an issue with the mobile behavior of the tabs.
Modified the style of the tabs on the :hover and :active states.
Fixed the misaligned icon on the Add Button for Android.
Changed the Starter Pages to reflect the standard way to use a margin on a full page.
Visual changes were made to the Tables pattern.

Avalara Tax v1

Thu Nov 17 2016 00:00:00 GMT+0000 (UTC)

VAT support

With the launch of globalization, specified updates ensure that all services are usable in the European market. The Avalara Tax service now supports the value-added tax (VAT), which is the tax included in the product's sale price.

To use Avalara Tax VAT, configure the following keys in the Site service for your European site:

businessIdentificationNo - Your Avalara Unified Business Identifier (UBI). The UBI is a tax registration number you receive when you file for a business license.
taxIncluded - The default value for this key is false. Set the key value to true for VAT.
account - Your Avalara account ID
license - Your Avalara license key
apiVersion - 1.0
url - https://development.avalara.net

For more information about the UBI, see the File business license applications section of the Avalara page.

For information on how to configure the tax provider for your site, see the Site service documentation.

To set up Avalara, see the Avalara Tax Calculation tutorial.

Customer v1

Wed Nov 16 2016 00:00:00 GMT+0000 (UTC)

When a user creates a customer profile using the YaaS identity provider through the /login/yaas endpoint, the system automatically stores the YaaS account email address in the contactEmail field of the created customer profile.

Dev Portal

Wed Nov 16 2016 00:00:00 GMT+0000 (UTC)

New improved Release Notes filtering

The view of the Release Notes page is improved. Previously, the navigation on the left side of the Dev Portal included filters to quickly find certain release note by API or Tool name.

Due to the rapid growth of services, the release notes landing page filters are enhanced to scale along with the increased number of services and to support an improved user experience.

The improved landing page filters allow you to:

Select the grid or list view. You can choose the view that works for you.
Sort the list of release notes by date.
Filter by keyword. Any filter you specify is applied to both the service name and its package.
Expand for more filters. For now, it includes five filters:
- Types
- Tools
- Markets
- Packages
- Services

The new filters:

See the improvements for yourself at Release Notes. If you think the new navigation is missing something, has issues, is not what you expect, or you have ideas for improvements, click Feedback and share your thoughts.

API Docs automatically filter based on your geographic location

In the newest version of the Dev Portal, the documentation for APIs filter automatically based on the services available in your geographic location.

When you are logged it to the Builder, the API Docs are filtered according to your region. For example, if you are in the U.S., the API Docs display services that are available in the United Statesregion.

You can check other regions, by changing the filter, as shown in the following image:

What happens when you are not logged in to the Builder or when there is no market available in your location?

If you are not logged in to the Builder, or if there is no market available in your region, the filter is set to Beta and only displays the BETA services.

Checkout v1

Tue Nov 15 2016 00:00:00 GMT+0000 (UTC)

The Checkout service now supports a new attribute on a checkout request to pass along the shopper’s selected payment method. This extra information enables:

Processing various payment methods such as credit card, debit card, and cash on delivery
Supporting fees on the selected payment methods

In addition, the service now passes all item fee and payment method fee information to the Order service.

Payment method processing

Until recently, the Checkout service supported only credit card and debit card payment authorization and capture. Passing the shopper's selected payment method now allows the Checkout service to process different payment methods. Currently, there are four defined payment methods:

credit card
debit card
invoice
cash on delivery (COD)

The service processes credit cards and debit cards with a transaction to the configured payment service. Currently, invoices and CODs are processed as null operations and the Checkout service simply assumes downstream processing. This allows you to continue using the Checkout service for validations, coupon redemptions, and order creation, while customizing your own payment capture process.

Payment method fee support

The Checkout service now supports an external fees service when adding charges and/or fees to the cart calculation for a selected payment method. You can use a fee service to add additional charges to the order as order surcharges. The payment method YRN is set to the format: urn:yaas:hybris:payments:payment-method:{tenant};{method}, where method is the payment method received in the checkout request. The Checkout service sends the YRN to the Cart Calculation service and the Cart Calculation service uses the YRN to query the fee service for payment method fees. See the Cart Calculation release notes for additional information.

Fee information passed to the Order service

In addition, the Checkout service now passes all of the item fee and the payment method fee information to the Order service. The service passes the information using a checkout mixin as defined in the mixin schema: https://api.xx.yaas.io/hybris/checkout/v1/meta-data/schemas/fees.json

In the Order service, use a simple GET request, using the order ID, to see exactly which fees were added to an order.

Coupon v1

Thu Nov 10 2016 00:00:00 GMT+0000 (UTC)

Bugs

Multi-tenant authentication tokens are now used when communicating to the Document Service to allow correct access to client's data.

Service SDK 4.11.3

Wed Nov 09 2016 00:00:00 GMT+0000 (UTC)

Service Generator `skip` flag

The Service Generation plug-in now provides a service-generator.skip flag that you can use to disable the generation of service classes. Even if you skip the generation, the plug-in still adds the generated sources in the target folder to the project sources. The effect is that as long as you don't build your project using the clean command, the plug-in does not remove the generated classes from the target folder, even when you use the skip flag.

Masking of password fields in the API console

Fields named password and client_secret are now masked within the API console, without updates to the RAML.

Earth Observation Analysis v1

Tue Nov 08 2016 00:00:00 GMT+0000 (UTC)

New Earth Observation Analysis service

The new Earth Observation Analysis service is available on the YaaS Market. It allows you to search for and analyze historical and near real-time satellite imagery. For example, you can get information about the density of vegetation on our planet by extracting the Normalized Difference Vegetation Index (NDVI) from images provided by the Sentinel-2 satellite. You can find more information about this new service in the Dev Portal API Documentation.

Features

Get metadata about satellite images within a specific region and time using simple REST calls, and download satellite images as classic RGB images or get higher-level information such as a vegetation index.

Cart Calculation v1

Tue Nov 08 2016 00:00:00 GMT+0000 (UTC)

Malformed fee handling

Following the support of fees in the Cart Calculation service, it can now handle malformed fees. A malformed fee is a fee whose data does not correctly or uniquely identify the identity of the fee. If a fee falls into one of the malformed scenarios defined by the Cart Calculation service, the fee value defaults to zero (0). This ensure the fee has no impact on the cart calculation totals and it serves as a visual cue that something may be wrong with the fee.

The Cart Calculation service only supports the following fee type values:

ABSOLUTE
ABSOLUTE_MULTIPLY_ITEMQUANTITY
PERCENT

For more information on cart calculation with fees, see the Cart Calculation Process page and the Calculate a Cart tutorial.

hybris techne v1.5.0

Fri Nov 04 2016 00:00:00 GMT+0000 (UTC)

New Patterns

New Product Thumbnail pattern added. Can be used to show a list of products in a grid.
Revisited Tree pattern. Now with more standard expand/collapse icons and behavior; a description of how the interactivity should work.

New Starter Pages

New Grid Started pages added. Speeds the development of pages used to display a grid of products using the Product Thumbnail pattern.
New Tree Starter Page added to show the interactive behaviour in action.

Minor updates

Fixed an issue when the Card component includes a popup submenu
Improved Icons page with grid layout for easy scanability. Added suggested colors for each icon based on it's recommended usage
Improvements on Dialogues/Modals, Toolbar documentation, Help messages icons and widgets.

Cart v1

Thu Nov 03 2016 00:00:00 GMT+0000 (UTC)

Retrieve cart now supports fees

A fee is an additional charge that can be applied to any item in the Storefront. For example, you can add a deposit fee to beer bottles. You can add multiple fees to a single item. When you retrieve a cart by using the cart ID, you retrieve details about the items in the cart as well as the cart calculation. The fees are a part of this calculation. Now, when you complete a GET request (/carts/{cartId}) and fees are included, you receive the following additional details:

The total, subtotal, and tax total for each fee item in the cart.
The total, subtotal, and tax total of the sum of the item fees for an item.
The total, subtotal, and tax total of the sum of each item fee for all of the items.
The fee aggregate for each fee YRN in the cart.

For more information about item fees, see the Retrieve Item Details From the Cart and Retrieve Cart Details by ID tutorials.

Storefront Template v1.0.6

Wed Oct 26 2016 00:00:00 GMT+0000 (UTC)

Display of product variants in the cart details and checkout confirmation pages

Product variants lets the customer see all the different variations of the products in the storefront. For example, you can see the different sizes and colors that a t-shirt comes in. The storefront's cart details and checkout confirmation page now support product variants.

After you add an item to the cart and click the cart icon, you can see the item in the cart with the product variant information, if it is applicable. In the example below, a black t-shirt in size small is in the cart.

When you click Checkout, the checkout confirmation page also shows the same product information.

Price ranges for products with variants

In this release, new pricing functionality in support of variants allows you to set the price as one value or, if a product has variants, as a price range.

Depending on whether a product has variants and multiple prices, the service:

displays a single price for products without variants, and for products with variants that cost the same price
displays the price range for products with variants that have at least two different prices in the Storefront List page

InStock presentation for product with variants

To further support product variants, updates to the service's behavior in response to the inStock value include:

The inStock line is hidden in the Storefront List page for products with variants.
The information on the Storefront Details page changes depending on an item's availability:
- Out of stock: Variants are out of stock
- Add to cart: Variants are in stock

Customer account deletion

A customer with a storefront account can now delete the account if necessary. This feature requires the customer to sign into the storefront, go to the My Account page, and click Delete Account, as shown:

The system asks the customer to confirm the action:

Upon confirming, the system sends an email with a confirmation link to the customer's sign-in email address or, for accounts created with a social sign-in, to the customer's contact email address. You can set the confirmation URL in the configuration key customer.deletion.redirecturl, using the Configuration service. The token included in the email is valid for 24 hours.

After the customer clicks the link in the email, the system deletes the account.

Region-specific storefronts

To use the storefront in different regions, provide the --region parameter in the build task, which runs the store in the specified region. This means that the service URL the storefront calls points to that specific region, for example, https://api.eu.yaas.io. If you omit this parameter, the service builds the storefront URL in the US region. For now, the other available region is the EU. Here is an example of the region parameter in use:

$ npm run-script singleProd -- --pid=abc --cid=123 --ruri=http://example.com --region=eu

HTTPS usage in the storefront

It is recommended that you use domains that are encrypted into a Secure Socket Layer (SSL) HTTPS session. You can enforce HTTPS instead of HTTP in the storefront by providing an additional parameter, --https, in the build task. Here is an example:

$ npm run-script singleProd -- --pid=abc --cid=123 --ruri=http://example.com --https

The endpoint used before by Storefront to get the anonymous access token is now deprecated: https://api.yaas.io/hybris/account/v1/auth/anonymous/login. We migrated it to the new https://api.yaas.io/hybris/customerlogin/v1/auth/anonymous/login.

We recommend this migration for the already implemented customer storefronts. The new call should use the following:

Method: POST

URL: https://api.yaas.io/hybris/customerlogin/v1/auth/anonymous/login

Body: { "clientId": <your_storefront_app_client_id>, "tenant": <your_tenant> }

Community

Mon Oct 24 2016 00:00:00 GMT+0000 (UTC)

Add a YouTube video to your Community Showcase

Showcase owners can now add a YouTube video promoting their showcases.

As a showcase owner, you just have to add the YouTube video ID to your showcase. You will also see a preview.

After you save your update, the video is available for the community.

Builder

Mon Oct 24 2016 00:00:00 GMT+0000 (UTC)

This release includes two new features:

Multiple source URL entries for services enabling deployment to EU and US data centers. YaaS generates the corresponding proxy URL per location.

Multiple module location URL entries for Builder modules enabling deployment to EU and US data centers.

Algolia Search v1

Thu Oct 20 2016 00:00:00 GMT+0000 (UTC)

New features and functionality

With the new indexing properties in the Algolia Search service, you can now enjoy the flexibility of indexing all of your products: published, unpublished, or both. Read on to learn about the latest enhancements to the Algolia Search service.

Enable indexing of all products or products by publication status

A new feature in the Algolia Search service allows you to index published products, unpublished products, or all of your products, both published and unpublished.

Use the new endpoint /{tenant}/project/configuration/indexing to specify an indexing method in the Algolia Search service. Now you can manage indexing with help of these properties:

activePublishedProductIndexing: If set to true, this property enables indexing of published products. If set to false, the property disables indexing of published products.
activeNonPublishedProductIndexing: If set to true, this property enables indexing of non-published products. If set to false, the property disables indexing of non-published products.

The active property, which enables indexing of published products only, is still available but is deprecated and scheduled to be removed entirely in an upcoming version of the Algolia Search service.

Enable unpublished product indexation only if your Product Content package subscription is up-to-date. If your Product Content package subscription is older than 20 October 2016, renew your subscription or the indexation feature will not work as expected.

Search both for published and unpublished products with new search credentials

The updated search feature changes the way the searchKey works and introduces an additional backofficeSearchKey.

Previously, the searchKey property searched for all indexed products, but only published products were indexed. Because you can now index both published and unpublished products, the new searchKey property searches for published products only, and ignores unpublished products. Make sure you remove any old keys and generate a new searchKey to use this feature properly.
To search for all products, both published and unpublished, use the backofficeSearchKey.

If you previously used Algolia indexing, you might still have the old key that allowed you to search for all indexed products. Continuing to use the old key could lead to some issues, because there was no distinction between indexing of published and unpublished products in the former version. To avoid the unnecessary risk of getting the wrong results, it is strongly recommended that you delete the old searchKey in your Algolia Dashbord and create a new searchKey that enables you to search for published products only.

Customer v1

Tue Oct 18 2016 00:00:00 GMT+0000 (UTC)

Features

Delete customer profiles and accounts as a merchant

The Customer service now allows merchants to delete customer profiles and associated accounts. Here is the process for deleting a customer account:

To request the deletion of a customer profile, the merchant sends a DELETE request to the /{tenant}/customers/{customerNumber} endpoint.
If the request is successful, the Customer service responds with a 202 Accepted message.
The service deletes the customer data asynchronously, in the background, and therefore no further action or communication is required. As soon as the service accepts the delete request, it fires the hybris.customer.customer-deleted event. The payload of this event contains the customerNumber and, if available, the email of the customer that is being deleted. The payload also contains the hybris.user that requested the deletion.

Resolved Issues

Customers can now confirm deletion requests without having to be logged in.

Dev Portal

Mon Oct 17 2016 00:00:00 GMT+0000 (UTC)

The view of the API Docs landing page is improved. Previously, the navigation on the left side of the Dev Portal included filters to quickly find documentation by API name.

Due to the rapid growth of services, the landing page filters are enhanced to scale along with the increased number of services and to support an improved user experience.

The improved landing page filters allow you to:

Select the grid or list view. You can choose the view that works for you.
Sort the list of APIs.
Filter by keyword. Any filter you specify is applied to both the service name and its package.
Expand for more filters. For now, the only filter is the package filter, which allows you to filter services for a specific package. The filter also informs you how many services the package contains.

The new filters:

See the improvements for yourself at API Docs. If you think the new navigation is missing something, has issues, is not what you expect, or you have ideas for improvements, click Feedback and share your thoughts.

Document v1

Fri Oct 14 2016 00:00:00 GMT+0000 (UTC)

From now on you can use rawwrite query parameter when performing a POST request on the /{tenant}/{client}/data/{type} endpoint.

Use the new parameter to insert the body of your request into the database in exactly the same form as you send it in your request.

When using this new query parameter, remember that the body of the request must contain at least these basic metadata attributes:

id
createdAt
modifiedAt
version

Please, keep in mind that in case, the document with the same id attribute already exists, the document is fully replaced. Because the operation performed on the database replaces the document in the database, do not set the patch query parameter to true when the rawwrite query parameter is set to true.

hybris techne v1.4.1

Thu Oct 06 2016 00:00:00 GMT+0000 (UTC)

Techne v1.4.1

This is a minor patch release with some small updates to Starter Pages and minor bug fixes.

Updates

Starter Pages - Updated Table and Cards pages to include pagination component at the bottom of the page
Localization Editor - Updated to show more specific error messages

Order v1

Wed Oct 05 2016 00:00:00 GMT+0000 (UTC)

Store the original price for an order item

A new optional field, originalAmount, is now available in order entries. The new field allows merchants to store the original price of an item. You can store the originalAmount separately from the unitPrice, which is the currently effective price of an item.

Add the original price to email templates

To display the originalAmount in emails to your customers, you can edit the order confirmation email templates. To do so, replace this section of code:

<span style="padding-bottom: 10px;">#e(${d.order.currency}) #format_amount(${entry.unitPrice})<br/>

With this code:

#if($!{entry.originalAmount} != $!{entry.unitPrice})
    <span style="padding-bottom: 10px; font-weight:bold; text-decoration: line-through">
         #e(${d.order.currency}) #format_amount(${entry.originalAmount})</span>
    <span style="padding-bottom: 10px; font-weight:bold; color:#ff1616">
         #e(${d.order.currency}) #format_amount(${entry.unitPrice})
    </span><br/>
#else
    <span style="padding-bottom: 10px;">
         #e(${d.order.currency}) #format_amount(${entry.unitPrice})
    </span><br/>
#end

hybris techne v1.4.0

Mon Oct 03 2016 00:00:00 GMT+0000 (UTC)

Techne v1.4.0

In this release, we have some brand new patterns and some minor updates to components.

New Patterns

Toolbar Pattern - Includes functionality for handling Multiple Attribute/Facet filtering, Sorting, Pagination and View Switcher between Cards and Table layout
Localization Editor - When content needs to allow for translation into more than one locale
Expandable Button - Allows you to design an experience that supports multiple actions from a dropdown

Components Updates

Alerts, Errors & Notifications – added example of "Notification” alert
Status Indicators - added example of "Warning” status
Help and Validation - added exmple of field-level error for Form Validation

Starter Pages

Updated Tables and Cards Starter pages to include the Toolbar Pattern

CECenter Mashup v1

Tue Sep 27 2016 00:00:00 GMT+0000 (UTC)

This service allows customers to create service tickets to report issues to a customer service agent for resolution. You can configure service ticket types for the different services you provide, such as requests for repairs, requests for servicing, and general inquiries.

When you create a service ticket, you can specify the information to collect in the tickets you customers submit. For example:

A short description of the customer's issue or request
The customer for whom the service ticket was opened
The product that the request or issue relates to

Manage the service ticket resolution process with features such as:

Built-in status management
A transcript concept that allows customer service agents to enter additional information about the processing status
Automatic calculation of processing times

For more information, see the CECenter Mashup service documentation.

Product Support v1

Tue Sep 27 2016 00:00:00 GMT+0000 (UTC)

Use the new Product Support service to allow consumers to register a product. Product registration is essential for many follow-up processes such as warranties and recalls. This service does not handle warranties or recalls.

The service allows consumers to:

Register a product
View registered products

You can also configure the service to:

Send an email upon product registration
Maintain products that consumers can register
Create stores to indicate the retail location where products are purchased
Update store details

When you configure the service, you can:

Maintain email templates for registration notifications
Create new stores
Flag products that are available for registration from a catalog

Media v2

Fri Sep 23 2016 00:00:00 GMT+0000 (UTC)

YaaS users,

In January of this year, the Media service version 2 was released. You can read more about that release here. In July, the addition of automatic migration functionality ensured that all data belonging to active users of the service remained safe and was migrated to the new service. Additionally, Deprecated storage locations were disabled at the time. By now, all users of the Media service should be familiar with version 2, which is, of course, much cooler than the previous version, Media service v1. Because the old version is no longer required, the time has come to announce that the shutdown date for Media service v1 is scheduled for Sunday, December 25, 2016. Please plan to use Media service v2 only after that date.

Product Details v2

Mon Sep 19 2016 00:00:00 GMT+0000 (UTC)

The Product Details service v2 is available and is compatible with the latest Product service release. As of this release, use Product service v2, instead of Product service v1, within the Product Details service.

Changes in this release

This release includes updates to make the Product Details service compatible with the Product service v2 release.

External media support removed

For security reasons, external media support is removed. Any external media you create is no longer visible in the Product Details service v2.

The sku field is renamed to code

The field, sku, is now named code to match the field name in Product service v2.

Default language replaced with localization value map

In the previous version of the Product Details service, if you did not provide Accept-Language or hybris-languages headers, the service assumed that you wanted to retrieve content in English. To provide more insight into how your data gets treated, the English-language assumption is removed. Now, when you fetch data without providing an Accept-Language or hybris-languages header, you receive a full map of localization values, matching the functionality in the Product service v2.

Default currency replaced with prices in all provided currencies

In the previous version of the Product Details service, if you did not provide the hybris-currency header, the service assumed that you were interested only in the USD currency. To provide more control over your data, the USD currency assumption is removed. Now, when you provide data without a hybris-currency header, you receive prices in all provided currencies.

Migration

You might need to reorder your media in the Product service v1 before you begin using Product service v2.

Media reorder migration (possible action required)

If you currently use the Product service v1 to manage your products, you might need to use the Migration service to reorder your media to the format supported by this release of the Product Details service. The Migration service takes into consideration the media's position attribute and the main flag. The main flag has a higher priority than any position value. If you ordered your media using the Product service v1, make sure you trigger migration after you finish using it, and before you start using Product Details service v2. For more information about the media reorder migration, see the Product service v2 Media Migration tutorial.

Builder

Thu Sep 15 2016 00:00:00 GMT+0000 (UTC)

This release includes two new features:

Notification Center
Chinese Localization

Notification Center

From this release on, the Notification Center notifies you about happenings in the Builder. After you sign in to the Builder, you'll see a small bell icon on the top right. Click the bell to open the Notification Center and view all notifications related to your access rights, as well as the projects and organizations you belong to.

For example, you can see a notification for an outdated subscription in the image shown.

Within the notification message, you can click the blue headline to navigate to an action page. In the example image, the link redirects to a subscription update page. After you perform an action to resolve a notification the message disappears from the notification center.

Chinese Localization

For all of our colleagues in China, content in the Builder can now appear in Chinese.

To change your user interface (UI) language to Chinese, go to My Account > My Profile and specify your preferred language in Builder Settings.

There are more changes and improvements on the way, so check back soon for the latest updates!

Price v1

Wed Sep 14 2016 00:00:00 GMT+0000 (UTC)

Scope removal for PubSub events

From now on, clients do not need to declare scopes to read events. As of a recent update to the PubSub service, when a tenant subscribes to any service, the subscribed service has access to all of the tenant's events on all the topics. Due to this update, you no longer need the hybris.pubsub.topic=hybris.price.price-change scope to read the price-change event. This update is backward compatible, so all existing clients are not affected by this change.

Resolved Issues

The issue in which the incorrect tenant header was passed in a price-change event is fixed. Previously, reading events was limited to the Hybris CaaS tenants.

YaaS Events

Mon Sep 12 2016 00:00:00 GMT+0000 (UTC)

Check out YaaS Events on YaaS.io to find out about YaaS-specific events and activities, events featuring YaaS, and where to meet the YaaS experts. You can browse a list of upcoming events, as well as learn more about past events.

View, search for, and filter events

On the YaaS Events page, you can view a full list of upcoming and past events, search for events by keyword, or filter the list of events by event type, country, or city.

View events

To view events at YaaS.io, click Community > Events. You can also go directly to https://events.yaas.io.

When you arrive at YaaS Events, check out a full list of upcoming and past events. Click on any event tile to view the event details.

In an event’s details view, you can view information such as date, time, and location. Events are listed in the time zone of the event location. If you do not see a time zone, then you are located in the same time zone as the event.

Use the scroll arrows on the left and right side of the image strip to view all images for the event. Click on any image to enlarge it.

The event URLs shown contain the event title and event date. For example, https://events.yaas.io/2016/10/07/SAP+CodeJam+Munich shows that an event called SAP CodeJam Munich that takes place on October 10, 2016.

Click Register Now to navigate to a registration page or click More Details to navigate to the event’s official landing page.

Search for events

You can use the type-ahead search bar to find events easily on the YaaS Events page. Enter at least the first three letters of your search term in the search. Press Enter to filter the list of relevant events. You can then select an event from the results list to view the event’s details.

To clear the search results and return to the events overview, click the x on the right side of the search bar.

Filter events

You can also use the filters on the top of the page to narrow the events shown by event type, country, or city.

Select a filter item to display the relevant events. Click Clear All to remove the filters and return to the full list of events.

Customer v1

Thu Sep 08 2016 00:00:00 GMT+0000 (UTC)

The latest release of the Customer service includes several updates, including the ability for customers to delete their profiles, a new event that identifies updates to customer sign-in emails, and an improved error message for a missing redirect URI.

A new event, customer-login-email-changed, occurs when a customer updates the email address used to sign into YaaS. Here is an a example of the event's payload when a hypothetical customer changes a sign-in email from "myoldemail@yaastest.com" to "newemail@yaastest.com".

{
    "customerNumber" : "C0123456789",
    "oldEmail" : "myoldemail@yaastest.com",
    "newEmail" : "newemail@yaastest.com"
}

More informative error message when the redirect URI is not set

The Customer service now returns the error code 400, along with a proper error message, when the redirect URI is not set. Previously, the service sent a more ambiguous 500 internal server error. More informative error messages can help you determine how to resolve issues.

Customers can delete profiles and accounts

The Customer service now allows customers to delete their profiles and associated accounts. A customer must be signed in to delete the account from the Customer service. Here is the process for deleting a customer account.

When the customer requests to delete the profile, send a DELETE request to the {tenant}/me endpoint.
If the request is successful, the service sends an email with a confirmation link to the customer's sign-in or, for accounts created with a social sign-in, the customer's contact email address. You can configure the confirmation URL, in the configuration key customer.deletion.redirecturl, using the Configuration service.
When the customer clicks the link to confirm, send a DELETE request with a token as a query parameter to the {tenant}/me?token={token} endpoint.
The Customer service responds with a 202 Accepted message.
The service deletes the customer's data asynchronously, in the background. As soon as the service accepts the delete request, the service fires the hybris.customer.customer-deleted event. This event contains the customerNumber and email address of the deleted customer in its payload.

Cart v1

Thu Sep 08 2016 00:00:00 GMT+0000 (UTC)

Excess calls to the Cart Calculation service eliminated when adding items to cart

Adding an item or a bulk of items to a cart triggers an add-to-cart request. In previous versions of the Cart service, each add-to-cart request also triggered a separate call to the Cart Calculation service, which caused Cart Calculation to time out. Now in most cases, add-to-cart requests no longer call the Cart Calculation service. This improvement reduces the load on the service.

Beginning with this release, add-to-cart requests only call the Cart Calculation service when a discount is applied to the cart, so that the Cart Calculation service can provide feedback to the storefront about the cart’s discount status.

Service SDK 4.11.1

Mon Sep 05 2016 00:00:00 GMT+0000 (UTC)

Resolved issues

The new patch version of the Service SDK solves former issues with file name and enum interpretation, as well as other fixes.

The RamlRewriterFilter now works with Spring Boot 1.4.0.
The system no longer interprets the target folder for generated files as an encoded URI, so you can now safely use the percent sign (%) inside your project's folder name.
You can use relative paths to external files that hold a JSON schema when using code generation.
The system now correctly interprets locally-referenced enums when generating a service code from the RAML file.

RAML Patterns 1.3.0

Fri Sep 02 2016 00:00:00 GMT+0000 (UTC)

A new version (v3) of the resource-type-element pattern is released with an improvement. The PUT and DELETE methods in the resource-type-element pattern are not required anymore. The methods for this pattern are now optional.

Resolved Issues

An issue with the trait-yaas-aware pattern was resolved. It no longer refers to the old format of the hybris-client header.

Checkout v1

Fri Sep 02 2016 00:00:00 GMT+0000 (UTC)

Support of item YRNs

Because the Cart service supports item YRNs (itemYrn), the Checkout service must do the same. Now, the system passes the product's item YRN from the Cart service to the Checkout service, and then to the Order service when you complete a checkout. This process ensures that the system supports products that have an item YRN throughout the entire shopping experience.

Language header support

The language header (accept-language) now works with not only the Order service, but the Product service as well. Include the header in requests to complete an order checkout. The header's value determines the language for the content that is retrieved from the Product service. If you do not include this header in your request, the system uses the default value, English.

Refer to the Checkout an Order tutorial for an example.

SKU attribute is now called code

To achieve consistency with the Product service, the SKU (sku) attribute is now called code (code).

Playbook v1

Wed Aug 31 2016 00:00:00 GMT+0000 (UTC)

This is the first official release of the Playbook service which is wrapped into the Customer Journey Manager package, now available on the YaaS Market.

Build and monitor customer journeys

The Playbook service enables you to perform the following tasks:

Design and build a customer journey.
Create a standard journey, or a KPI-driven journey.
Retrieve, update, and delete a Playbook.
Fetch all the Journeys.
Collaborate with SAP JAM users.

For more information on this service, see the Playbook service documentation.

Template v1

Wed Aug 31 2016 00:00:00 GMT+0000 (UTC)

This is the first official release of the Template service which is wrapped into the Customer Journey Manager package, now available on the YaaS Market.

Create and manage an activity template, or a stage template

Use a pre-defined template, or customize and design your own Activity or Stage, and save it as a new template. Also, import or export custom activity and stage templates from any SAP, or non-SAP system.

For more information on this service, see the Template service documentation.

Activity v1

Wed Aug 31 2016 00:00:00 GMT+0000 (UTC)

This is the first official release of the Activity service which is wrapped into the Customer Journey Manager package, now available on the YaaS Market.

Manage entities and activity metrics

The Activity service enables you to fetch business entities and Metrics from a Source system. For example, use this service to fetch pre-defined email campaigns from the SAP Hybris Marketing system, which you can then assign to an Activity.

For more information on this service, see the Activity service documentation.

Customer Journey Manager Configuration v1

Wed Aug 31 2016 00:00:00 GMT+0000 (UTC)

This is the first official release of the Customer Journey Manager Configuration service which is wrapped into the Customer Journey Manager package, now available on the YaaS Market.

Manage business and system configurations

The Customer Journey Manager Configuration service is a mashup service that is used to configure the Customer Journey Manager application. This service provides the URL to access the Customer Journey Manager application.

For more information on this service, see the Customer Journey Manager Configuration service documentation.

KPI v1

Wed Aug 31 2016 00:00:00 GMT+0000 (UTC)

This is the first official release of the Key Performance Indicator (KPI) service which is wrapped into the Customer Journey Manager package, now available on the YaaS Market.

Create and manage KPIs

KPIs (Key Performance Indicator) help you to monitor a journey. Use the KPI service to create a KPI-driven journey that enables you to achieve business goals.

For more information on this service, see the KPI service documentation.

Web Interaction Persistence Enricher v1

Mon Aug 29 2016 00:00:00 GMT+0000 (UTC)

Overview

This enricher captures the clickstream of a user after the consent is obtained, captures it, and ports it to the graph database.

Features

Persists end-user interaction
The enricher captures the following five interaction types:
- WEBSITE_VISIT: Visits to the Web site
- WEBSITE_SEARCH: Searches on the Web site
- WEBSITE_DOWNLOAD: Downloads from the Web site
- WEBSITE_VIEW: Views at the Web site; for example, viewing a video
- WEBSITE_REGISTRATION: Registrations at the Web site
Persists End User Navigation
This enricher tracks the navigation path of the user as the user moves from one point to another on the Web site.

Loyalty Member v1

Mon Aug 29 2016 00:00:00 GMT+0000 (UTC)

Features:

Activity Types CUSTOM and ACTIVITY are now introduced to support custom scenarios.
A new configuration "Maximum Points per day" is now added to restrict a user from earning points beyond a certain limit per day.
/activities and /memberRegistrations endpoints now support custom attributes, which are in turn passed to Rules service to support custom conditions.

Loyalty Offer v1

Mon Aug 29 2016 00:00:00 GMT+0000 (UTC)

Replicate offers from SAP Hybris Marketing and SAP Hybris Marketing Cloud

The Loyalty Offer service now supports the replication of offers from SAP Hybris Marketing and SAP Hybris Marketing Cloud into Loyalty. With this enhancement, the replication of offers is bidirectional. Two new fields support this feature. The field originId, contains the origin system ID of the offer. The field externalId, contains the external unique ID of the offer. These fields contain data only for the replicated offers, not for offers directly created in Loyalty.

Loyalty Configuration v1

Mon Aug 29 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Configuration service now stores initial load configuration status for the following services:

Member
Offer
Geofence
Content
Report Metadata

Service Ticket Mashup v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

The Service Ticket Mashup service now supports mixins in service tickets. Specify the schema of a mixin in the metadata attribute.

For more information about mixins,see Operate on Mixins.

Service Ticket v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

The Service Ticket service now supports mixins in the service ticket. Specify the schema of a mixin in the metadata attribute.

For more information about mixins,see Operate on Mixins.

ERP SD Customer Proxy v2

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

Get detailed customer information

You can now use the ERP SD Customer Proxy service to retrieve detailed customer information via the BAPI BAPI_CUSTOMER_GETDETAIL1.

Interaction Log v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

You can now use the Interaction Log service to calculate the communication duration of contact with customers, such as video chats, text chats, and phone calls. The new data fields, communicationStartedAt and communicationEndedAt, are now available in this service to support this new function.

Engagement Center UI Configuration v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

Now you can use a new service with the GET, POST, PUT, and DELETE methods to configure SAP GUI for HTML for the Engagement Center. The endpoint of this new service is /{tenant}/sapguihtml.

To integrate SAP GUI for HTML in the Engagement Center, you must maintain this data:

SAP GUI for HTML URLs
WebSocket URLs
View types (DISPLAY, SEARCH, CREATE, or EDIT)
Keys of the business document type for the view types

ERP SD Configuration v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

Switch flag for customer data replication

You can now use the ERP SD Configuration service to manage the customer data replication between the connected ERP system and the Engagement Center using the ERP SD Customer Proxy service.

New mixin schemas for IDoc

You can now use the ERP SD Configuration service to generate mixin schemas for IDoc types of both DEBMAS06 and ADRMAS03. The new mixin schemas can be used in customer data replication between the connected ERP system and the Engagement Center via SAP HANA Cloud Integration.

Engagement Center Customer v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

You can now create or update a customer profile without specifying an email address. The body still contains some basic customer data, but the contactEmail attribute is no longer required. The service saves the new customer without assigning an internal account. To create an internal account for such a customer, use the new endpoint /{tenant}/customers/{customerNumber}/accounts/internal.

Engagement Center Indexing v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

The Engagement Center Indexing service now supports a new field, formattedPhone, which removes all of the characters in the contactPhone parameter excluding numeric characters.

ERP SD Sales Order Proxy v1

Fri Aug 26 2016 00:00:00 GMT+0000 (UTC)

New edit function for ERP sales orders

The ERP SD Sales Order Proxy service now supports the editing of ERP Sales Orders. To use this function, you must implement the SAP Note 2339873. For more information, see the API documentation for the ERP SD Sales Order Proxy service.

Retrieving help values

The ERP SD Sales Order Proxy service now supports to retrieve the help values from the connected SAP ERP system. Currently only the fields of the payment terms, payment method, billing block, and delivery block are supported.

hybris techne v1.3.1

Mon Aug 22 2016 00:00:00 GMT+0000 (UTC)

Techne v1.3.1

We focused this release on cleaning up the Techne website and documentation so standards and practices are more clear for teams building on YaaS, with some minor updates to existing components and patterns.

Component & Pattern Updates

Updated and clarified the Action Bar (formerly Page Header with Save/Cancel actions) pattern expected behaviors to ensure consistency across Builder modules
Increased the size and changed the orientation (vertical to horizontal) of the contextual menu for visibility and usability purposes
Updated and clarified guidelines for the Modal/Dialog pattern

Website Updates

Updated the main site navigation to separate Components, Patterns and Starter Pages from each other
Separate Starter Pages section for easier access and reference (source code available via Github)
Redesigned all site pages for better readability and access to code snippets
Made Axure libraries and techne color swatches available on the Download & Getting Started page

Dev Portal

Thu Aug 18 2016 00:00:00 GMT+0000 (UTC)

Interactive tutorial is a functionality in the Dev Portal that enables creation and usage of tutorials in interactive way. Basically it means there are documents that you can edit and run the code that they have inside.

Previously, the content in the interactive tutorials was hidden, unless the Load Tutorial button was clicked. It looked like it is shown in the following screenshot:

We have received an improvement request from the community to be able to:

Search content of each tutorial with ctrl + f or cmd + f,
Read the content before loading the tutorial

Now interactive tutorials are displayed as static HTML. Scroll to the certain tutorial and click the Load {{Tutorial Name}} tutorial to run or edit the code. link, which appears now in the fixed box, to load the tutorial, as shown in the following screenshot:

Your feedback is very important and valuable for us, so thank you and keep it up.

Stripe Payment v1

Fri Aug 12 2016 00:00:00 GMT+0000 (UTC)

Additional Stripe account name

Now when you activate Stripe Connect, the Stripe Payment service updates the site's settings with the merchant's Stripe account name (businessName attribute). In the Builder, a new field appears on the Payment Details page of the site's payment settings. Since a Stripe account can only be connected to one site, being able to see which Stripe account has already been used is beneficial to the merchant.

If Stripe Connect is already activated, you must deactivate and reactivate Stripe Connect for the Stripe account name to appear in the Builder.

Cart v1

Fri Aug 12 2016 00:00:00 GMT+0000 (UTC)

Support of item YRNs to improve functionality with external product services

Further to the introduction of the YaaS Resource Name (YRN) support, the Cart service now supports item YRNs (itemYrn). An item YRN is the equivalent to the current product schema. Now when you add, remove, or update an item in the cart by using the item YRN instead of the product schema or product ID. The item YRNs were introduced because, eventually, the Cart service will cease to use the product schema. When you add an item to the cart, the product schema, which consists of various attributes (for example, ID, YRN, description, and SKU), is coupled with the product information you entered using the Product service in the Product Content package. By removing the product schema and only using a generic item YRN, it allows you to use your own product service with ease.

For more information about how item YRNs are used in the current API calls, see the tutorials in the Cart service.

Cart service decoupled from the other services

The design of the Cart service is refactored so that it is no longer depends on other services such as the Product service. This way, you can use it as a standalone service, which corresponds to the true definition of a microservice.

This refactoring introduces the following validation changes:

There is no longer any product validation when items are added to the cart during a merge cart or a change site request. This imples that when you change the site of a cart, or when you merge two carts together, these actions will be successful even if the items within the cart do not exist.
There is no longer any tax code validations or updates when you merge two carts or when you change the site of an existing cart.
Price validation is no longer executed when you merge two carts. Therefore, carts with different currencies can now be merged even if the price does not exist in the desired currency.

Dev Portal

Tue Aug 09 2016 00:00:00 GMT+0000 (UTC)

Summary

The search box and the Ask a question button on many landing pages are removed. The removal is because:

According to Google Analytics, these components were used by a very small percentage of users.
The search box duplicated a search feature present in the top navigation.
Thanks to your feedback, it became apparent that the exact search scope of the removed search boxes on each landing page was not clear.

Your feedback is very important and valuable for us, so thank you, and keep it up.

Customer v1

Thu Aug 04 2016 00:00:00 GMT+0000 (UTC)

Features

Added hybris.profile_consent_view, hybris.profile_consent_manage, hybris.serviceticket_view, hybris.serviceticket_manage and hybris.serviceticket_configuration_view scopes for a logged in customer.

Service SDK 4.11.0

Wed Aug 03 2016 00:00:00 GMT+0000 (UTC)

Spring Version Update

With this release, the Spring Framework version is updated to the 4.3.2.RELEASE. Update the version you use accordingly.

Service Generation Issues Resolved

To resolve a number of Service Generator issues without breaking existing code, a new feature flag called compatibilityModeEnabled is available and is enabled by default. You must explicitly disable the flag to make the fixes take effect. To do so, configure the plug-in as shown:

<execution>
    <id>service-generation</id>
    <goals>
        <goal>generate-service</goal>
    </goals>
    <configuration>
        ...
        <compatibilityModeEnabled>false</compatibilityModeEnabled>
    </configuration>
</execution>

The details of the fixes included in the feature flag are described as follows.

Enum Generation

With this release, a new feature generates enumeration classes as inner classes with the Service Generator. This improves readability and helps to avoid mapping conflicts when the same attribute name is used within multiple DTOs.

DTOs Definition Generation

DTOs that are generated for nested schemas are named after the referenced schema name instead of the first occurring reference name. That enables better naming when the same schema is referenced in multiple places.

Validation of lists

Now the @Valid annotation is generated in Jersey resources in front of DTOs that are mapped form JSON arrays to Java Lists, as long as the List type is a JSON object that itself requires validation itself.

Builder

Wed Aug 03 2016 00:00:00 GMT+0000 (UTC)

This release includes two new features:

Use the project's scopes when defining user roles
Select an organization contact person from organization members

Use the project's scopes when defining user roles

With this release, you can choose from your project's scopes when defining a new user role in your project. The scopes that are available for selection come from the scopes you defined in your services.

The scopes are grouped by the packages you subscribed to and alphabetically ordered. Your projects scopes appear in the section My project scopes.

Select an organization contact person from organization members

The contact person for an organization must now be a member of that organization. Previously, you could enter any name and email address. Now, you must select the email address from the Email Address drop-down list, which includes all available organization members

The list dynamically updates as you type, allowing you to find users based on a few characters.

There are more changes and improvements on the way, so check back soon for the latest updates!

PubSub v1

Fri Jul 29 2016 00:00:00 GMT+0000 (UTC)

Read events without declaring scopes

The reading of events by consumers is made simpler. If a tenant subscribes to a service, that service has access to all of the events on the tenant's topics. The consumer no longer need to declare scopes to read events.

For more details, see the PubSub RAML contract, specifically the JSON schema for the /topics/read resource in the PubSub API console.

This change in the PubSub contract is backward-compatible, so all existing clients are not affected by this new functionality. From now on, clients do not need to configure scopes to read events.

Storefront Template v1.0.5

Wed Jul 27 2016 00:00:00 GMT+0000 (UTC)

Order cancellation

A customer can now cancel an order before the order is shipped if it has been placed using a registered customer account. Anonymous orders cannot be cancelled in the storefront. The cancel order button is available in the Order details screen:

After the order cancellation is confirmed, the order status becomes 'Cancelled' and no future changes to this order can be made:

Measurement unit prices on cart, checkout page, order confirmation, and order details pages

When products with units of measurement are purchased, the item price displayed in the cart, checkout, order details, and order confirmation pages contain the unit of measurement information, as shown:

If a customer logs in to the Storefront using a social account, the email address linked to this social account is automatically saved in the customer profile. The email address then prepopulates the email field in the checkout page when the customer places an order.

Price v1

Tue Jul 26 2016 00:00:00 GMT+0000 (UTC)

Publishing a price change event

Previously, there wasn't a way to know when a product's price changed. For third-party services like Algolia Search, knowing when a price changes is important information when you're searching for a certain price. The Price service now publishes an event for immediate price changes. The following price changes trigger the price-change event:

A price is created for a product.
A price for an existing product is updated.
A product's price is deleted.

The event is published only if the price change is effective immediately. For a price change that occurs at a later date, the service publishes the event when that price change takes effect (for example, a price change with a new date range).

To allow a third-party service to read this event, use the hybris.pubsub.topic=hybris.price.price-change scope.

For more information about the event, see the Events page.

For more information about the scope, see the Scopes in Price Service page.

Community

Mon Jul 25 2016 00:00:00 GMT+0000 (UTC)

Type-ahead search for Community Showcases

The new type-ahead search enables you to find showcases more easily on Community.
Enter the first three letters in the search bar on the top of the current showcase page to display a selection of relevant showcases.
Select a showcase from the result list to view the showcase's details.

Dev Portal

Wed Jul 20 2016 00:00:00 GMT+0000 (UTC)

Search improvement

Previously, searching in the Dev Portal was slow and faulty. We received feedback from the community that the search engine froze the whole page. This happened because the search function triggered every time the search query changed. If the query was short (for example two characters), there were so many matching records that it could freeze the page until all the results loaded. This search brought no real value and prevented users from typing proper queries until the results loaded.

From now on, the search function triggers when you finish typing and, for slow typers, only when you enter three or more characters.

If your search query is too short, this information appears:

Solutions section in Dev Portal

YaaS is a platform that you can use to build various solutions. Each solution, depending on its complexity, can consist of one or more independent packages that are available for subscription on the YaaS Market. Therefore, we are happy to announce a new section in the Dev Portal, called Solutions. The new section aims to explain all the technical details concerning solutions currently available on YaaS.

Your feedback is very important and valuable for us, so thank you and keep it up.

ERP SD Customer Proxy v2

Mon Jul 18 2016 00:00:00 GMT+0000 (UTC)

Resolved Issues

The update resolves the issue of simplified and enhanced management of ERP customers in ERP SD Customer Proxy v2. You must update your subscription to fix these issues.

ERP SD Configuration v1

Mon Jul 18 2016 00:00:00 GMT+0000 (UTC)

Resolved Issues

The update resolves the issue of generating mixin schemas in the ERP SD Configuration v1 service. You must update your subscription to fix these issues.

Customer v1

Mon Jul 18 2016 00:00:00 GMT+0000 (UTC)

New "link" field in POST response body

A new field, link, is included in the body of the response to a POST request. The link field contains the full path to the resource created.

New configuration keys for customer emails

The following configuration keys are now available for changing the headers of customer emails:

cust.notification.email.from - The corresponding value assigned for this key in the customer setting is used to set the sender's email address as part of the email header.
cust.notification.email.from.name - The corresponding value assigned for this key in the customer setting is used to set the sender's name as part of the email header.
cust.notification.email.replyTo - The corresponding value assigned for this key in the customer setting is used as the sender's reply email address, as part of the email header, when a recipient responds.
cust.notification.email.replyToName - The corresponding value assigned for this key in the customer setting is used as the sender's reply name, as a part of email header, when recipient responds.

Coupon v1

Mon Jul 18 2016 00:00:00 GMT+0000 (UTC)

New "link" field in POST response body

In the Coupon service, a new field, link, is included in the body of the response to a successful POST request. The link field contains the full path to the resource created.

Service SDK 4.10.1

Fri Jul 15 2016 00:00:00 GMT+0000 (UTC)

With this release we fixed an issue with missing overlay artifact WAR for the ApiConsole in version 4.10.0. We extended yaasAware trait to reflect the headers mentioned in Hybris-specific headers. Also we fixed some usability bugs that affected API Console and improved our documentation.

Builder

Fri Jul 15 2016 00:00:00 GMT+0000 (UTC)

This release includes two new features:

Define Blocking Rules for Services
Use Builder Modules in Project

Define Blocking Rules for Services

You can now define blocking rules that prevent a tenant from using a higher metric amount than the limit specified. For each metric key, which is the name of the blocked property, you can define the endpoint (Path) and the methods (GET, PUT, DELETE, and POST) that become blocked after the specified limit is reached. The limit is defined in the publishing tab in the package which contains the service.

Use Builder Modules in Project

A new toggle button is available on the Builder module view named, Use this Builder Module for my Project. With this feature, test the functionality of a Builder module easily before wrapping it into a package. Simply select the toggle button, as shown in the screenshot below, to make the Builder module appear in the navigation on the left side:

There are more changes and improvements on the way, so check back soon for the latest updates!

RAML Patterns 1.2.2

Fri Jul 15 2016 00:00:00 GMT+0000 (UTC)

Features

We adjusted the yaasAware Trait to reflect the headers mentioned in the documentation as Hybris-specific headers and also changed the way of how we display the traits in the overview.

Checkout v1

Wed Jul 13 2016 00:00:00 GMT+0000 (UTC)

Sorting and paginating

The Checkout service now supports paginating and sorting of the query parameters. Sorting and paginating the parameters allows you to view the results in an organized format and find specific orders with ease.

Pagination is based on two parameters: pageSize and pageNumber Page size determines how many results are displayed on a single page, while page number determines which page you are viewing (if the results span more than a single page). By default, if you do not specify a page size or page number, a GET request displays 1000 results per page and the results appear on page one first. If you set a page number, but no page size, it displays 16 results per page. If you set a page size, but no page number, the results of the first page are displayed.

You can sort in ascending or descending order based on the following query parameters:

customer ID (customerId)
order created (orderCreated)
completed checkouts after a failed initial attempt (checkoutCompleted)
checkout modification date and time (modifiedFrom and modifiedTo)

If a sort order is not specified, the results are sorted in ascending order.

For more information on sorting and paginating, see the Retrieve a Checkout tutorial.

YRN support

The Checkout service now supports the YaaS Global Resource Name (YRN) concept. The YRN concept is described as a best practice in the YaaS DevPortal. See Resource Identifier. Corresponding YRNs are supported for the following parameters:

cart ID
cart item ID
checkout ID
customer ID
discount ID
order ID
price ID
product ID

Display additional information in orders

To make the order more informative, two new parameters are now passed from the Checkout service to the Order service. They are:

the item's original price
the payment mode (live or test)

Tax v1

Tue Jul 12 2016 00:00:00 GMT+0000 (UTC)

Sorting and paginating tax codes

The Tax service now supports sorting and pagination of tax codes. Being able to sort and page the tax codes allows you to view the results in an organized manner and gives you the ability to find specific tax codes with ease.

You can sort the tax codes in ascending or descending order based on the code and siteCode parameters. If a sort order is not specified, the results are sorted in ascending order.

For more information on sorting and paginating, see the Retrieve a Tax Code tutorial.

Media v2

Fri Jul 08 2016 00:00:00 GMT+0000 (UTC)

New query parameter

Going forward, you can use the content-type query parameter to filter your media files. The new parameter is available under the following endpoints:

/files
/public/files
/bulk/variants

The query parameter content-type filters your files by the content type that was specified during the upload of media files, so if you uploaded an image as a binary/octet-stream content type, you are not able to retrieve it by querying for the image/jpeg content type.

This functionality is useful to get or delete a particular type of files, for example, all invoices that you know are stored as PDFs. The useful example is to filter files by content-type image/jpeg, image/png ant image/gif. This way you receive only those files which are supported for transformation. To learn more, see Filter media by content type section of the Media service documentation.

Order Stripe v1

Wed Jul 06 2016 00:00:00 GMT+0000 (UTC)

Features

Stripe order service adds known channel (from where the order originated) to order service while creating an order in YaaS order service. Right now, the only known channels are Twitter and Stripe.

Customer v1

Wed Jul 06 2016 00:00:00 GMT+0000 (UTC)

Technical Tasks

The configurations of tenant are fetched from configuration service in a single GET request

Configuration v1

Wed Jul 06 2016 00:00:00 GMT+0000 (UTC)

Simultaneously updating the same configuration property made safer

The Configuration service now implements the optimistic locking mechanism, which means that it is possible to protect yourself from unexpected results of simultaneous updates of the same configuration property. To do so, add the version query parameter to any property-modifying calls and include the version you previously received in the payload. Please refer to the Configuration service documentation for more information.

Faster API Console

We migrated to the improved API Console that was introduced with the 4.10.0 release of the Service SDK.

Order v1

Wed Jul 06 2016 00:00:00 GMT+0000 (UTC)

New fields show order origination and total taxable amounts

A new optional field for an order, channel, can show where orders originated from. The channel attribute consists of two values, name (string) and source (URL). For example, name can be something like "Twitter" and source can be the URL of a tweet "https://twitter.com/hybriskiwis/status/707599225782214656".

A new field, taxable, added to the taxLine, represents the total taxable amount for each line.

Technical Tasks

The configurations for the tenant resource are fetched from the configuration service in a single GET request.

Customer v1

Thu Jun 30 2016 00:00:00 GMT+0000 (UTC)

Bug Fixes

Multi-tenant authentication tokens are now used when communicating to the Document Service to allow correct access to client's data.

Cart v1

Tue Jun 28 2016 00:00:00 GMT+0000 (UTC)

Additional YRN support

Previously, the YaaS Global Resource Name (YRN) concept was introduced in the Cart service to support the product YRN in the product attribute of the cart item.

To further support addtional YRNs, the Cart service now supports YRNs in the following locations:

When you add an item to the cart, the response returns the item ID (itemId) and corresponding YRN (yrn).
When you add an item to the cart, the request contains the price ID (priceId) and possibly the price YRN (yrn). It is not mandatory to include the price YRN in the request.
When you create a new cart, the response returns the cart ID (cartId) and corresponding YRN (yrn).
When you add a discount to the cart, the request contains the coupon code (code) and possibly the coupon YRN (couponYrn). It is not mandatory to include the coupon YRN in the request. The response returns the discount ID (discountId) and corresponding YRN (yrn).

For more information about YRN support, see the tutorials in the Cart service.

Tax v1

Tue Jun 28 2016 00:00:00 GMT+0000 (UTC)

New YRN identifiers

The Tax service now associates, with every newly-created tax code, an identifier that is based on the Uniform Resource Name (URN) schema called the YaaS Global Resource Name (YRN). The YRN concept is described as a best practice in the YaaS DevPortal. See Resource Identifier.

The service returns the YRN in the response body and provides a way to uniquely identify and locate a particular tax code.

For backward compatibility, the Tax service currently returns, where applicable, both tax code id and yrn. Requests to locate and modify a tax code must still supply a resource id.

Price v1

Mon Jun 27 2016 00:00:00 GMT+0000 (UTC)

New group attribute

Now when you create a new price for your product, you can also group certain products together using the new group attribute. Using this attribute allows you to create prices for individual products while assigning them to a group so you can retrieve the prices for all of the products within the same group with ease (instead of retrieving prices for products individually). Keep in mind that although the service supports prices that are created with the product ID or the item YRN, you can only use the group attribute if you create the price using the item YRN.

For more information on how to add the group attribute when creating a new price, or how to retrieve all of the prices for a specific group, refer to the Create multiple prices for a tenant and Retrieve all prices by query parameters sections in the Querying tutorial.

PubSub v1

Fri Jun 24 2016 00:00:00 GMT+0000 (UTC)

Max length for the topic eventType increased to 64 characters

Due to popular demand, the maximum length constraint for the topic eventType has been relaxed. The topic eventType can now contain up to 64 characters, instead of only 32 characters.

For more details, see the PubSub RAML contract, specifically the JSON schema for the /topics resource in the PubSub API console.

This change in the PubSub contract is backward-compatible, so all existing clients should not be affected.

Dev Portal

Fri Jun 24 2016 00:00:00 GMT+0000 (UTC)

List of scopes for existing applications available in interactive documentation

In interactive documentation, you can select the existing project to use later in the document. Before this release, the result of your selection looked like this:

The feedback from the community was that sometimes a selected application doesn't include the scopes that are required for the interactive document. You may not be aware of that, or you may not remember all the scopes your application has.

Now, when you select an existing application, you can clearly see which scopes it contains:

After expanding the list, you can see a full list of application scopes:

Builder

Thu Jun 23 2016 00:00:00 GMT+0000 (UTC)

This release includes the following new features and improvements:

Dev Teams and Projects merged
New Publisher mode
New default user roles
Applications renamed to Clients and new service access functionality
Package makeover
Test package creation disabled

Dev Teams and Projects merged

When you sign in to the Builder, you'll notice its new appearance. Previously, there was a column for Dev Teams and a column for Projects & Sites.

Now, there is only Projects. Don't worry, your Dev Teams did not disappear. They are still there, but all teams functionality is now merged into Projects.

The functionality for Dev Teams and Projects is still available. The navigation still contains all the nodes that were previously available in Dev Teams as well as Projects & Sites:

Please note that the available navigation is defined by the user role assigned to you for a project. For more information, see the section New default user roles.

New Publisher mode

To publish packages in the YaaS Market, you must enable Publisher mode. To use the Publisher mode toggle, open your project and select Administration > Details.

You can turn on Publisher mode at any time. When you enable Publisher mode, an additional tab labeled Publishing appears for all of your packages within the selected project.

In the Publishing tab, you can enter all publishing-related data such as Terms of Service, Marketing Content, screenshots, and pricing conditions.

New default user roles

Two new default user roles are available: the Publisher role and the Developer role.

Since some of the new navigation nodes within projects are not applicable to all project team members, access to different areas of the Builder can be restricted by user role. A marketing person, for example, doesn't need access to service administration, while a developer likely won't provide marketing content for a package. Therefore, different user groups now see different nodes in their navigation:

Applications renamed to Clients and new service access functionality

Applications are now called Clients. We extracted the clients from Services and merged them with Applications, making the creation of a service even easier. All you need to do is provide the unique identifier for your service and a version:

Like before, you can secure your service with basic authentication and add authorization rules to allow different methods for each endpoint of your API. Additionally, if you want your service to call other services, you can add a client to your service that defines the scopes and grants access to other APIs. You can add from the list of your existing clients or create a new one directly from the service:

When you click New Client, a wizard guides you through the process: Choose required scopes and enter the Identifier and Display Name. Click Save to automatically attach your new client to the service.

Previously, you had to decide in the beginning whether to create a service that interacts with other services or not. Now you can add a client to a service whenever you want.

Package makeover

The Package tabs are renamed and their contents reshuffled to improve the interface.

In the Configuration tab, you can add the services and Builder modules that will be delivered with your package to subscribers:

Access Control allows you to whitelist other projects, from other organizations, that can subscribe to your package without publishing your package to the YaaS Market:

The Publishing tab contains all publishing-related data such as Terms of Service, Marketing Content, screenshots, and pricing conditions:

The Publishing tab appears only when you set your project to Publisher mode.

Test package creation disabled

It is no longer possible to create test projects. Because the number of projects is limited for each organization, automatically setting up test projects can create a problem when an organization reaches its project limit. It is still possible to test a package. Simply subscribe to the package within the current project and start testing instantly.

There are more changes and improvements on the way, so check back soon for the latest updates!

hybris techne v1.3.0

Mon Jun 20 2016 00:00:00 GMT+0000 (UTC)

Techne v1.3.0

Major/New Updates

In order to make your UI design work even faster and have better consistency across Builder UI Modules we’ve introduced some starter page layouts you can use and customize as needed. These starter layouts include:

Table page
Cards page
Detail 1 page
Detail 2 page

We look forward to feedback on these starter pages and suggestions for other starter pages you might find useful.

Full Screen View of Screenshot component: standard component to enlarge screenshots included in UI modules

Included a Feedback Form component so you can easily add the Feedback form to any module in a consistent way with the rest of Builder

Included a standard “Back to Top” component for pages that are long

Minor Updates

Fixed Back Button animation
Clarified pagination usage guidelines
Updated and made consistent styling of modals
Updated Help component text so it is all italic
Updated tabs for better mobile usability

Cart v1

Fri Jun 10 2016 00:00:00 GMT+0000 (UTC)

Channel support

Through the use of embedded commerce, you can sell your products on various channels (such as the YaaS Storefront, Twitter, and Pinterest to name a few). To support these new channels, the channel information needs to be received by the Cart service from the client application.

Now when you create a cart, the channel information is added to the cart.

Product YRNs

The Cart service now supports the product's YaaS Global Resource Name (yrn) in the product attribute of the cart item. When you add a product to the cart, you can use the product's ID or the YRN. For more information about YRNs, see the Resource Identifier section in the DevPortal.

Social Media User v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

The Social Media User service is used to store and manipulate social media user data, which can be harvested from social media channels. You can map the harvested social media users to Engagement Center customer accounts. This enables you to understand your customers better, based on their social media activities. The Social Media User service also provides the functionality of basic consent management. You should make sure that the social media user data you stored in this service is fully compliant with all applicable laws and regulations. SAP does not accept any liability for the use of the service.

Using this service, you can:

Retrieve social media users.
Store social media users.
Delete social media users.
Update social media users.

Social Media Post v2

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

New parameters and endpoint added for manipulating social media data

The Social Media Post service now supports pageNumber and pageSize parameters, you can also use q parameter to search multiple data fields from the Document service. In order to avoid accidentally updating or deleting social media data, you should keep the following rules when using q query parameter for PUT and DELETE methods:

communicationMediumID must be valid
socialPostRootID and socialPostID cannot be null or empty at the same time

Meanwhile, a new endpoint to this service /{tenant}/socialMediaPosts/{id} is added to this service, You can used it to manipulate social media data stored in the Document service. The id parameter is a mandatory field if you want to access the data.

Service Ticket Mashup v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

Manage attachments

You can now use the Service Ticket Mashup service to manage attachments for a service ticket. The new capabilities are as follows:

Upload attachments for a given service ticket. The allowed file types are *.txt, *.png, *.jpg, *.mp4, and *.pdf. The total uploaded file size for a service ticket cannot exceed 1.6 MB.
Modify the file name of attachment.
Delete an attachment.
Retrieve the download link for the specified attachment. The download link will expire after one minute upon retrieval.
Delete all attachments for a service ticket.

Dispatch service tickets

You can now use the Service Ticket Mashup service to dispatch service tickets. If the status of an unassigned service ticket is OPEN or INPROCESS, the service dispatches the ticket to a user assigned to the service ticket user group in the Contact Center Settings. Users can accept or reject the service tickets they receive. Details are as follows:

Use the new endpoint {tenant}/dispatchingSetting to configure dispatch settings for service tickets.
If a new service ticket is posted without an assigned processor, the Service Ticket Mashup service sends a request to the Contact Center for dispatching. This happens only when the service ticket dispatch setting is switched on.
The request body of the PUT operation for the endpoint {tenant}/serviceTickets/{id} is enhanced with the new attribute cctrTaskStatus. If the modified service ticket is unassigned, with the status of Open or InProcess, you can set the value of cctrTaskStatus to TO_BE_SENT to trigger dispatch again. This happens only when the service ticket dispatch setting is switched on.
The response body of the GET operation for the endpoints for retrieving a service ticket is enhanced with the new attribute cctrTaskStatus. Use it to indicate the status of sending a request to the Contact Center for dispatching.

Service Ticket v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

You can now use the Service Ticket service to manage attachments for a service ticket. The new capabilities are:

Upload attachments for a specified service ticket. The allowed file types are *.txt, *.png, *.jpg, *.mp4, and *.pdf. The total uploaded file size for a service ticket cannot exceed 1.6 MB.
Modify the file name of attachment.
Delete an attachment.
Retrieve the download link for the specified attachment. You should notice that the download link will expire after 1 minute.
Delete all attachments for a service ticket.

ERP SD Customer Proxy v2

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

With this release of the ERP SD Customer Proxy service, managing ERP customers is easier than ever before!

Features

With the ERP SD Customer Proxy service version v2, you can do the following:

Create an ERP customer in the SAP ERP system via BAPI BAPI_CUSTOMER_CREATEFROMDATA1.
Update an ERP customer in the SAP ERP system via BAPI BAPI_CUSTOMER_CHANGEFROMDATA1.
Retrieve the sales areas of a given ERP customer.

What's new

Compared to v1, the v2 ERP SD Customer Proxy service has the following added capabilities:

The interface for creating and updating ERP customers is simplified. Now you do not need to use the mixin schema generated by the ERP SD Integration builder module, to pass some ERP specific customer data to the service.
The interface for creating and updating ERP customers is enhanced. Now you have access to all the import parameters supported by the BAPI, on the interfaces of relevant service operations.
The endpoint /{tenant}/messages provided in v1 is removed. You do not need to separately retrieve the error messages from the endpoint. Now you can directly get error messages returned by the BAPI or any other errors from the response body, in the process of creating or updating ERP customers.
A new endpoint is provided to get all sales areas of a given ERP customer.

SAP Jam Communities v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

Use the new SAP Jam Communities service to integrate YaaS functionality with the SAP Jam Communities collaboration product.

With this service, you can:

Retrieve published questions and answers and the relevant comments from SAP Jam Communities.
Reply to a question or a comment.
Get all of the messages and participants who post questions or comments within a specific conversation.
Manage the configuration of SAP Jam Communities.
Manage SAP Jam Communities user data.

Price v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

Resolved issues

Previously, if you had a product with multiple price attributes (for example, original amount, unit of measurement, and sales price), you could not complete a partial update to the original price (originalAmount) attribute. In this scenario, you would receive a 400 error code stating that the price has already been defined for that specific product ID and currency. This error has now been fixed and you can now complete a partial update to the originalAmount attribute.

ERP SD Configuration v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

Support for generating mixin schemas

You can now use the ERP SD Configuration service to generate mixin schemas. The generated schemas can be added to the customer root level to store the ERP specific customer attributes. Using this service, you can also retrieve the links to the schemas stored within the Schema service. If you use the Customer Engagement Center package and its ERP Sales Order module, it’s a mandatory step to generate schemas via the endpoint.

Cart v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

Mixin enhancements

Currently, mixins can be added to the cart at the cart, cart item, and product levels. This feature has been enhanced to handle mixins in the following two scenarios:

When you merge an anonymous cart with a registered cart
When you complete a partial or full update to the cart

Prior to this enhancement, some mixins were lost when you merged or updated a cart.

When you merge an anonymous cart with a registered cart, two outcomes can occur. If the anonymous cart and registered have different mixins, the mixins will be consolidated when the two carts are merged. If the anonymous cart and registered cart have the same mixin but the mixin values are different, the cart retains the mixin values from the anonymous cart.

When you update the mixins in a cart, you can complete a partial or full update. A partial mixin update lets you add a new mixin or update an existing mixin value in the cart. If you do a full update, the entire cart is updated with the content sent in the request.

Engagement Center Indexing v1

Tue May 31 2016 00:00:00 GMT+0000 (UTC)

The latest enhancement for the Engagement Center Indexing service supports the upgrade of the Product service from version 1 to version 2. In the Product service v2, the former sku field is now name code. To maintain compatibility, the value of the code parameter is now assigned to the sku parameter in the Engagement Center Indexing service. You can retrieve the value of code from the sku field.

Service SDK 4.10.0

Tue May 24 2016 00:00:00 GMT+0000 (UTC)

This release integrates the latest version of the open-source API Console into the Service SDK, improving performance and security. The API Console integration into your YaaS service is now more clean and robust. If you develop a new service based on the Service SDK Archetype, you benefit from these improvements.

This new feature deprecates the old approach for integrating the API Console. However, existing services using the old approach is supported until the next major release of the Service SDK.

Migration to new API Console

To migrate your existing YaaS service from the legacy API Console to the new one, follow this integration guide. Then, remove the legacy API Console by removing the registration of ApiConsoleFeature in your Jersey configuration, usually found in the JerseyApplication class of your service.

Order v1

Mon May 23 2016 00:00:00 GMT+0000 (UTC)

Features

Customers can now cancel an order that is not yet SHIPPED. For this purpose, there is a new endpoint, /{tenant}/orders/{orderId}/transitions, for GET and POST operations.

To make GET or POST calls on this endpoint, the hybris.order_update_as_customer scope is required, which is automatically granted by the Customer service after the customer logs in.
The GET operation returns an array of possible transitions for an order that can be made by a customer. But because customers can only make transitions to declined, the response is either empty or an array of a single status – DECLINED.

Example Response:
```
[
{
  "status": "DECLINED"
}
]
```
The POST operation changes the status of the order to the status that is indicated in the request body. Example Request:
```
{
 "status": "DECLINED"
}
```
If a customer tries to make transitions that are not allowed, the service returns 403 – Forbidden with an appropriate error message.

Dev Portal

Mon May 23 2016 00:00:00 GMT+0000 (UTC)

Release note links on landing pages

The API Docs and Tools & Resources landing pages now include links to release notes for the service or tool you are viewing. Click any release note link to read up on the latest or previous changes.

This image shows the release notes links on the API Docs landing page.

This improvement has been added, because your feedback was that:

Previous list with all services on API Docs landing page didn't bring any real value to you,
You like when there's a link to release notes in documentation of specific service. Therefore the decision was to do the same for landing pages.

Interactive documentation searchable

The Dev Portal search results now include interactive documentation.

To try out the new functionality, search for this example sentence, To perform the basic operations supported by the Product service. A Product service document with the title Basic appears.

Improved play buttons in interactive documentation

The Play Notebook button in interactive documentation has a new look. The button is now named Execute All and appears in two places in the tutorials, so you no longer need to scroll to the bottom to start a tutorial.

As shown in this image, the second Execute All button is located at the beginning of each tutorial.

This change was driven by your feedback. It was confusing for you why it says Notebook and why you have to scroll to the bottom of each document to start it.

We appreciate your feedback. Keep letting us know how we can improve.

Customer v1

Mon May 23 2016 00:00:00 GMT+0000 (UTC)

Features

hybris.order_update_as_customer scope is granted in addition to existing scopes to a customer on login. This scopes allows customers to transition the orders they have placed to declined.

Email Builder Module v1

Fri May 20 2016 00:00:00 GMT+0000 (UTC)

Create and delete templates in the Builder

You can now create and delete templates directly in the Builder. Finally, you can perform all template management tasks using the Builder web interface instead of having to make direct REST calls.

Builder

Thu May 19 2016 00:00:00 GMT+0000 (UTC)

This release includes the following new features and improvements:

Securely change passwords
Assign roles to staff members
Disable auto logout
Delete images for organization, profile, and packages
Download invoices
View statistics on the number of package subscribers
Create organizations more easily

Securely change passwords

We improved the method of changing the password in your profile and made it more secure. Previously, you were able to just set a new password. Now you need to know the current password to be able to change it, as shown in the image. If you do not provide the current password, you will not be able to save the new password.

Assign roles to staff members

We simplified how to assign a role to a staff member. In the past, you had to enter the whole email address to assign a particular user role to a user in your team or project. Now, you can choose, from a drop-down list of all users within your team or project, the user to whom you want to grant the rights for the selected user role. You can start typing the name of a user and the list filters the suggested users according to your typing.

Disable auto logout

For security reasons, the Builder logs you out after 30 minutes of inactivity. However, we received several requests to provide the ability to stay logged in. While we didn't completely disable auto logout, you can now remain logged into the Builder for the current session, until you log out on your own or close the browser window. After 30 minutes, you will be informed one time that your session is about to expire. You can check the box to stay logged in. The session expiration pop-up will not appear again for the remainder of the session.

Delete images for organization, profile, and packages

You can now remove images from your organization, your profile, and your package icons. To do so, simply click the red x on the right side of the icon and the previously selected image will disappear. You still need to save the change in the header bar.

Download invoices

You can now download your invoices. To download invoices, navigate to your Organization page, and then click Bills. Click the Download link to open the selected invoice in a new window, where you can save it as a PDF. Please make sure that your browser allows pop-ups from YaaS.

View statistics for the number of subscribers

As a package provider, you can see how your package is used and how many users subscribed to it in the last six months. On the package details page, click the Statistic link to view details on package usage.

Create organizations more easily

Previously, when you created an organization, you entered the country your organization is located in. Now, you must select your organization’s purpose of use for YaaS. You can chose between Commercial and Non-commercial. If you choose Non-commercial, you can test and play around with YaaS and subscribe to the Beta packages that are available on the YaaS Market. All countries are allowed to use YaaS for non-commercial purposes, including the US.

When you create a non-commercial organization, you do not need any further approval. You are automatically allowed to subscribe to the Beta packages.

Subscribing to commercial packages is still restricted to US-based companies. When you select Commercial, “United States” is the only option available in the Country drop-down list on the Organization Address page, as shown. You still must complete the approval process. A wizard guides you through the mandatory fields that must be completed before sending the form to the back end systems.

There are more changes and improvements on the way, so check back soon for the latest updates!

Media v2

Sun May 15 2016 00:00:00 GMT+0000 (UTC)

Media V2 image cropping and image variants

The Media V2 upgrade includes awesome new features that provide more options for image management.

Crop images

In addition to image clipping, Media V2 now supports cropping - resizing the original image to fit within the desired dimensions by cutting off the edges.

Add new variants to existing images

After you upload an image, you can also trigger the creation of new variants by making a POST request on the variants endpoint, with the variants specified in the query parameters.

Delete variants

It is now possible to delete variants. Just make a DELETE request on the variants endpoint to remove all of the variants. Pass query parameters in the request to remove specific variants.

For more information head over to the docs!

Cheers,

Framefrogs

Stripe Order v1

Sat May 14 2016 00:00:00 GMT+0000 (UTC)

The newly-released Stripe Order service is part of the Stripe Relay In-App & Social Sales package. This package allows merchants to sell products directly within applications via Stripe Relay.

For more information about this service, see the Stripe Order service documentation.

Stripe Order Webhook v1

Sat May 14 2016 00:00:00 GMT+0000 (UTC)

The newly-released Stripe Order Webhook service is part of the Stripe Relay In-App & Social Sales package. This service's role is to receive orders from Stripe and notify the Order Stripe service to create the orders on the YaaS side.

For more information about this service, see the Stripe Order Webhook service documentation.

Storefront Template v1.0.4

Thu May 12 2016 00:00:00 GMT+0000 (UTC)

Image carousel on product details page improved

On the Product Details page, the carousel with the product images has been improved. As a result, the zoom function on a desktop, in full screen mode, and when changing between thumbnail images for a product, provides a better user experience than previously. Zoom is no longer available on mobile.

Out of Stock button disabled when the product is out of stock

When a product is out of stock, the Out of Stock button on the Product Details page is disabled.

Because Google+ sign-in is deprecated, we have migrated to Google sign-in. After the user signs in to the Storefront with a Google account, if Google returns an avatar, the application displays it as the user's profile picture in My Account.

API Management v1

Thu May 12 2016 00:00:00 GMT+0000 (UTC)

No more applications

Simplifying the YaaS experience is entering a new stage. We deprecated the endpoint /applications in the API Management service and replaced it with /clients. This eliminates the confusion behind the common idea of an "application" and is more consistent with the OAuth 2.0 framework.

The functionalities of both endpoints are equal. The changes are not yet in the Builder. Stay tuned for a further announcement.

The final calling date for /applications is September 1, 2016.

Coupon v1

Wed May 11 2016 00:00:00 GMT+0000 (UTC)

Features

Redemption event now consists of a new property – 'issuedTo' that contains the customer number, to whom the coupon was issued.

Loyalty Email v1

Mon May 09 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Email service enables you to create and upload email templates in multiple languages so that you can send repetitive emails by making a simple REST call. You can send emails to intimate your customers of activities such as:

Successful registration
Order confirmation
Account expiration
Referral emails
Tier upgradation
Offers

These types of emails are sent to one person as a result of an action triggered by the user. You can create and manage email templates for any use case.

Examples:

Send a registration email to a customer when they register to the loyalty program.
Send an order confirmation email to a customer that lists their order details.
Send a referral email to friends for registering to the loyalty program.
Send an email to a customer when they upgrade their tier. For example, when a customer upgrades from the bronze to silver tier.
Send an email to a customer to inform about account expiration.
Send an email to a customer to inform about offers on any product.

Loyalty Member v1

Mon May 09 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Member service allows you to:

Manage loyalty programs and tiers.
Manage loyalty member information such as user, status, tier, points, and registered on.
Manage member activity information such as registration, order, redeem, rating, review, and expiration.

Fault tolerance introduced for the member service so that it retries partially disrupted calls.
Service now generates human readable member numbers.
Email is no longer the unique identifier for the member but customerid.

Loyalty Cards v1

Mon May 09 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Cards service enables you to design templates for your digital loyalty cards and coupons, and offer them as part of your loyalty program.

The Loyalty Cards service allows you to create digital loyalty card and coupon templates for Apple and Google wallets.

Loyalty Card Service provides REST service to create, update and view loyalty card and coupon templates for Google and Apple wallets. In addition, the loyalty card service also provides service for one time configuration of certificate and merchant details required to configure Apple or Google wallet service.

A Loyalty administrator can configure cards and coupons for Apple and/or Google wallets from Configuration > Wallet Configuration menu.

Loyalty Card service now supports multiple languages. Loyalty Card templates can now be saved in multiple languages which are supported by the tenant.

Scopes prevent unauthorized access to loyalty micro services. The accepted scopes for Loyalty Cards service are:

sap.loycard_view - View Google and Apple loyalty card and coupon templates
sap.loycard_manage - Create or edit Google and Apple loyalty card and coupon templates

Note: Deletion of template for digital loyalty cards and coupons is currently not supported.

Loyalty Apple Wallet v1

Mon May 09 2016 00:00:00 GMT+0000 (UTC)

Features

Apple Wallet gives users a convenient way to organize and use rewards cards, boarding passes, tickets, and gift cards. You can bring up passes in your app with PassKit APIs, send them via email, or post them on the web. You can also set the time or location for an item to appear.

Passes are a digital representation of information that might otherwise be printed on small pieces of paper or plastic. They let users take an action in the physical world. Passes can contain images and a barcode, and you can update passes using push notifications. The pass library contains the user’s passes, and users view and manage their passes using the Wallet app.

The Loyalty Apple Wallet service will enable you to download and update loyalty card and coupon passes on supported iOS devices.

Loyalty Apple Wallet service now supports multiple languages. The Loyalty Card passbook can now be saved on compatible Apple devices in the preferred language of the member.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Apple Wallet service are:

sap.applewallet_view - View Apple loyalty card and coupon configuration for Apple Wallet
sap.applewallet_manage - Manage or edit Apple loyalty card and coupon configuration for Apple Wallet

Loyalty Analytics v1

Mon May 09 2016 00:00:00 GMT+0000 (UTC)

Features

Analytics service is now more flexible, robust and easy to use. It does not directly required and respond with standard Elastic Search query, rather it deals with very generic format.

Loyalty KPIs enhancements:

Member Revenue: Total revenue generated from loyalty program members can be shown in currency (sum of all the revenue in one currency).

Loyalty Charts enhancements:

Member Revenue ($) by Month / Qtr / Year per Tier can be shown in multiple currencies.

In this release, Analytics service provides better way of filtering charts and kpis.

Service SDK 4.9.1

Wed May 04 2016 00:00:00 GMT+0000 (UTC)

With the new release of the Service SDK, we improved functionality and fixed some bugs.

Bug fixes

Fixed wrongly generated setters for complex objects that use additionalProperties.

Stripe Payment v1

Tue May 03 2016 00:00:00 GMT+0000 (UTC)

Deferred payment

Previously, when you checked out an order, the payment was captured during the checkout process. Now with the deferred payment feature, you can authorize the payment during the checkout, but the customer's credit card will not be charged until the order has shipped. This gives the merchant the flexibility to determine how they want to charge their customers.

If the merchant has set the payment settings to capture after an order is shipped, the payment is only authorized during the checkout process. The payment transaction ID and pending status is sent to the Order service. After the order has been shipped, the transaction ID is used to capture the payment.

For more information, see Deferred Payment.

Checkout v1

Tue May 03 2016 00:00:00 GMT+0000 (UTC)

Deferred Payments

The Checkout service now supports the new deferred payment feature in the Stripe Payment service. When a customer checks out their cart, their credit card will either be charged at the initial checkout or after their order has been shipped. This depends on how the merchant decided to set up their payment settings. If the merchant chooses to have the payment captured once the order has shipped, the payment call made during checkout will return a transaction ID and a payment status of pending, which will be passed to the Order service. Once the order has been shipped, the same payment endpoint will be called again and the payment will be captured.

For more information, see the Deferred Payment page in the Stripe Payment service, or the payment information in the Checkout Process documentation.

Media v2

Fri Apr 29 2016 00:00:00 GMT+0000 (UTC)

Resizing the image files in the Media service V2 is now possible

You can now upload your master image file and then trigger a transformation process to create multiple variants of different sizes. This can be useful if you need to resize images in your application to accommodate different devices, such as mobile devices or standard desktop computers.

What's new:

You can now specify additional image sizes of your master image file by performing requests on the /files endpoint with the size query parameter and its required value. The master image will be automatically transformed to multiple variants.
To retrieve a specific variant of your image file, perform a GET request on the /files/{fileId} endpoint.

Dev Portal

Fri Apr 29 2016 00:00:00 GMT+0000 (UTC)

Before this release, Dev Portal pages did not print correctly. The rendering issues have been fixed now so that you can easily share Dev Portal content offline with other parties.

The following images show how the generated PDFs looked in previous versions and how printed PDFs will look now, in the current version.

Thank you again for your valuable feedback.

Service SDK 4.9.0

Thu Apr 28 2016 00:00:00 GMT+0000 (UTC)

With the new release of the Service SDK, we added further support for easier authorization, fixed some bugs, and updated Maven dependencies. Please make sure your Maven dependency versions are not in conflict with Service SDK versions after the update.

Enabled generated client to use the new OAuth 2.0 Jersey Filter with the same client instance

You can now override the AuthorizationScope used by the OAuth2 Jersey Filter on a request basis. To do this, set a RequestProperty with the key OAuth2Filter.PROPERTY_AUTHORIZATION_SCOPE and the desired AuthorizationScope as the value anywhere in your client invocation call chain:

return documentClient
    .tenant(tenant)
    .client(CLIENT_NAME)
    .dataType(DATA_TYPE)
    .prepareGet()
    .withRequestProperty(OAuth2Filter.PROPERTY_AUTHORIZATION_SCOPE, new AuthorizationScope(tenant, SCOPES))
    .execute();

With this new functionality, you can reuse the same generated client instance for making calls that are authorized with a different AuthorizationScope.

Maven dependencies updated

Maven dependencies have been updated to the latest ones, including updating the Jersey library to version 2.22.2 and Spring dependencies to version 4.2.5.RELEASE. Please check your Maven dependency tree and update the versions in order to eliminate possible version conflicts.

Bug fixes

We fixed the problem of the API Console throwing a NullPointerException error when requesting a non-existing resource. We also improved the confusing JavaDoc of the RamlRewriterFilter.setTraitMappings() method, which was not in sync with the implementation.

Commerce Builder Module v0.2.15

Tue Apr 26 2016 00:00:00 GMT+0000 (UTC)

New Cancel button functionality

With this release of the Commerce Builder Module, the Cancel button functionality has been updated in accordance with the following Techne requirement:

Cancel: Stops the process the user has started and brings the user back to the page before they started the process. Cancel stops a new object being created, closes a modal or an edit page, ends a complete wizard and deletes all data changes. Most of the time, this pattern can be solved with a historical back using the Referrer from the Builder link manager.

Improved UX when deleting tax overrides on PDP

The user experience for deletion of tax overrides on the Product Details page has been improved. Before, the tax override would be removed from display when clicking the X on the tax override card, but the actual deletion would only happen when the user subsequently clicked SAVE. Now, when the user clicks the X on the tax override card, a modal dialog displays and asks the user if they are sure they wants to delete the tax override, and an API call to delete the tax override is made after the user clicks OK.

New alert when a site currency is updated

In this release we added a notification for the user whenever currency for a site is changed. This alert informs that shipping rates are affected by the change of currency and allows the user to navigate to the shipping settings for that specific site and make any necessary adjustments.

Stripe Connect and test mode

Stripe Connect is a new and easy way for you to integrate the Stripe payment provider with YaaS. With Stripe Connect, you can take advantage of the Stripe Relay feature that will be available in the upcoming Stripe Relay In-App & Social Sales package.

To activate Stripe, navigate to the following setup page:

your project > Commerce Settings > Payment Settings

Click Activate Stripe. You will be routed to the Stripe site to activate your Stripe account.

Once you are connected to Stripe, the Stripe private and public keys are stored in the Site setting.

If you are already connected to Stripe using the previous configuration, you have the option to remain as is, or to click on the Activate Stripe Connect button to update your configuration.

After you are connected to Stripe, its default is set to Live mode, which means you are ready to begin charging credit cards. If you want to test the checkout process and not charge a real credit card, you can toggle it to Test mode. Click the slider to toggle back and forth between these modes.

If you want to remove Stripe as your payment provider, click Deactivate and Stripe will be removed.

Storefront Template v1.0.3

Mon Apr 25 2016 00:00:00 GMT+0000 (UTC)

Until now a customer could change their contact email address in Storefront, but not the login email address. As customer service allows now login email address change, we have implemented also this in Storefront. The login email address can be changed from 'My Account' page once a user is logged in.

When changing the address, the user is prompted to enter his password. After pressing 'Save' button, an email notifying about the change is sent to the old address and another email requesting to confirm the change is sent to the new email address. After the user confirms the change, the login email is updated as requested. At the same time the customer contact email address is set to the changed login email address.

Main media for products and categories

From now on, the main media for products and categories is the first media item in the collection. You should no longer rely on the main attribute for product and image attribute for category. We also recommend a migration to make sure the order of your media is kept properly.

Add an item to the cart

An indicator has been added so you are aware that an item has successfully been added to your cart. When you add an item to the cart, a notification slides over the cart icon to show how many products have been added.

Add a note to the item

After an item has been added to the cart, you can add a note to that item. This field is for you to add extra information to the product.

Multiple coupons and coupon revalidation

You can now add multiple coupons to the cart. As you add and remove items from the cart, the coupon is revalidated with each cart update. If the coupon is no longer valid, a message appears that the order value is too low for that specific coupon. Note that even though the coupon no longer valid, it is not removed from the cart. If the coupon is valid again, the NOT APPLIED message is removed.

Billing and shipping address on checkout page

The placement of the billing and shipping addresses on checkout page has changed. After adding shipping configurations, the options in the country drop-down menu of the shipping address on checkout page had to be limited to the configured ship to countries of that specific site, while the country drop-down of the billing address should display all countries. To simplify the logic and ensure a smoother user experience (and because there was no real reason to display the billing address on top), we simply decided to switch the placement of the billing and shipping addresses. With this solution, the user will immediately see which countries are available destinations for delivery, while they have the option to add any country to their billing address.

Another change introduced in this release is an update to the drop-down menus themselves. The formerly used ui-select2 directive has been deprecated and it was recommended to start using the ui-select directive from Angular, thus all drop-down menus in the Storefront has been updated to use this new directive, also supporting search and scrolling.

Dev Portal

Thu Apr 21 2016 00:00:00 GMT+0000 (UTC)

We have improved the user experience for interactive documentation within the code cells and left navigation of the Dev Portal. Code cells are now more functional and easier to understand.

Play icon

A triangular play icon now displays in the left navigation of the Dev Portal next to sections that include interactive documentation.

Pencil icon for editable code cells in interactive documentation

The blue code cells in the interactive documentation can be edited directly. A pencil icon displays next to code cells that are editable.

Improved code hints in code cells

We improved the look and feel of the code hints that display when you type your code inside a code cell. Previously, they were placed directly between lines of code, which was confusing and disrupted the workflow. Code hints now display in their own layer above the code cell and are separated by a box shadow.

Expand/collapse functionality and indentation in responses in code cells

When you execute a code cell, a response displays below it. These responses are now indented for better readability.

You may also expand and collapse certain lines within a response. A small, triangular arrow displays next to lines that can be expanded or collapsed.

Red background for error responses

All error responses with status codes of 4XX and 5XX now have a red background for better visibility.

Stripe Payment v1

Wed Apr 20 2016 00:00:00 GMT+0000 (UTC)

Stripe Connect

Stripe Connect is a new and easy way for you to integrate the Stripe payment provider with YaaS. Previously, you needed to configure the public and private keys in the Site service, but with Stripe Connect, the merchant can configure Stripe with the click of a button in the Builder. With Stripe Connect, you can take advantage of Stripe's full API, including the Stripe Relay feature found in the upcoming Stripe Relay In-App & Social Sales package.

If you're currently using the old configuration with the public and private keys, you can continue to use this approach indefinitely, or you can reconnect Stripe using Stripe Connect.

To read more about this feature, see Stripe Connect.

Live Mode and Test Mode

You can switch between live or test mode in Stripe Connect. When you first configure Stripe using Stripe Connect, the liveMode attribute is set to true by default, which means that it only captures the payment with valid credit cards. If you switch to test mode, you can use a fake credit card to complete a payment capture for development purposes or to validate the payment process.

To read more about live mode and test mode, see the Live and Test Mode tutorial.

Cart v1

Tue Apr 19 2016 00:00:00 GMT+0000 (UTC)

Bug fixes

Previously you could use any currency code to create a cart. The code did not need to comply with any standards. This has now changed. The Cart service now checks that the currency code used to create the cart is valid according to [ISO 4217][1] standards. If the code is not valid, the service will return a 400 Bad Request error.

[1]: https://en.wikipedia.org/wiki/ISO_4217 iso4217

Builder

Mon Apr 18 2016 00:00:00 GMT+0000 (UTC)

This release includes the following new features and improvements:

New Website field added to the Organization Details page
New package update process

Website field added to Organization Details

On the Organization Details page, there is now a Website field to enter the URL for your organization. Associated teams and projects inherit the Website field value.

When you define the website for an organization, it populates the Publisher Website field on the Package Detail page of the Publishing tab. You can still edit the URL in the Publisher Website field, if necessary.

New package update process

We have made the first in a series of improvements in updating packages in the Builder.

Currently, every change on the package level is a breaking change and needs a new approval from the YaaS Market moderator.

Editing the package and clicking the Save button will create a new package version and put the package into a draft state. To push the new version to the YaaS Market, you must submit it again for approval.

You will be unable to modify the package while it is in review. You can edit the package again after it has been approved or declined.

After the package is approved and available in the YaaS Market, the Update button displays in the Subscription section of the Builder for customers who are subscribed to the previous version. Customers can click Update to resubscribe to the package.

Currently, customers who are already subscribed remain subscribed to the old version until the end of the current month. The new version becomes available on the first day of the following month.

There are more changes and improvements on the way, so check back soon for the latest updates!

Community

Mon Apr 18 2016 00:00:00 GMT+0000 (UTC)

In order to make it easier for you to contact the owner of a showcase, you can now sign in directly from the contact form, if you are not signed in already. Previously, you had to sign in to the Builder and then navigate back to the contact form.

New design for Community Showcases

The overview and details of the Community Showcases have a new design. The overview is now more compact and in a grid format. The tags are displayed in the details, but not in the overview. The mobile form is even more compact and does not show the short description anymore.

The details also have a new design. The tags were removed from the left section of the page and are now located in the content area on the right.

Bug fixes

Signing in to the Builder when using Internet Explorer now works correctly.
The ScreenShot Carousel now works correctly on narrow screens.

Category v1

Fri Apr 15 2016 00:00:00 GMT+0000 (UTC)

New Features and Functionality

Prior to this release, you could only assign single image to category. Starting from this release, you can create as many images as you need. For more information about this functionality, see Media Tutorial in category service documentation.

Image property is deprecated

Because image property on category will not be longer supported and it might be removed in future releases we strongly recommend using new endpoint for assigning images to category.

Service SDK 4.8.1

Thu Apr 14 2016 00:00:00 GMT+0000 (UTC)

Bug

In this release, we further hardened the service-sdk-api-console library against a security vulnerability that was fixed in the previous version (4.8.0). Users of this library are advised to upgrade to this latest version as soon as possible.

hybris techne v1.2.0

Wed Apr 13 2016 00:00:00 GMT+0000 (UTC)

Techne v1.2.0

Our second release of 2016!

We used Q1 to do some major clean up and refactoring, as well as improved guidelines and standards documentation. We also had our first contribution back to the library and we’re looking forward to more!

Major notes:

Fixed techne.yaas.io navigation on mobile devices
Clarified color coding of status indicators
Added Pills as a component to communicate status or state on detail panels
Added an orange ‘warning’ status color designation
Major cleanup on the bootstrap overwrites file for improved usage
Cleaned up the markup for Section Level Help
Removed the definition of the @bower-path variable. IMPORTANT NOTE: As some people need to change the path to their bower_components folder, we removed the default value for the @bower-path variable. In order to build your less files with techne, it is from now on required to define this variable on your own in your stylesheet. ( Example: @bower-path: '../../bower_components'; ):

Dev Portal

Wed Apr 13 2016 00:00:00 GMT+0000 (UTC)

We received feedback that the interactive tutorials were sometimes taking a long time to load, which made the documentation page unresponsive for several seconds. This was particularly noticeable when there were multiple interactive tutorials available on a single page.

Due to the technical complexity of the solution, it was not possible to improve the load times. Therefore, we have implemented manual loading for on-demand tutorials instead of loading them automatically. To load a tutorial, click the LOAD TUTORIAL button, as shown in the following image:

After you click the button, the following displays while the tutorial is loading:

There are no changes in usability. After loading, the interactive tutorials look and behave the same way as they did before.

Customer v1

Tue Apr 12 2016 00:00:00 GMT+0000 (UTC)

Features

An optional Boolean property named syncContactEmail can now be used to update the contact email when performing a POST request to change a login email address. If the property is set to true, then the contact email will be set to the new login email address when the login email is changed successfully. If the property is absent or set to false, then the contact email will remain intact and only the login email address will be changed.

Service SDK 4.8.0

Fri Apr 08 2016 00:00:00 GMT+0000 (UTC)

OAuth 2.0 authorization for Jersey made simple

The Service SDK Authorization Library now provides an OAuth2Filter component. This makes it even easier to authorize your requests to other YaaS services – at least when you're using Jersey/JAX-RS for these requests.

Other Improvements

Also, in the Authorization Library, the ClientCredentialsGrantProvider now comes with preset connection and read timeouts. This makes services more robust in the event of an outage of the OAuth 2 authorization server.

In generated clients, the Response is now always closed inside the RequestExecutor. This mitigates possible memory leaks when reading the response body as an InputStream and forgetting to close it later.

Bugs

Fixed potential vulnerabilities inside the service-sdk-api-console library. Users of this library are advised to upgrade to the latest version as soon as possible.

Also, the API console now transmits more appropriate media types when delivering static web resources.

Cart Calculation v1

Wed Apr 06 2016 00:00:00 GMT+0000 (UTC)

Bug fixes

Currently, you can configure multiple tax providers for a single site. The Cart Calculation service was calculating taxes by using the tax settings of the first tax provider you created. This calculation was incorrect. Now Cart Calculation service will check the multiple tax providers and use the Active tax for that particular site when completing the calculation.

Algolia Search v1

Thu Mar 31 2016 00:00:00 GMT+0000 (UTC)

New feature

A new feature has been added to the Algolia Search service to provide you with better and more useful information for error responses.

Details of validation errors

Users can validate Algolia credentials, such as validating the searchKey attribute for a specific application and index name. However, sometimes this validation results in an error.

With the latest feature update, the error message is more descriptive. The new complex details attribute has two fields named type and message that carry information about the error type. The attribute also provides a descriptive explanation of the error.

If validation fails, the type and message attributes (being part of the details attribute) may contain the following values:

invalid_api_key: The searchKey is invalid or does not grant access to the index.
unknown_application_id: The application ID is invalid.
invalid_index: An index with the specified name does not exist.

Cart v1

Mon Mar 28 2016 00:00:00 GMT+0000 (UTC)

Cart now supports inline schemas in mixins

The Cart service now supports inline schemas for the mixins that were previously added to the cart, cart item, and product level.

Previously, you could only add mixins by first defining them within the Schema service. Now you have more flexibility to define the mixins in the different levels of the API. This gives you the ease of creating new mixins within the service request rather than having to define them beforehand.

For information on mixins and how to create inline mixins, see the Extend Cart Information.

Coupon validation to not include shipping costs

When a discount is added to the cart, the coupon validation is made against the cart's subtotal which includes the shipping cost. This should not be the case. The coupon validation is now only based on the subtotal of the items within the cart. For more information about discounts, see Discounts.

Checkout v1

Mon Mar 28 2016 00:00:00 GMT+0000 (UTC)

Checkout now supports inline schemas in mixins

The Checkout service now supports inline schemas for the mixins that were previously added to the cart at the item and product level. The service is also able to handle the inline schemas that were added to the address and the customer attributes.

Previously, you could only add mixins by first defining them within the Schema service. Now you have more flexibility to define the mixins in the different levels of the API.

Bug fixes

When a product is given a price with more than 2 decimal places, the checkout validation was failing due to the rounding process that is implemented. To ensure that the customer can complete a successful checkout, the rounding validation has been fixed.

When the payment provider (Stripe Payment service) is not configured properly in the Site service, the system was returning an improper error code (404) and message. This issue is now fixed and it is returning the proper error code (500) and message.

Tax v1

Mon Mar 28 2016 00:00:00 GMT+0000 (UTC)

Bug fixes

Previously, if a discount was applied to a cart, it was being applied to the sum of the cart's subtotal and shipping cost. This calculation was incorrect and has been fixed. Discounts are now only applied to the cart's subTotalPrice (in other words, the total of the cart items).

For tax-inclusive products (VAT), if a discount is applied after taxes and the product's original price is reduced, the totalTax value should reflect the taxes on the reduced price and not the original price. The tax total is now calculated correctly.

Document v1

Mon Mar 21 2016 00:00:00 GMT+0000 (UTC)

From now on, to partially update a document in the Document service you can use the patch query parameter. This query parameter is introduced to align with the YaaS standards and to replace the outdated query parameter, partial. It works exactly in the same way as the old one. It is strongly recommended to use the patch query parameter instead of partial, however the Document service supports both to provide backward compatibility.

API Management v1

Thu Mar 17 2016 00:00:00 GMT+0000 (UTC)

Hear Ye! Hear Ye!

The new API Management service is now available. This Essential Service introduces major improvements in the management of applications and services.

New features and functionality

The service introduces major improvements in the management of applications and services and boosts the YaaS adventure.

Simplified initial YaaS experience: no more dev teams!

To improve the user's initial experience and understanding of YaaS, dev teams have been replaced with regular projects. All of the actions that can be performed for dev teams are also available for projects.

Publisher mode

Applications and services are visible for the project owner by default. As a project member, you can switch the Publisher Mode to ON in the Builder to see them.

No difference in applications

The functionalities for both types of applications are unified. Single-tenant applications (previously in projects) and multi-tenant applications (previously created for services) became one type of application. This limits the confusion connected with required scopes and service scopes. An application is created independently, and you can link it later to your service.

No YaaS URL in application identifier

The YaaS URL, referred to as the "base path" in the code, is still mandatory for every organization and is used in the service's proxy URL. However, it is no longer part of the application Identifier.

The above functionalities will be available in the Builder soon!

Storefront Template v1.0.2

Tue Mar 15 2016 00:00:00 GMT+0000 (UTC)

Styling and layout changes

The new release of Storefront template brings many styling and layout improvements. You will notice these changes right away in the product/category list pages, where sorting options and the product counter are better highlighted at the top of the page. Further updates are visible in the cart and checkout pages.

Product listing page

Cart

Checkout

Checkout process improvements

During checkout, once the customer clicks on the ‘Preview Order’ button, the page scrolls down automatically to the billing information. Several bugs related to shipping rates on checkout were also fixed.

In addition, we made improvements in the implementation of the translation files.

Order v1

Tue Mar 15 2016 00:00:00 GMT+0000 (UTC)

Order subTotalPrice field

With this release, a checkout client can now post the subtotal value of the order using the subTotalPrice field. This will eliminate the need to recalculate this value before it is served by the Order service when a user wants to read the details of the order, such as seeing the details of a placed order in the Builder UI or receiving the order details in a confirmation email. This will ensure that there is no room for any calculation inconsistencies.

The latest order schema is available here: order.json %>/hybris/order/v1/meta-data/schema/order.json)

Mixins in customer attributes

With this release, a merchant/checkout application can create an order with mixins in customer objects. The schema of a mixin should be specified in the metadata attribute.

For example:

"metadata": {
   "mixins": {
     "secondaryContactPhone": "<%- @partial('proxy_url') %>/hybris/schema/v1/kiwistest/contact-number.json"
   }
 },
"mixins": {
 "secondaryContactPhone": {
       "number": "+86 334 0033 9934"
     }
}

To make use of this data in your order confirmation email templates, refer to the following example and modify it to your needs according to mixin contents:

#if($!{d.order.customer.mixins} && $!{d.order.customer.mixins.secondaryContactPhone})
    #e($!{d.order.customer.mixins.secondaryContactPhone.number})
#end

Builder

Tue Mar 15 2016 00:00:00 GMT+0000 (UTC)

Organizations moved

For easier handling and usability, organizations have been moved from My Account > My Profile > Organizations to the Builder. All organizations are now under [Organization Choser] > Manage Organizations. If you click Manage Organizations, you will be redirected to the Organizations Overview and will see all of the organzations that you have permissions to manage. You can click on any organization to see its organization details, billing preferences, and billing history.

You can also navigate to a particular organization and manage it from the Builder home page. If you are a direct member of an organization and have permissions to manage it, the organization's name displays as a blue link in the title bar. If you click on it, you will be forwarded to the organization details page.

If you do not have access to a particular organization, then you will see its name as simple text in the title bar:

There are more changes and improvements on the way, so check back soon for the latest updates!

Media v2

Wed Mar 09 2016 00:00:00 GMT+0000 (UTC)

New Features

New functionality to delete multiple files belonging to a given tenant.

The delete functionality has been extended to enable removal of multiple files with a single request. Deleting by query enables you to remove files that have metadata that matches a given query. The metadata query syntax for this operation is the same as for a filter operation. The deletion operation may be performed on both the public and private media files of a particular tenant.

Service SDK 4.7.0

Fri Mar 04 2016 00:00:00 GMT+0000 (UTC)

HTTP error response callbacks for generated clients

The generate-client goal of the generator plug-in is generating even more code now. For each error HTTP response that was defined in RAML, it will generate an on- method to register a callback, for example onInternalServerError. This feature has the benefit of allowing you to shorten your code significantly. However, old code will continue to be supported in the same way with the new Ramler version, so no changes are required.

Bug fixes and improvements

The SDK Maven Archetype now only generates one common Spring context to ensure consistency between the generated Jersey tests and the actual service. The generated Cloud Foundry deployment configuration cf-manifest.yml has been renamed to the Cloud Foundry's default manifest.yml. The default URL of the authorization endpoint has been updated to point to the latest version of the OAuth2 service.

References to Riemann's URL have been removed from the Service SDK documentation. The monitoring library of the Service SDK is supposed to be used with its own instance of Riemann. The library will always expect the Riemann URL to be provided.

The default log format now also accepts the application instance as an integer. Previously, it only accepted string values.

An "eager token expiration" feature was added in the authorization library, which causes the token to be refreshed five seconds before its expiration in order to compensate for possible network lag and to prevent the usage of an expired token.

A bug was fixed in service generation that was causing missing imports in DTOs created for specific JSON type formats.

Product v2

Fri Mar 04 2016 00:00:00 GMT+0000 (UTC)

We are pleased to announce the release of Product Service v2 which introduces new functionality and improvements.

For this release, we have introduced features that allow you to use our service for more general and simpler purposes.

New Features and Functionality

Our most important goal for this release was simplifying the user experience. In doing so, we have introduced following improvements:

Media enhancements

Automatic media reorder when creating/updating your product's media.

Prior to this release, you were on your own with media ordering, for example, when you added media to the product in any other position than the last, you had to recalculate the position of all other media in this product. This made it difficult to use. In this release, when you are creating or updating media, you no longer have to manually manage its position in the media's collection. The service now automatically places it in the appropriate position and reorder the rest of your media respectively. For more information about this functionality, see Media Tutorial.

If you were previously managing your media collection's order manually, you will need to use (just once) our Migration service to migrate your media's order to the format used with the Product Service v2.

New media endpoint

To be compliant with Media Repository v2, we changed how to add media to products. This change was necessary because the Media Repository service v2 moved storage to an external service (AWS S3 Bucket). In addition, this change gives you the ability to define a 'Content-Type' header for the uploaded media. This value is respected when fetching media with the returned media's link (with the Product Service v1, you received 'binary/octet-stream' 'Content-Type' header). For more information about this change in the Product service, see Media Tutorial

Removing external media support.

For security reasons we have removed external media support. It will no longer fetch, create, or update the media, so all external media created is not visible. For more information about external media support, see Media Tutorial

Product management

Rename field 'sku' to 'code'.

The SKU (Stock Keeping Unit) is just one of many other product's identifier types, such as UPC, EAN, GTN, and so forth. Not all products have to be connected with inventory. We want you to be able to use the Product service for more than shops, for example, the YaaS Market or the YaaS blog. We were looking for another word for a user-managed identifier. We chose 'code' as it is more general than 'sku'. As of this release, every product must have a 'code' value and it must be unique for a single tenant. The code is not automatically generated for you, because one of the code considerations was human-readability.

Optimistic locking feature

To allow you to safely manage your products, we introduced an optimistic locking mechanism. Now with every update, you can provide the version metadata value that you received when you fetched that product. The service ensures that the version you provided matches the version stored in the database. If it does not match, someone has updated your product in the meantime. For more information about the optimistic locking feature, see the Optimistic Locking Tutorial

No strict validation for product's attributes.

In this release, additional attributes that are not supported by the Product service are simply ignored when provided instead of generating an error.

Partial put improvements.

We improved the partial update function to include the possibility to add or remove single elements of the product's collections. With the Product Service v1, you had to provide a full collection even if you wanted to simply add a new element to it. In this release, adding or removing additional translations in the localization map is simpler than ever before. For more information about partial update improvements, see the Partial Update Tutorial

Localization

Removing default language support

In the previous version of the Product service, if you did not provide 'Content-Language' or 'Accept-Language' headers, the service assumed that the content you were working on was in English. As we want you to be more aware of how your data are treated, we removed that assumption. Now, if you are providing data without localization, the service requires that you provide a 'Content-Language' header. If you're fetching data, and you provide 'hybris-languages' header or do not provide a 'Accept-Language' header, you will receive a full map of localization values. For more information about language support, see Localization Tutorial

Migration

'SKU' field's Migration (no action required)

We have added a field named 'code' to all your products with 'sku' as the value. In the previous release, the introduced the mapping mechanism that was updating both fields simultaneously. Now, using the Product service, you will notice that the values from your 'sku' field are now visible in the field 'code'.

Media reorder migration (possible action required)

In this release, we introduced a new tool called the Migration Service. The purpose of the tool is to migrate your media collection order. The tool reorders your media to the format supported by this release of the Product service, taking into consideration the media's position attribute and the main flag. Note that the main flag has the higher priority than any position value. If you were ordering your media with the Product Service v1 make sure you trigger it after you have finished using it and before you start using Product Service v2. For more information about the media reorder migration too, see Product Service v2 Media Migration Tutorial

Order v1

Wed Mar 02 2016 00:00:00 GMT+0000 (UTC)

Measurement units

With this release, a checkout client can post and customer/merchant can see measurement units for order line items. A measurement unit consists of a numeric value and a unit. It describes how much of a product is ordered when a customer puts quantity=1 of this product in their cart. For example:

"measurementUnit": {
  "value": 1,
  "unit" "m"
}

"measurementUnit": {
  "value": 2,
  "unit" "kg"
}

Only value is a required field. If unit is not provided, it will be interpreted as 1 piece.

The schema of the measurementUnit is a common quantitative-value schema, which you can find here: schema-quantitative-value

You can make use of this data and present it to your users. If you would like to update your order confirmation email templates and include this information in the order line items section, you can add the following code to your email template and customize the styling to your needs:

#if($!{entry.measurementUnit} && $!{entry.measurementUnit.value})
   <span style="color: #3c3c3c; padding-bottom: 10px;">
       #e($!{entry.measurementUnit.value})#e($!{entry.measurementUnit.unit}) per package
   </span><br/>
#end

Please note that this will only work if the order is placed using a checkout service that passes this information correctly to the Order service. The YaaS Checkout service does not support this yet, but it will be introduced soon.

Exposing the RAML API descriptor at the fixed URL

The Order service now exposes the RAML API descriptor at the 'meta-data/api.raml' relative URL. This makes the service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. Although the API descriptor is also served at the previous URL for backwards compatibility, existing Order service API consumers should update to the latest URL.

Customer v1

Wed Mar 02 2016 00:00:00 GMT+0000 (UTC)

Exposing RAML API descriptor at the fixed URL

The Customer service now exposes the RAML API descriptor at the 'meta-data/api.raml' relative URL. This makes the service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. Although the API descriptor is also served at the previous URL for backwards compatibility, existing Customer service API consumers should update to the latest URL.

Dev Portal

Wed Mar 02 2016 00:00:00 GMT+0000 (UTC)

Previously, the Feedback modal was not displaying properly in Internet Explorer (IE). When the user selected the link, the entire page grayed out and became unresponsive. This was caused by a Bootstrap issue. We fixed the issue, and the design is now consistent across all browsers.

Site v1

Wed Mar 02 2016 00:00:00 GMT+0000 (UTC)

Exposing RAML API descriptor at the fixed URL

The Site service now exposes the RAML API descriptor at the 'meta-data/api.raml' relative URL. This makes the service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. Although the API descriptor is also served at the previous URL for backwards compatibility, existing Site service API consumers should update to the latest URL.

Document v1

Tue Mar 01 2016 00:00:00 GMT+0000 (UTC)

New Features

Single token for many requests

Going forward, you can get one access token for your team and use it to perform many requests for many tenants. You can now use query parameter {tenant} to specify for which tenant you want to run the operation. The main advantages of this solution are:

Easier development of multi-tenant services.
Reduced number of calls to the OAuth service, and therefore reduced latency.
Reduced token cache size.

Get a list of all tenants for a client

To improve development and management of multi-tenant services, a new function to list of all tenants for a given client is introduced. You can now use simple GET method on the /all endpoint to retrieve this list.

Extended delete function to delete all service data for tenant, and a new hybris.media_admin scope

The delete functionality has been extended to enable you to delete all tenant data with just one call. This is a useful feature if you want to perform a cleanup after testing. You can trigger the deletion of all tenant data by using the DELETE method on the /{tenant}/{client}/ endpoint. To prevent the unintentional removal of service data, a new hybris.document_admin scope has been added.

Media v2

Tue Mar 01 2016 00:00:00 GMT+0000 (UTC)

New Features

Single token for many requests

Going forward, you can get one access token for your team and use it to perform many commits for many tenants. The /commit endpoint allows you to use query parameter {tenant} to specify which tenant should be the owner of the media file. The main advantages of this solution are:

Easier development of multi-tenant services.
Reduced number of calls to the OAuth service, and therefore reduced latency.
Reduced token cache size.

New functionality to delete all tenant media files, and a new hybris.media_admin scope

The delete functionality has been extended to enable you to delete all tenant media files with just one call. This is a useful feature if you want to perform a cleanup after testing. You can trigger the deletion of all media files stored for a particular tenant by using the DELETE method on the /files or public/files endpoints. To prevent the unintentional removal of a huge number of media files, a new hybris.media_admin scope has been added.

Customer v1

Tue Mar 01 2016 00:00:00 GMT+0000 (UTC)

Customers can change their own login email address. For more information, see the Customer service documentation in the Dev Portal.

Engagement Center UI Configuration v1

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

Enhanced configuration retrieval and required updates to support YaaS enhancements

This release of the Engagement Center UI Configuration service provides new options for retrieving Engagement Center configurations and module definition. To support the new Media Service version, you may need to re-upload any images you previously uploaded for the Engagement Center UI Configuration service. Additionally, upgrades for Cloud Foundry require users of the Engagement Center UI Configuration service to update application URLs.

Retrieve default configurations and module definitions

In this release, the Engagement Center UI Configuration service offers these new capabilities:

Retrieve the default configuration data for tiles, modules, business document types, action area views, header area views, work area views, and required scopes.
In addition to retrieving business context configuration data, you can now use the endpoint businessContextConfig to retrieve module definitions.

Media Repository service version 2 requires re-upload

Version 2 of the Media Repository service is now available. Because version 1 and Version 2 of the Media Repository service use different backends, there is no integration between them. The Engagement Center UI Configuration service uses version 2, only. This means that the service can no longer show any images uploaded previously, using version 1. To show images, you must upload any company logos and background images again.

Update required for Engagement Center UI view URLs

Because all Engagement Center UI views are now deployed to the new Cloud Foundry domain, all view URLs changed. This means that to use the Engagement Center package, you must adapt your application URLs using these steps:

Create a new application.
Select these scopes for your tenant:
- hybris.cecenteruiconfig_view
- hybris.cecenteruiconfig_manage
- hybris.cecenteruiconfig_customer_engage
- hybris.cecenteruiconfig_ticket_backoffice
Use the Client ID and Client Secret for your new application to get an access token from the OAuth2 service.
Select these scope for your tenant so you can delete stored configurations from the Engagement Center UI Configuration service:
- hybris.cecenteruiconfig_view
- hybris.cecenteruiconfig_manage
- hybris.cecenteruiconfig_customer_engage
- hybris.cecenteruiconfig_ticket_backoffice
Get an access token from the OAuth2 service.
In the Engagement Center UI Configuration service's API console, delete these stored configuration data points:
- tilesConfig
- moduleDefinitions
- businessDocumentTypes
Sign in as an Engagement Center administrator to the Builder UI for your tenant.
Initialize these configurations:
- tilesConfig
- moduleDefinitions
- businessDocumentTypes
In all of your application’s redirect URLs, replace hybris-cecenter-agenthome-ui-v1.us-east.cf.yaas.io with cecenter.yaas.io.

Social Media Retrieval Scheduling v1

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

The Social Media Retrieval Scheduling service is a mashup service that provides the functionality to schedule background jobs, which periodically (every 30 minutes) retrieve social media posts from configured social media channels.

Before using this service, make sure the services for harvesting data from target social media channels have been implemented and correctly configured. You can refer to SAP Jam Communities as an example.

You need to create one background job for each target social media channel and configure the endpoint, which can be called to harvest data from this social media channel.

In order to generate a proper token to call the configured social media data harvesting endpoint, an application needs to be created in your project and the Client ID and Client Secret of this application need to be configured in a background job.

Using this service, you can:

Configure the background job for the target social media channels.
Automatically start the background jobs, which periodically run to harvest social media posts.

Engagement Center Customer v1

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

The Engagement Center Customer service now supports address mixins. For more information about the mixin concept, refer to the topic Mixins.

Engagement Center Search v1

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

The Engagement Center Search mashup service now supports the sort and from query parameters for these endpoints:

/{tenant}/customer/search
/{tenant}/transaction/search
/{tenant}/product/search
/{tenant}/salesOrder/search
/{tenant}/serviceTicket/search

Use the sort parameter to sort results by field. Use the from query parameter to define the starting index of your search results.

For more information, see the EngagementCenterSearch service documentation.

Builder

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

Included in these release notes are the following new features and improvements:

Information about limits available on all levels
Image upload on COIN view improved
Base path changed to YaaS URL

Information about limits available on all levels

We previously announced limits on the number of organizations, teams, and projects that were introduced to prevent excessive creation of objects. Since only five teams and five projects/sites can be created within each organization, notifications have been added not only on the organization level, but also on the overview pages for Dev Teams and Projects & Sites.

On the Builder overview page, only those dev teams and projects/sites of which a user is a member are displayed. This means that someone who does not have permissions to add a team or project will only see the teams and projects of which they are a member, and the +ADD button is not displayed:

If a user has the appropriate permissions to create teams and projects, the +ADD button displays as long as the limit within the organization has not been reached. For example, since each organization can have a maximum of five projects/sites, the +Add New Project/Site button will no longer be displayed after five projects/sites have been created.

Image upload on COIN view improved

The error that displayed on the COIN view during System Demo 12 was resolved.

A notification was added about the size and format restrictions for image uploads. The image size must be 408 x 362 pixels, and the image must be in JPG or PNG format:

Additionally, if a showcase was created in the background (even with errors), the page gets refreshed and you can then see and use the additional actions buttons.

Base path changed to YaaS URL

Since the principle of the base path was confusing to many users, it has been reworked and renamed. The base path, which is the location where all your services and modules will be stored, is now called YaaS URL and mandatory during the organization creation process:

The YaaS URL is located on the organization details page where the base path could be found before.

Currently, the YaaS URL is verified during the approval process for US companies. (For non-US companies, it only checks whether the path already exists.) The YaaS URL can only be set by the organization owner, and once it is set, it cannot be changed.

There are more changes and improvements on the way, so check back here for the latest updates soon!

ERP SD Configuration v1

Mon Feb 29 2016 00:00:00 GMT+0000 (UTC)

New endpoints for managing multiple sales areas, reference customers, and document types

The service now introduces new endpoints for managing multiple instances for the following data:

Sales organization
Distribution channel
Division
Sales area
Reference customer
Transaction document type

Commerce Builder Module v0.2.14

Thu Feb 25 2016 00:00:00 GMT+0000 (UTC)

Customer Settings

In this release, a new field 'Email Reset URL' is available. Merchants can specify here an email reset URL used for confirmation of email login changes made by a customer.

More information can be found at Customer documentation.

Improvements in Coupon listing page and information on site cards

Improvements have been made to the start and end date fields in coupon listing page. If no end date is set for a coupon, 'No end' is displayed. Additionally, the order of the listed sites starts now with the default site, followed by the rest of the sites in alphabetical order. Some improvements were also made to the information shown on site cards.

Cart v1

Tue Feb 23 2016 00:00:00 GMT+0000 (UTC)

Add multiple items to the cart in a single call

You can now added multiple items to the cart in a single call. This new feature uses the batch processing guidelines from the API Best Practices. This feature benefits a customer who frequently shops at your store. If a customer makes frequent orders from you store and always orders the same items, they do not have to go through the long process of adding items one at a time. For more information about this feature, see Add Multiple Items to the Cart in a Single Call.

Exposing RAML API descriptor at the fixed URL

The Cart service now exposes the RAML API descriptor at the meta-data/api.raml relative URL. This makes the Cart service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. This change has zero impact for existing API consumers, but if you are referring to the Cart service RAML file, you must use the latest URL.

Bug fixes

Now when you add an item to the cart, the price is stored as is (regardless of the decimal point) until calculation. After the cart is calculated, rounding is applied.

hybris techne v1.1.0

Fri Feb 12 2016 00:00:00 GMT+0000 (UTC)

Techne v1.1.0

Updates

Updated style for required field indicator

Updated list management interaction design to improve usability

Updated label status class to correct status color display

Updated Tool Tips vs. Pop Over usage guidelines and classes

Updated placement of help icon to allow for proper scaling and layout across devices

Updated style to better visuals indicate inactive cards

Updated validation styling

Other minor styling improvements across components

Updated techne.yaas.io/gettingstarted.html to ensure all materials are in sync

Dev Portal

Fri Feb 12 2016 00:00:00 GMT+0000 (UTC)

Thanks to the community feedback we realized that code blocks in documentation were not displayed properly. They had an extra space above the code, which simply wasn't looking good. We fixed this issue.

Schema v1

Thu Feb 11 2016 00:00:00 GMT+0000 (UTC)

Ability to store metadata with a schema in the Schema service

You can now add and manage additional metadata about a schema in the form of simple key-value pairs (where values are strings) along with a schema in the Schema service using the new {tenant}/{schemaId}/metadata endpoint. Schemas stored in the Schema service are immutable by design and cannot be changed. This new feature enables you to store and update additional information about your schema, such as its title, description, or other information, without creating a new version of the JSON schema. You can update (fully replace) your schema metadata at any time with a single PUT on {tenant}/{schemaId}/metadata. You can filter your schemas using metadata and use paging and sorting in the results. For more information, see the Schema documentation.

Builder

Thu Feb 11 2016 00:00:00 GMT+0000 (UTC)

Included in these release notes are the following new features:

Improved list of subscriptions
Event topics for services and applications
Visibility of nodes
New improvements on organization level
- Consumption Data
- Visibility of Projects and Teams
- Limit of organizations, teams and projects

Improved list of subscriptions

We improved how the lists of subscriptions are displayed in teams and projects/sites. Previously, it was just an unsorted amount of cards. These are now separated into two sections: ACTIVE and EXPIRED.

If you unsubscribe from a package, it will remain in the active section until the expiration date and then will be automatically moved to the expired section.

Event topics for services and applications

In Projects/Sites > Applications, you can now define topics for the events that are calling the API. On the Application Details page, scroll down to the bottom to see the topics. You cann add topics by clicking the +TOPIC button.

For more information on topics, please see the PubSub documentation.

Visibility of nodes

With this release we're introducing the Customization section for projects. As a project owner/manager you now can decide which nodes can be seen by the members of your project, and which not. This is only valid for those nodes that come as Builder modules with packages you subscribe to and are added as visible by default to the left navigation area. Go to [Your Project] > Administration > Customization to turn them on and off.

New improvements on organization level

Consumption Data
As an organization owner, you can see the consumption data of your teams and projects without being a member of those teams/projects and without entering them in the Builder. To do this, go to your organization and then to the Bills tab in the left navigation area. You will see the monthly overview of your charges. By clicking on any month, you can drill down to the list of all the teams and projects within your organization that are subscribed to packages and therefore produce costs for your organization. By clicking on a particular team or project, you can see the list of all packages to which this team/project is subscribed. You can see the used rate plan and the costs for this package for this team/project. You can click on the package to see the usage of metrics and the complete consumption of this project/team for this subscription:
Visibility of Projects and Teams
You can see all the teams and projects/sites that are created in your organization by navigating to Administration > Dev Teams & Projects/Sites

If you are not a member of a team or project, you can still see them all as an organization owner (or assigned to the organizaiton owner role) but not be able to enter them from within the organization. As a member of a team or project/site, you can click on one and navigate to the according team or project.
Limit of organizations, teams and projects
To prevent excessive creation of objects, new limits for organizations, teams, and projects have been introduced. From now on, only two organizations can be created from each YaaS account, and five teams and five projects/sites can be created within each organization.

Once the limit is reached, the user with the role that allows you to create teams/projects will not see the +ADD button anymore.

There are more changes and improvements on the way, so check back here for the latest updates soon!

Loyalty iBeacon v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

Introduced in iOS 7, iBeacon is a new technology enabling new location awareness possibilities for apps. Leveraging Bluetooth Low Energy (BLE), a device with iBeacon technology can be used to establish a region around an object. The UUID, major and minor values provide the identifying information for the iBeacon.

The UUID, major and minor values provide the identifying information for the iBeacon. Generally speaking, this information is hierarchical in nature with the major and minor fields allowing for subdivision of the identity established by the UUID.

For example, the values may be used for a nationwide retail store. The UUID is shared by all locations. This allows an iOS device to use a single identifier to recognize any of the stores with a single region. Each specific store, New York, Washington, and San Francisco, is then assigned a unique major value, allowing a device to identify which specific store it is in. Within each individual store, departments are given separate minor values, although these are the same across stores to make it easier for an app on a device to readily identify departments.

Using this information, an iOS device can identify when it has entered or left one of the stores, which specific store it is, and what department the user might be standing in. These values are determined by the person or organization deploying the beacon device. UUIDs, major and minor values are not registered with Apple.

The Loyalty iBeacon microservice maps the UUID, majors and minors to human readable descriptions so that these values can be reused in other areas. This master data of beacons can then be used in wide variety of use cases. For example, a Marketer can make a combination of UUID, Major and Minor using the mapped descriptions in the iBeacon Management microservice and associate it with an offer. When a mobile app come in range of an iBeacon, appropriate offers can then be pushed to the device.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty iBeacon service are:

sap.loyibeacon_view - View iBeacon information
sap.loyibeacon_manage - Manage or edit iBeacon information
sap.loyibeacon_delete - Delete iBeacon information

Loyalty Offer v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Offer service allows you to create an offer in SAP Hybris Loyalty after coupon details, iBeacon details, and geofence details are provided. Once these coupons are created in the system, based on the certain attributes (iBeacon/geofence) information, notifications are sent to users with offer details. The following two types of offers are:

Push offer - Email is sent to a customer with an offer code when a particular condition is met.
Pull offer - Mobile app will request for valid offers for customers when they hit the specified Geofence radius.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Offer service are:

sap.loyoffer_view - View offer information
sap.loyoffer_manage - Manage or edit offer information
sap.loyoffer_delete - Delete offer information

Loyalty Geofence v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

Geofencing is a technology that defines a virtual boundary around a real world geographical area. A radius of interest is established that can trigger an action on a geo-enabled mobile device.

The Loyalty Geofence service allows an administrator to set up triggers so when a device enters (or exits) the boundaries defined by the administrator, a text message or email alert is sent. The technology has many practical uses. For example, a marketer can geofence a retail store in a mall and send a coupon to a customer who has downloaded a particular mobile app when the customer (and his smartphone) crosses the boundary.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Geofence service are:

sap.loygeofence_view - View Geofence configuration
sap.loygeofence_manage - Manage or edit Geofence configuration
sap.loygeofence_delete - Delete Geofence configuration

Loyalty Email v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Email service enables you to create and upload email templates so that you can send repetitive emails by making a simple REST call. You can send emails to intimate your customers of activities such as:

Successful registration
Order confirmation
Account expiration
Referral emails
Tier upgradation
Offers

These types of emails are sent to one person as a result of an action triggered by the user. You can create and manage email templates for any use case.

Examples:

Send a registration email to a customer when they register to the loyalty program.
Send an order confirmation email to a customer that lists their order details.
Send a referral email to friends for registering to the loyalty program.
Send an email to a customer when they upgrade their tier. For example, when a customer upgrades from the bronze to silver tier.
Send an email to a customer to inform about account expiration.
Send an email to a customer to inform about offers on any product.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Email service are:

sap.loyemail_view - View authorization for Loyalty Email service
sap.loyemail_manage - Create and update authorization for Loyalty Email service
sap.loyemail_delete - Delete authorization for Loyalty Email service

Loyalty Cards v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Cards service enables you to design templates for your digital loyalty cards and coupons, and offer them as part of your loyalty program.

The Loyalty Cards service allows you to create digital loyalty card and coupon templates for Apple and Google wallets.

A Loyalty administrator can configure cards and coupons for Apple and/or Google wallets from Configuration > Wallet Configuration menu.

Scopes prevent unauthorized access to loyalty micro services. The accepted scopes for Loyalty Cards service are:

sap.loycard_view - View Google and Apple loyalty card and coupon templates
sap.loycard_manage - Create or edit Google and Apple loyalty card and coupon templates

Note: Deletion of template for digital loyalty cards and coupons is currently not supported.

Loyalty Apple Wallet v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Apple Wallet service will enable you to download and update loyalty card and coupon passes on supported iOS devices.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Apple Wallet service are:

sap.applewallet_view - View Apple loyalty card and coupon configuration for Apple Wallet
sap.applewallet_manage - Manage or edit Apple loyalty card and coupon configuration for Apple Wallet

Loyalty Analytics v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Loyalty Analytics service is now open beta.

Features

Embedded Analytics within SAP hybris Marketing Loyalty (Beta) enables Marketers or Analysts to define their own set of KPIs to analyze how their loyalty program is performing.

In YaaS Builder, the Analytics tab in SAP hybris Marketing Loyalty (Beta) loads the Analytics dashboard that contains the following loyalty KPIs and charts:

Loyalty KPIs:

Members: Total number of members who have signed up for the loyalty program
Member Activities: Total number of member activities
Member Revenue: Total revenue generated from loyalty program members
Points Accrued: Total loyalty points accrued by loyalty program members
Points Redeemed: Total loyalty points redeemed by loyalty program members
Active Offers: Total offers active for the loyalty program
Redeemable Points: Total points available to redeem for the loyalty members

Loyalty Charts:

Members by Tier ( Pie Chart)
Members by Month / Qtr / Year per Tier
Member Activities by Month / Qtr / Year per Tier
Member Revenue ($) by Month / Qtr / Year per Tier

A Marketer can filter these KPIs and charts based on the time period and tiers configured for the loyalty program. Only predefined KPIs are displayed. There is no option for Marketers to create their own KPIs and charts. A Marketer can hide or unhide the KPIs based on his requirements.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scope for Analytics is sap.loyanalytics_view, which allows a user to view the KPIs and charts in Analytics tab of SAP hybris Marketing Loyalty (Beta).

Loyalty Configuration v1

Wed Feb 10 2016 00:00:00 GMT+0000 (UTC)

Loyalty Configuration service is now open beta.

Features

The Loyalty Configuration service is a core service that is used for configuring loyalty program setup, points to currency ratios, and customer advocacy.

Using this service, you can:

Create the loyalty program.
Add tiers for the loyalty program such as Bronze, Silver, Gold.
Select one of the commerce platforms: hybris Commerce Suite or hybris Commerce as a Service.
Show or hide reward information
Show cash balance instead of points
Configure points to currency ratio
Configure customer advocacy

In YaaS Builder, choose the Configuration tab in SAP hybris Marketing Loyalty (Beta) to perform the loyalty program configuration tasks.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for configuration service are:

sap.loyconfig_view - View authorization for Loyalty Configuration service
sap.loyconfig_manage - Create and update authorization for Loyalty Configuration service
sap.loyconfig_delete - Delete authorization for Loyalty Configuration service

Checkout v1

Tue Feb 09 2016 00:00:00 GMT+0000 (UTC)

The Checkout service supports customer information and address mixins

The Checkout service now supports the customer's information and address mixins and passes them to the Order service. These mixins come from the Customer service.

Configuration v1

Thu Feb 04 2016 00:00:00 GMT+0000 (UTC)

Exposing RAML API descriptor at the fixed URL

The Configuration service now exposes the RAML API descriptor at the 'meta-data/api.raml' relative URL. This makes the Configuration service more accessible to potential API consumers, which can easily locate the API descriptor entry point by knowing the base URL. Although the API descriptor is also served at the previous URL for backwards compatibility, existing Configuration service API consumers should update to the latest URL.

Service SDK 4.6.1

Thu Feb 04 2016 00:00:00 GMT+0000 (UTC)

More secure exception mappers

From now on, all exception mappers in jersey-support module of the SDK that deal with exceptions coming from Jersey are no longer including the exception's message in the HTTP response body, instead static messages will be included. That assures that no internal system information will be leaked outside your service, as long as you are using our library. Do not worry about loosing the exception information, the exception will be now logged in every exception mapper.

If you are instantiating any of those exceptions manually with a message that you want to see in response body, you need to provide a custom exception together with an exception mapper for that case.

User in metric logs

We continue to improve metric logging in Service SDK. Now the current user can be included in every metric log. For more information, see the updated schema-log. In order to use this feature, the user property must be present in the MDC context.

Improved control over JSON serialization/deserialization

It is now possible to customize serialization and deserialization of JSON entities by configuring the JsonFeature included in the Service SDK. For example, you can now easily enable inclusion of empty value properties in serialization which is needed for a Jersey client which makes partial update requests.

Api Console security improvement

The Api Console library which can be embedded in your service, will now load only RAML files which reside underneath the service's base URL.

Support for exposing your service's RAML at the recommended fixed URL

The Service SDK now supports services which expose the RAML API definition at the 'meta-data/api.raml' relative URL. Exposing the RAML at a well-defined fixed URL which can be easily resolved relative to the base-URL of the service itself makes services more accessible to API consumers which would be then able to easily locate the service's API definition entry point.

As a result we have adjusted the Api-Console and the Service Generator to follow this convention by default and to locate the RAML file at the new fixed location instead of locating it by parsing the now deprecated api-listings.json file.

Artifacts created with the updated archetype will also automatically follow the convention.

Migration guide

To benefit from the advantages of following the fixed RAML URL convention, your service needs some adjustments.

For a Java service which used the previous SDK version you can follow these steps:

####Step 1: The Api-listings.json file has been deprecated and you need to move all information contained here to the Service Generator Plugin configuration.

In the project's pom.xml you need to locate the 'service-sdk-generator-maven-plugin' and update the configuration of the execution with the 'generate-service' goal.

replace

 <inputFolder>src/main/resources/api</inputFolder>

with

<inputFolder>src/main/webapp/meta-data</inputFolder>

####Step 2: Take values from the 'src/main/resources/api/api-listings.json and add them to the plugin configuration as follows:

Api-listings.json fields	Plugin configuration fields
namespace	outputApiTitle
packageName	outputPackageName
async	async

Example result:

<execution>
    <id>service-generation</id>
    <goals>
        <goal>generate-service</goal>
    </goals>
    <configuration>
        <outputPackageName>com.hybris.configuration.rest.resources</outputPackageName>
        <outputApiTitle>Configurationservice</outputApiTitle>
        <inputFolders>
            <inputFolder>src/main/webapp/meta-data</inputFolder>
            <inputFolder>target/hybris-api-dependencies</inputFolder>
        </inputFolders>
    </configuration>
</execution>

####Step 3: If there are several APIs defined in the api-listings.json you need to add an execution for each API defined in the api-listings.json file. For each execution make sure you update the 'outputPackageName', 'outputApiTitle', 'async' fields. (repeat step 1 and 2 for each API definition)

Important: Each exection needs to have a different 'id'.

####Step 4: Delete the api-listings.json files from the 'src/main/resources/api' directory

####Step 5: First step to expose the RAML and it's include files as static content is by moving/renaming the /src/main/resources/api folder to /src/main/webapp/meta-data

####Step 6: The main RAML file needs to be renamed to api.raml All secondary RAML files can keep their original name.

####Step 7: (optional but recommended) It is encouraged to follow certain conventions for structuring and naming the additional resources. According to these conventions, the following relative URL paths and file suffixes should be used:

Resource	Path	Suffix	Example
RAML API Definition	(See above.)	(See above.)	`meta-data/api.raml`
RAML Trait	`meta-data/traits/`	`.raml`	`meta-data/traits/colored.raml`
RAML Resource Type	`meta-data/resourceTypes/`	`.raml`	`meta-data/resourceTypes/items.raml`
RAML Security Scheme	`meta-data/securitySchemes/`	`.raml`	`meta-data/securitySchemes/oauth_2_0.raml`
JSON Schema	`meta-data/schemas/`	`.json`	`meta-data/schemas/thing.json`
Example Data	`meta-data/examples/`	`-example.json`	`meta-data/examples/thing-example.json`

####Step 8: Register the 'default' filter to 'serve' the new 'meta-data' folder and also register the SDK's Raml Rewriter filter by adding the following files to the web.xml:

    <!-- Add RAML rewriting to static RAML resources that are part of the service 
        meta-data -->
    <filter>
        <filter-name>ramlRewriterFilter</filter-name>
        <filter-class>com.sap.cloud.yaas.servicesdk.ramlrewriter.filter.RamlRewriterFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>ramlRewriterFilter</filter-name>
        <url-pattern>/meta-data/*</url-pattern>
    </filter-mapping>

    <!-- Make sure that static meta-data are being served normally -->
    <servlet-mapping>
        <servlet-name>default</servlet-name>
        <url-pattern>/meta-data/*</url-pattern>
    </servlet-mapping>

####Step 9: Rebuild the Maven project (mvn clean install)

Backwards compatibility

To mantain backwards compatibility and to give enough time to your service's consumers to update to the latest RAML URL you may adjust your service to expose the RAML API descriptor at both the current URL and the new fixed URL simultaneously by following these steps:

####Step 1: In web.xml, map the RamlRewriterFilter (and the default Servlet) to additional URL pattern /api-console/raml/*.

    <filter-mapping>
        <filter-name>ramlRewriterFilter</filter-name>
        <url-pattern>/meta-data/*</url-pattern>
        <url-pattern>/api-console/raml/*</url-pattern>
    </filter-mapping>

    <!-- Make sure that static meta-data are being served normally -->
    <servlet-mapping>
        <servlet-name>default</servlet-name>
        <url-pattern>/meta-data/*</url-pattern>
        <url-pattern>/api-console/raml/*</url-pattern>
    </servlet-mapping>

####Step 2: In pom.xml, make sure that the build copies all RAML API resources to the /api-console/raml/api/ directory in the WAR file and also renames api.raml to its service specific name. (make sure you replace 'YOUR_ORIGINAL_RAML_FILE_NAME_HERE' as appropiate.

<plugin>
    <artifactId>maven-antrun-plugin</artifactId>
    <executions>
        <execution>
            <id>package-raml-backward-compatibility</id>
            <goals>
                <goal>run</goal>
            </goals>
            <phase>prepare-package</phase>
            <configuration>
                <tasks>
                    <copy todir="${project.build.directory}/${project.build.finalName}/api-console/raml/api">
                        <fileset dir="src/main/webapp/meta-data" excludes="api.raml"/>
                    </copy>
                    <copy tofile="${project.build.directory}/${project.build.finalName}/api-console/raml/api/YOUR_ORIGINAL_RAML_FILE_NAME_HERE.raml"
                            file="src/main/webapp/meta-data/api.raml"/>
                </tasks>
            </configuration>
        </execution>
    </executions>
</plugin>

RAML Patterns 1.2.1

Thu Feb 04 2016 00:00:00 GMT+0000 (UTC)

Features

The SAP usage disclaimer has been added at the top of every pattern.

Bug fixes

Several small bugs were fixed in this release.

Commerce Builder Module v0.2.13

Thu Jan 28 2016 00:00:00 GMT+0000 (UTC)

With this release, you will be able to see some additional information on cards on listing pages under Commerce Settings. Site Settings cards now display information about the default site, and a site's language, currency, and in/active state, while Payment and Tax Settings cards display information about the service providers configured for the sites.

In addition, we have added two new fields on the Site Details page, which allows the merchant to specify a site URL and a product path. These parameters will be used to construct a redirect URL to the original Product Details page of a product made available to buy in social apps. The product URL will be exported along with other product details to Stripe Relay.

Also, for a product you can now add external images. Simply paste the external image link to the External Image URL field and save the product.

Additionally, in this new release, when creating and managing coupons user time zone is being used instead of GMT. Improvements were also made to shipping zones and methods.

Cart v1

Mon Jan 25 2016 00:00:00 GMT+0000 (UTC)

Support of mixins in cart items and products

To extend the use of mixins in the cart, you can now also apply mixins to individual cart items as well as the product attribute within the item. For more information, see Extend Cart Information and Create Cart with Mixins.

Checkout v1

Mon Jan 25 2016 00:00:00 GMT+0000 (UTC)

Checkout supports mixins for each cart item

The Cart service introduced mixin support at the cart item and product level. When the cart information is passed to the Checkout service, Checkout also supports the new mixin information.

Bug fixes

When a coupon is redeemed, the record now stores the customer ID.

Cart Calculation v1

Mon Jan 25 2016 00:00:00 GMT+0000 (UTC)

Bug fixes

Based on user feedback, the API Console link for Cart Calculation service is now fixed.

Dev Portal

Wed Jan 20 2016 00:00:00 GMT+0000 (UTC)

We'd like to share some details on what we've done recently to improve the Dev Portal.

Better glossary term usage indicator

To ensure that you can understand all the concepts described in the Dev Portal, we include definitions for certain terms in the form of tooltips. Previously, the tooltip indicators looked like normal hyperlinks. Based on your feedback, we changed the formatting of these indicators so that it is easier to differentiate links from tooltips at a glance.

You can also go to the Cart service documentation to see it in action.

In YaaS, we publish release notes not only for APIs, but also for our tools, such as the Builder or the Service SDK. This is why the left navigation in the Release Notes section did not have package filtering like the APIs section. You could filter only by APIs or Tools. Based on your feedback, we extended left navigation filtering. Now, after selecting APIs in the filter, you will see another Packages filter.

We are currently working on improving the style of the filters and extending the filtering functionality.

Custom error pages

Previously, if there was an error, a generic error page that said The page you have requested is still in the queue was displayed. Based on your feedback, we have changed this to make it more useful by adding several custom error pages that clearly describe what went wrong.

To see one of the error pages, click here.

Search for main titles enabled

The search in the Dev Portal now works for titles, so you can search for the title of a document even if you don't know which section it is in.

All of these improvements were introduced based on your feedback and requests. We hope to get more feedback from you. Just use the Feedback button whenever you want to share your thoughts.

Storefront Template v1.0.1

Tue Jan 19 2016 00:00:00 GMT+0000 (UTC)

Shipping rates improvements

With this release we have fixed some minor issues related to the shipping cost implementation.

Media v2

Fri Jan 15 2016 00:00:00 GMT+0000 (UTC)

With this release of the Media service, managing both private and public media files is easier than ever before!

Features

With the Media service version v2, you can do the following:

Upload all your media files easily with a temporary upload link you can pass to your client.
Delete all unwanted media.
Manage the file's metadata for improved clarity and arrangement.
Decide who can access your media by using these endpoints:
- /public/files - Files posted to this endpoint do not require a scope. Anyone can retrieve a file by sending GET request to /public/files/{fileid}.
- /files - Files posted to this endpoint require the hybris.media_view scope. All sensitive files, such as invoices, stored here are viewable only by you.
List and filter your media files quickly using a query with response pagination.

What's new

Compared to v1, the v2 Media service has the following added capabilities:

The file upload and download process is enhanced to improve scalability.
Two separate endpoints are provided for private and public files.
Filtering media files using basic query is now possible.
A new migration tool simplifies moving all your media to the new version with just one request. For more information, see Migration Manager.

Media v2

Tue Jan 12 2016 00:00:00 GMT+0000 (UTC)

Going forward, you can improve your Media service experience by caching data.

The benefits of caching are:

bandwidth reduction
shorter response times
resource savings

How it works

Each time you perform a GET request on these endpoints, the Media service provides an ETag (entity tag) for the media file you requested, and sends it in the response:

/public/files/{fileId}
/public/files/{fileId} with a query on a particular variant
/files/{fileId}
/files/{fileId} with a query on a particular variant

The ETag is always the same for a given file and, thanks to this identifier, you do not have to GET the payload multiple times for already-cached files. When you use the If-None-Match header in subsequent requests, you receive the 304 Not modified response from the service, without a payload.

If you send an incorrect ETag in the If-None-Match header, for example, the ETag for a master media file, when requesting a variant, the service returns the 200 response code, for private files - along with the payload and for public files with a redirect link.

To learn more, see the Caching section of the Media service documentation.

Coupon v1

Tue Jan 12 2016 00:00:00 GMT+0000 (UTC)

Features

Retrieving coupon details and redemption details on behalf of a customer

In addition to redeeming a coupon on behalf of a customer using the hybris.coupon_redeem_on_behalf scope, a seller or a client application can now also retrieve coupon details on behalf of a customer using the same scope when the customerNumber query parameter is provided with the request. The seller can also retrieve redemption details on behalf of a customer after a successful redemption using the same scope and providing the customerNumber query parameter.

Payload of the 'hybris.coupon_redemption' event

The payload of the hybris.coupon_redemption event has been extended with two new attributes: redemptionId and couponCode.

Builder

Fri Jan 08 2016 00:00:00 GMT+0000 (UTC)

There are many new features and exciting changes in the Builder. Included in these release notes are examples of how to do the following:

Create an organization
Get started with teams
Create a package
Test your package
Share with the community
Set up a project

Create an organization

If you are new to YaaS, you only see one option when you log into the Builder - a yellow button that enables you to create an organization. To start your own organization, proceed with the steps below. Otherwise, if you are invited to an existing team or a project, click on the link in the email you received to accept the invite.

Click on + NEW ORGANIZATION in the Organizations Overview window. Input your organization's legal name, the display name, and select the country where your company is located:

If you choose the United States, then you must also accept the Framework Agreement, since this is the only country that is able to subscribe to commercial packages on the YaaS Market. The approval process for your USA organization requires you to add business-relavant data using the step-by-step wizard. As shown below, set the base path, the company address, billing address (if different), a contact person responsible for the organization, and a payment method (at the moment credit cards only):

Once you complete this process and send the data for approval, the status is set to pending. You can not subscribe any packages during this phase until your organization is set to approved.Your organization needs to go through some background checks - this may take a couple of days. As soon as your organization is approved, an email is sent to the contact person, and the change is reflected in My Account > Organizations > [Your Organization], as shown in the example below:
Organizations from countries other than the United States can only subscribe to Beta packages, and therefore, do not need to sign any terms of use. If your organization is not located in the USA, then the approval process is really simple. Click the Get Approval button and input the base path, as shown in the example below. The base path is needed for all the services created within this organization as well as it will be displayed in URLs. SAP hybris reserves the right to change the base path if it is not conform with your organization. After you click the Save button, your organization is auto-approved, and you can subscribe to the Beta packages offered on the YaaS Market:

Once the approval process is complete, you can not modify or add any data regarding your organization.

To invite other members to your organization go to Administration > Organization Members and click on + NEW ORGANIZATION MEMBER. Enter the email address and role for the team member, then click on the Invite button:

The new member needs an account in YaaS and has access to your organization immediately.

Getting started with teams

If you have a role that is allowed to create teams and projects within an organization, the + NEW DEV TEAM button is visible in the Builder. Click on it, enter the information in the required fields as shown in the example below, and click on Create:

Some fields can be changed after creation, and some, such as the Identifier, can not be changed, so be careful when choosing one.
The newly created team is shown on the dashboard when you select the appropriate organization in the upper left corner. If you are a member of more than five teams and do not see the team you want to access on the dashboard, click on the Dev Teams button in the upper left navigation. A list of all your teams is displayed, ordered by teams you created and teams you are invited to join. Click on a particular team to see the details:
Within a team, you can register the services and Builder modules that you develop and deploy. You can also bundle them into packages, as seen in the next example, and sell them on the YaaS Market (in the future). Team members can be assigned a user role that is allowed to subscribe to packages - by default the creator and owners can do that -, developers on your team can use the services that are offered in those packages, and your services can call those subscribed-to services. The packages your team subscribes to is listed under the Subscriptions navigation node, and the usage data is on the subscription details page.
Under the User Roles navigation node, define different roles and then assign different team members to those roles. Click on the + NEW USER ROLE button, and enter the name and the description of the new user role. Choose which actions can be performed by a member of this role in the Scopes section, and click the Save button to create the new user role:

We recommend creating specific user roles for different tasks. The owner role is really powerful, as it allows to perform all actions on your team.

Invite users directly to this user role when you invite new team members to your organization, or go to Dev Team Members and click on + DEV TEAM MEMBER. Enter the email address and role for the team member, then click on the Invite button:

An invite is sent in an email to the new team member and they can access the team after they accept the invitation. You can see the invite in the Pending Invitations window until the invitation is accepted.

Create a package

A team's ultimate goal is to create packages and sell them on the YaaS Market. Publishing will only be available in the future, but you can already prepare and try your packages internally. To do so, go to [Your Dev Team] > Packages > + NEW PACKAGE, enter the name of the package, and click on the Save button.
On the package detail page, enrich your team's package with more services and Builder modules. In the Configuration tab, add these options to your package by clicking on the appropriate link and following the instructions, as shown in the example below:
If the service(s) you add to your package are using services that are not located in this package, then modify the required packages section as well. Add all the packages which contain those services that are called by your service.
In the PUBLISHING tab, add the Terms of Service as a PDF file or URL. These terms are acknowledged by anyone who subscribes to your package and uses it. Enter your company's web address, and a responsible person from your team who can be contacted by the YaaS Market operator in case questions arise:

You can also Whitelist teams and projects that can use your package without subscribing to it on the YaaS Market by entering the Team or Project ID in the appropriate field. Those teams or projects can add your package as a private package in the Subscriptions section.
In the MARKET CONTENT tab, provide all the necessary data to successfully market your package. The short description is used wherever your package appears in any list in the Builder. The long and technical descriptions are shown on the YaaS Market. Optionally, add some nice screen shots to entice your customers:
In the last tab, called PRICING, select the Package Type: Beta or Commercial. Define the Rate Plan which depends on the package type. For the Beta type, define the Metrics and the usage is blocked after the included quantity of units is used.

For the Commercial type, you can set a price for any additional usage. Once the included volume is consumed, payment is made for each additional quantity used, as defined.

Test your package in a test project

After you add at least one service to your package, the TEST button appears below the package details. To test a package before you publish it, make sure to add the following details:
- Add an icon
- Set a responsible person
- Define at least one metric
Then click the TEST button and provide the required data, such as the unique identifier of the test project:
Click on the Save button and a test project is created automatically. All team members are added as test project members, and a subscription is made between your package and the test project. Access the test project either on the package details page or under the Projects & Sites navigation node:
You can now start testing the functionality of your service(s) and Builder modules.

The YaaS Community is a place to showcase your projects and business applications to a broader audience. Click on the SHOWCASE button and review the information from your package, or make any desired changes, such as uploading a new icon.
Click on the Share & Save button and you own project space is created under the URL, https://community.yaas.io/.

Setting up a project

If you haven't been invited to a project, you can create one if your user role has the permissions to do so. If so, you see the + NEW PROJECT/SITE button, as seen in the example below. Enter the Display Name, Identifier (which cannot be changed later), and the Description. Then click the Save button:
You can invite other members to your project, and create user roles and assign them to different users. You can also subscribe to packages on the YaaS Market at the URL: https://market.yaas.io/. Or, if you are logged into the Builder and select to add packages, you are automatically forwarded to the YaaS Market within the context of your organization and project. Go to Administration > Subscription or click on the SUBSCRIBE TO PACKAGES button on the project details page, and then click on the + ADD PACKAGES button. You can choose from many packages on the YaaS Market.
The packages on the YaaS Market are divided into two categories, based on your company location:
- Standard – United States only
- Beta – Worldwide
The Standard packages are available only to US-based companies while the Beta packages are available to all other companies except for US. First, your organization must go through an approval process before subscribing to packages, as described in the example above.

Click on a package to see its details, and then subscribe to it by clicking on the SUBSCRIBE NOW button. If redirected from the Builder, your project or team information is preset in the window. Confirm the subscription is for the project listed, and then click on the SUBSCRIBE NOW button. You can subscribe to more packages, or click on the CONFIGURE IT button:
Once you're directed back to your project in the Builder, you'll see the navigation tree on the left has changed to reflect that each subscribed-to package containing a Builder module now has navigation nodes:

For example, the PRODUCT CONTENT package offers the possibility to create products and publish them in an online shop. After subscribing to this package, go to the Products tab in the Builder, and click the + ADD PRODUCT button. Enter all the product information and click on the Save button.

All of your created products are located in the Products tab, and you can sort by the newest, or alphabetically from A-Z, or from Z-A. When you subscribe to the Product Content package, an online shop is automatically created at the URL: http://shops.yaas.io/[Your-Project-Identifier]. The project identifier is located on the project details page. Every product set to Active on the product creation page or on the product details page in the Builder, appears in the online shop immediately:

As you can see, the Builder is a powerful tool that lets you do many things in YaaS. There are more changes and improvements on the way, so check back here for the latest updates soon!

Checkout v1

Wed Dec 16 2015 00:00:00 GMT+0000 (UTC)

Bug fixes

The Checkout service can successfully create an order even if the shipping detail is not configured in the Site service.

The checkout details can now be retrieved when the cart contains a composite mixin.

Engagement Center UI Configuration v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Use the new Engagement Center UI Configuration mashup service to configure the Engagement Center user interface (UI).

With this service, you can manage:

Tiles configuration
The logo and the background image of the Engagement Center home page
The UI layout of the Engagement Context in the Engagement Center, including action area views, business document types, header area views, and work area views
Required scopes that enable the Agent Home to acquire an access token
Modules configuration

Service Ticket Mashup v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Use the new Service Ticket Mashup service to track, work through, and provide resolution for customer issues in the Customer Engagement Center. You can alos configure service ticket types for the different types of service you provide, such as requests for repair and servicing, and general inquiries.

The Service Ticket Mashup service provides additional capabilities on top of the Service Ticket service, such as consistency checks for customer and product master data when creating or updating service tickets, and reading additional customer and product attributes when retrieving service tickets.

When you create a service ticket, you can specify the relevant information. For example:

A short description of the customer's issue or request
The customer for whom the service ticket was opened
The product that the reported request or issue is related to
The different classes of service tickets, for which you can configure the classes
Ticket priority and desired due date

When working on the resolution of a service ticket, you can use features such as:

Built-in status management
A transcript concept that allows processors of the tickets to enter additional information about the processing status
Automatic calculation of processing times

Service Ticket v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

When you create a service ticket, you can specify the relevant information. For example:

A short description of the customer's issue or request
The customer for whom the service ticket was opened
The product that the reported request or issue is related to
The different classes of service tickets, for which you can configure the classes
Ticket priority and desired due date

When working on the resolution of a service ticket, you can use features such as:

Built-in status management
A transcript concept that allows processors of the tickets to enter additional information about the processing status
Automatic calculation of processing times

You can also use the Service Ticket Mashup service to develop applications on top of service tickets. The Service Ticket Mashup service provides additional capabilities on top of the Service Ticket service, such as consistency checks for customer and product master data when creating or updating service tickets, and reading additional customer and product attributes when retrieving service tickets.

Recent Service Tickets v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Providing an overview of the service tickets that have most recently been updated

Service tickets enable you to track customer issues and work on those issues through to resolution.

The Recent Service Tickets service provides you with an overview of the service tickets that have most recently been updated. The list is separated into service tickets that are still open (in status OPEN or IN_PROCESS) and service tickets that are closed (in status COMPLETED or CONFIRMED).

Recent Sales Orders v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Retrieving recent sales orders of a customer

The Recent Sales Orders service is a mashup service that is used for retrieving the recent sales orders of a customer.

Using this service, you can:

Retrieve a list of sales orders. All the sales orders are returned in descending order of the time they were created.

Scopes prevent unauthorized access to the Recent Sales Orders service. The accepted scope for the Recent Sales Orders service is:

hybris.order_read - Read-only access to the Recent Sales Orders service

Loyalty Report v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Report Metadata service stores the metadata for KPI reports, which are displayed in the analytics dashboard of SAP Hybris Loyalty.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Report Metadata service are:

sap.loyreport_view - View authorization for Report Metadata
sap.loyreport_manage - Edit/Manage authorization for Report Metadata
sap.loyreport_delete - Delete authorization for Report Metadata

Engagement Center UI Logging v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Disclaimer

For reasons of data protection, SAP strongly recommends you not to log any sensitive data when you use the Engagement Center UI Logging service. SAP does not accept any liability for the use of the service by its customers.

Features

The Engagement Center UI Logging service is a business service that enables you to post log entries and record them in the YaaS logging system.

Using this service, you can:

Post messages or metrics, which conform to message format or metric format specifications.

Scopes prevent unauthorized access to the Engagement Center UI Logging service. The accepted scope for the Engagement Center UI Logging service is:

hybris.cecenteruilog - This scope is required to create log entries.

Engagement Center Search v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

The new Engagement Center Search service is a mashup service that allows you to search for these objects in the Engagement Center:

Customer
Product
Order
Service ticket

For more information, see the EngagementCenterSearch service documentation.

Interaction Log v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Using the new Interaction Log service, you can document each interaction that takes place between a customer and an agent in the Engagement Center by creating an interaction log item. An interaction log item contains information such as:

the customer and the agent that interacted with each other
the date and time the interaction took place
notes the agent took about the interaction
links to related objects such as service tickets and sales orders

The interaction log is a collected history of these interaction items.

By keeping this history and making it available to your agents, you can improve the efficiency of your customer interactions because every agent will have an overview of the interactions that previously occurred with a particular customer.

ERP SD Configuration v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Features

The ERP SD Configuration service is a mashup service that is used for handling SAP ERP SD integration configuration. Note that you are responsible for providing a valid SAP license and must insure that you are in compliance with SAP’s licensing policies.

Using this service, you can:

Create SAP ERP SD integration configuration data for connecting with the SAP ERP system.
Update stored SAP ERP SD integration configuration data.
Get stored SAP ERP SD integration configuration data.
Delete stored SAP ERP SD integration configuration data.

Scopes prevent unauthorized access to ERP SD configuration mashup service. The accepted scopes for ERP SD configuration mashup service are:

hybris.erpsdconfig_view - Provide read-only access to SAP ERP SD integration configuration.
hybris.erpsdconfig_manage - Create, update and delete SAP ERP SD integration configuration.

Engagement Center Indexing v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

The new Engagement Center Indexing service provides the functionality to perform initial data indexing and delta indexing for these business objects:

Customer
Order
Product
Service Ticket

When the initial indexing is complete, the service starts monitoring events from the PubSub service, and continuously performs delta indexing for all upcoming changes. Currently the service listens to these events:

hybris.customer.customer-signup
hybris.customer.customer-updated
hybris.order.order-created
hybris.product.product-created
hybris.product.product-updated
hybris.product.product-deleted
hybris.serviceticket.serviceticket-created
hybris.serviceticket.serviceticket-updated
hybris.serviceticket.serviceticket-deleted

Storefront Template v1.0.0

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Site Selector and Site Icon

With this release, the Site Selector has been moved from the footer to the header, where it's more available to the user. The merchant can choose to upload a Site Icon, e.g. a flag that will be displayed instead of the default globe that indicates the Site Selector. This way it's easy for the user to recognize, in the case of a flag, what regional site she is currently on.

Shipping Rates Implementation

The Storefront is now implemented with the new Shipping Service. On the product details page, the customer can click the "Shipping Info" link below the "Add to Cart" button to get information about all available shipping zones, methods, ranges and rates for the site.

The order total in cart is calculated with the minimum qualified shipping rate for the cart total, based on the default shipping zone of the site. User is given more shipping options to select from on the checkout page. The shipping service returns the options based on the "ship to" country selected in the address form and the available shipping options display in the Delivery Method drop-down, where user can select an alternative shipping method if wanted.

Further changes were made to checkout page to ensure that the buyer sees the final tax amount and shipping rate included in the order total before placing the order. To enable this, the cart was moved to display at the bottom of the checkout page, and to be hidden behind a "Preview Order" button. When the user has filled in the required address fields on the checkout page, the order can be previewed with the final order total. Storefront is calling the cart-calculation service directly with the complete shipping address in order to get this calculation returned. Clicking the "Preview Order" button displays the cart including order totals and user can fill in the payment details and place order.

Currently we have disabled the ability to edit cart and add coupon code on the checkout page, but this will be reintroduced shortly.

Loyalty Member v1

Tue Dec 15 2015 00:00:00 GMT+0000 (UTC)

Features

The Loyalty Member service allows you to:

Manage loyalty programs and tiers.
Manage loyalty member information such as user, status, tier, points, and registered on.
Manage member activity information such as registration, order, redeem, rating, review, and expiration.

Scopes prevent unauthorized access to Loyalty micro services. The accepted scopes for Loyalty Member service are:

sap.loycore_view - Enable view access for loyalty core services
sap.loycore_manage - Enable create and update access for loyalty core services
sap.loycore_delete - Enable delete access for loyalty core services

Cart Calculation v1

Mon Dec 14 2015 00:00:00 GMT+0000 (UTC)

New version of Cart Calculation service

Cart Calculation service v1 is now released.

Shipping v1

Fri Dec 11 2015 00:00:00 GMT+0000 (UTC)

Features

Shipping configuration for a site is automatically deleted when the site the configuration refers to is deleted by the Site service.

Site v1

Fri Dec 11 2015 00:00:00 GMT+0000 (UTC)

Updates

The hybris.site_settings_manage scope has been deprecated and is no longer supported. To manage site configuration, use the hybris.site_manage scope instead.

Checkout v1

Thu Dec 10 2015 00:00:00 GMT+0000 (UTC)

New shipping attribute

The Shipping service now has a new attribute (zoneId) that needs to be included in the shipping calculation. The Checkout service now uses the values from the method and zone ID attributes to calculate the order's shipping cost. For more information on shipping, see the Shipping documentation.

Commerce Builder Module v0.2.12

Tue Dec 08 2015 00:00:00 GMT+0000 (UTC)

Shipping Zone, Methods and Rates

You can now configure shipping zones per site, where one will be the default shipping zone. A shipping zone can have multiple shipping methods and these can again have multiple shipping rates for defined order total ranges. The shipping rates are set in the currency of the site. A shipping method can be made active or inactive, defining whether or not it will be available to the customer when checking out in the storefront. Shipping zones, methods and rates can also be edited or deleted.

This new shipping rate setup offers a lot of flexibility to the merchant when defining shipping rates that are both acceptable to his customers as well as supporting his business model.

Minified JavaScript

With this release, we have minified the module's JavaScript files in order to enhance the performance of the Commerce Builder Module.

Migration to v1

The Commerce Builder Module is now migrated to call v1 versions of all the services.

Document v1

Fri Dec 04 2015 00:00:00 GMT+0000 (UTC)

Improved protection for resources within projects

We have improved protection for resources in the Document service, as detailed in our blog post from November 24th. As a result of these changes, any requests with tokens issued with the Implicit Grant flow will now be rejected with an error code of 403. All resources are now protected with an additional security check. If you use the Implicit Grant or Resource Owner Password Credentials Grant flow to access services, you must change to the Client Credentials flow. This provides an additional level of security so that users who belong to a project/site but do not have Client Credentials cannot manipulate resources within the project/site.

Shipping v1

Thu Dec 03 2015 00:00:00 GMT+0000 (UTC)

Features

We are happy to announce the release of the brand new Shipping service, which will replace the existing Shipping Cost service, which will no longer be available after December 15, 2015. The new service goes beyond flat rate shipping cost and allows you to define multiple shipping zones, shipping methods and shipping fees for order subtotal ranges per site. This provides a much more flexible shipping cost setup that reflects the costs of shipping with different carriers in distinct regions. To learn more about what the Shipping Service offers, please visit Shipping Service documentation.

hybris techne v1.0.1

Wed Dec 02 2015 00:00:00 GMT+0000 (UTC)

Techne v1.0.1

Components

New Help and Validation

All help and validation components are now under one section. Also, new critical error avoidance guidelines and 'on-demand: help bubbles'.

Cards and Tables

We have added new rules and guidelines for how to use pagination and infinity scroll when working with cards and tables.

Notification Messages

Links have now a different styling when used in notification messages.

Patterns & Layouts

The Builder header has different areas for navigation, page name, edit page functionality, and primary interactions. techne now provides detailed rules for different scenarios to help you make the right decision on each page.

We have added examples of how Builder module navigation header and help and validation should be implemented.

Avalara Tax v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Avalara Tax service

Avalara Tax service v1 is now released.

Price v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Price service

Price service v1 is now released.

Stripe Payment v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Stripe Payment service

Stripe Payment service v1 is now released.

Checkout v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Checkout service

Checkout service v1 is now released and integrates with the v1 version of Cart service.

New shipping fee

The Checkout service now validates the shipping fee by checking to see that the shipping method (methodId) exists for a particular site and the shipping amount (amount) is valid for that method before it completes the checkout process.

Bug fixes

Checkout now returns a proper 400 error for an invalid ZIP Code in the payload.

Cart v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Cart service

Cart service v1 is now released and integrates with the v1 version of Shipping service.

New shipping fee

If there is a shipping fee applicable to the cart, the shipping attribute shows the amount and currency of the shipping cost.

Retrieving a cart without calculation details

You can now retrieve the cart details without completing the calculation using the new expandCalculation attribute. To retrieve a cart without the calculation details, set this attribute to false. By default, the attribute is set to true. For more information on the new attribute, see Retrieve cart details without calculation details.

Bug fixes

The error propagation logic in Cart service was fixed so that the Checkout service now returns a proper 400 error for an invalid ZIP Code in the payload.

Tax v1

Tue Dec 01 2015 00:00:00 GMT+0000 (UTC)

New version of Tax service

Tax service v1 is now released.

Loyalty Advocacy v1

Sun Nov 15 2015 00:00:00 GMT+0000 (UTC)

Features:

The Loyalty Advocacy service allows you to submit a rating for a particular product and submit a review comment for a particular product in a storefront. In the storefront, you can also view average user rating, list of all ratings and review comments, and total number of users who rated the product.

Scopes prevent unauthorized access to loyalty micro services. The accepted scopes for Loyalty Advocacy service are:

sap.loyadvocacy_manage - Create and update authorization for Loyalty Customer Advocacy service
sap.loyadvocacy_delete - Delete authorization for Loyalty Customer Advocacy service

hybris techne v1.0.0

Mon Nov 02 2015 00:00:00 GMT+0000 (UTC)

Techne v1.0.0

Welcome to techne v1.0.0 – our first official stable release for YaaS!

This release focused on overall stabilization of components, patterns and clear usage guidelines and documentation. The techne page itself under techne.yaas.io is aligned with the overall builder and YaaS design and we added a lot of new design examples and guideline updates on every page!

Guidelines

Visual System

Alerts, Errors & Notifications

Light Blue alert color is deprected.

System Errors

Generic System Errors

Added a new section for System Errors to provide user-friendly guidance on error content for more generic system erros.

Components

New navigation structure and much more documentated techne components with clear usage guidelines and recommendations

Alerts, Errors and Notifications

Updated usage guidelines on alerts, errors and notifications on the components page. We limited know the amount of available colors for this pattern.

Buttons

We wrapped the buttons section and added a documentation for the add-something-to-a-list button

Contextual Menu

Documentation and guidelines for the “more” contextual menu to ise on cards and tables.

Radio and Checkboxes not depricated!

Custom radio and checkboxes will stay in techne.

Modal boxes for dialogs

Guidelines and documentation on modal boxes.

Page Header

Redesigned component and clear guidlines for a mobile first techne page-header.

Pagination component

Redesigned component for pagination with documentation and guidelines.

Product Thumbnails

Component for displaying products. This replaces the thumbnail component.

Tables

New mobile table drop behaviour for tables with interactions and/or avatars.

Tour Bubble

Guidelines and documentation on the tour bubble.

Trees

Reintroducing trees with design update.

Patterns & Layouts

Updated visual reference examples of how to combine techne components to design usable, intuitive consumer-grade YaaS tools. Updated overall styleguide.

Cards

Guidelines on icon shapes to you use on cards and tables.

Thank you everyone for participating and helping us to make this first major release happen.

There will be more in the future, stay tuned.

Search v1

Tue Jun 30 2015 00:00:00 GMT+0000 (UTC)

From now on, Elasticsearch version 1.6 provides backup for the Search service and offers full text search and matching. You can set the field as analyzed to have Elasticsearch apply tokenization of strings for full text search. Do not use analyzed fields when using terms and/or filters in your queries. In those cases, set those fields to not-analyzed.

Release Notes | YaaS Dev Portal

Builder

New General Data Protection Regulation views

hybris techne v1.5.9

Patch Release

Service SDK 4.17.1

Dependency updates

Resolved issues

hybris techne v1.5.8

Patch Release

hybris techne v1.5.7

Additional Icons

Builder

Improved authorization rule definition

SAML2 Adapter v1

HERE Map Tile Service v1

Point of Interest Service v1

Transparency v1

OAuth2 v1

Service SDK 4.17.0

Audit Library

Support for the new hybris-user-id header

Dependency updates

Resolved issues

HERE Map Tile Service v1

Identity v1

Earth Observation Analysis v1

Image subsets

WCS function call describeCoverage

New image format PNG

Builder

A notification widget that provides project-level information

Dev Portal

API Management v1

RAML Patterns 2.0.3

Dev Portal

Builder

New widgets for the organization dashboard

PubSub Builder module v1

Manage PubSub topics and subscriptions more easily

Deletion v1

Account v2

The Account v2 service is released

The Account v2 doesn't leave anyone behind

What about the previous version of the Account service?

Builder

A dashboard on the organization level

A view to manage all of your bookmarks across organizations

Simplified project selection for new users

Service SDK 4.16.0

Support for unencoded slash in URI parameter in Rammler

PubSub v1

Allow the hyphen character (-) in the username of the Basic Authentication for Push Subscriptions

Identity v1

OAuth2 v1

Service SDK 4.15.0

Multiple values and new fields available for the metric logging pattern

Error Message Servlet

Resolved issue

Customer v1

New optimistic locking feature and personalized customer emails

Optimistic locking for customer updates

Customer information in the email templates

Velocity Template v1

Validation of uploaded template variants

Media v2

Builder

The project dashboard is available by default

Document v1

Knowledge Hub

Document v1

Document Backup v1

New features

Backup to the cloud

Request with a body

Request without a body

Restore from the cloud

Request with a body

Request without a body

List your backups

Support for the new `hybris-user-id` header

WCS function call `describeCoverage`

Allow the hyphen character (`-`) in the username of the Basic Authentication for Push Subscriptions