What’s New

Here, you will find the updates in the platform SDK and in this documentation since the previous release.

APS API

• With the new mechanism of aliases, the actors on the APS bus can use less and much shorter REST requests to call some APS operations of both kinds CRUD and custom. Now, instead of the long “implementing” RQL function to specify an APS type ID, a REST request can refer to the alias of that APS type directly as explained in the APS Types document. For example, instead of:

  GET /aps/2/resources?implementing(http://aps-standard.org/types/core/account/1.0)
  

  you can use:

  GET /aps/2/collections/accounts
  

  All singleton resources (services) have aliases. With the service alias, you do not need to preliminary identify the APS ID of the service to call an operation afterwards. For example, instead of the two operations:

  GET /aps/2/resources?implementing(http://www.odin.com/billing/order-management/1.3)
  

  POST /aps/2/resources/<resource-id>/orders
  

  use only one operation:

  POST /aps/2/services/order-management/orders
  

• The access to APS resources for APS connectors can now be limited by means of the impersonation mechanism. An application can require impersonation at one of the levels, either provider level (means unlimited and it is the default for those applications that are not aware of the new mechanism), reseller level, customer level, or none. When installing an APS application instance, the provider can allow or reject the required level of impersonation. The feature improves security for applications and increases the platform robustness from occasional or intentional application misbehavior.

• The order management API is extended with the following new features:

  • Specify a payment method in a request for order creation.
  • Request for several service plans in a sales order.
  • Get a list of orders filtered by their status in the order flow.

• With the new APS-Actor-Scope HTTP header, APS application UI can specify a scope of APS resources it wants to get from the APS controller.

• With the new aps/MultiLine widget, it is possible to align the aps/Output and aps/Status widgets into a column or a row using various styles.

• The new additionalInfo property in the aps/Tile module aligns vertically the blocks of data printed out by a group of tiles as explained and demonstrated in the Alignment of Additional Info section.

Development Tools

The new versions of the Command Line Tools, APS PHP Runtime, and APS Fiddle are issued to support the updated APS API.

Security

The new GDPRSupport APS type makes it easier for APS applications to comply with the General Data Protection Regulation (GDPR) of the European Union. The new Personal Data document explains the concepts and provides some examples.

SDK Documentation

• Some examples in JS Modules and screenshots in UI Style Guidelines were updated to make all examples strictly comply with the Widget Hierarchy rules.
• All examples with an old style HTML declaration of widgets were removed from the JS Modules documents.
• The new UX1 user panel is introduced in the Integration with User Panels section. Everywhere in the current documentation, the UX1 panel replaced the CCP v2 panel.
• In the certification requirement document, rule 3.3, the SVG graphical format was added as allowed.
• The Human Interface Guidelines set of documents was substantially restructured. All its recommendations and examples are compliant with the new UX1 user panel.

← Glossary