---
schema_version: "1"
id: 98db7ba75fef2cc8751d4612bccaf894a7c8bae508d9200dc95e058186e907c1
title: APIkit Mule4-1.1.7 Release Notes
collection: mulesoft
version: current
locale: ja-jp
portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/apikit/apikit-4.1.7-release-notes.md
canonical_url: https://docs.mulesoft.com/jp/release-notes/apikit/apikit-4.1.7-release-notes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 8b79ba26255995c957fe297c3890a22d59001459ef0010b03d6fb8cb8776a22e
description: MuleSoft Documentation Site
latest: true
---
# APIkit Mule4-1.1.7 Release Notes

**August 29, 2018**

## [](#whats-new)What’s New

There are no new features in this version. There are just a few enhancements and bug fixes.

## [](#compatibility)Compatibility

- Mule Runtime 4.1.2 and later
- Anypoint Studio 7.2.0 and later
- Java Parser RAML 1.0 v1.0.20
- Java Parser RAML 0.8 v0.8.22
- API Console 4.2.0

## [](#fixed-in-the-release)Fixed in the Release

- APIKit validations don’t display the field.
- APIkit not using example from raml.
- SE-8909: Content type not allowed in flow mapping for APIKit.
- SE-8900: skipNullOn="everywhere" causing issues java.nio.charset.IllegalCharsetNameException on Windows
- 'content-type' is not accepted as valid flow-mapping attribute.
- Metadata for Attributes communicates everything as nullable.
- NPE in APIKit Metadata when no RAML is specified.

## [](#enhancements-in-this-release)Enhancements in this release

- Scaffolder duplicates flows if there are in a different xml where the api router lives

## [](#see-also)See Also

- [Known Issues](https://help.salesforce.com/s/issues)