Engagement Services - Virginia cluster 3 database outage

• Engagement services in Virginia cluster 3

[01:21 UTC] Engagement services is unavailable for some customers in Virginia. We are investigating.

[02:01 UTC] Resolved. We identified a failing database, which was rebooted. The service was restored at 01:52 UTC. We will continue to monitor and investigate the cause of this incident.

Workspace Hotfix

• Workspace

  • Fix inability to provide input parameter for deleting in the dev portal for storage object service

  • Fix incorrect Swagger model response for POST/PUT/GET verbs for object services

  • Fix link on Client SDKs page to download Visualizer navigating to community.kony.com when should be navigated to download section in Kony Community

  • Fix export of app/services not cleaning up temp files when a failure occurs

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Cloud Management Console Hotfix

• Cloud Management Console

  • Fix issue occurring when adding an orchestration operation it is linking the operation to all versions of the service

  • Fix issue occurring when logging out from the console, claims token is not invalidated

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

[2017-09-21 22:56 UTC] After further evaluation, hotfix is being deployed earlier than original schedule.

Engagement Services - degraded performance for sending messages

• Engagement services

[23:28 UTC] Some customers have reported slow message sends for Engagement services. We are investigating the issue.

[November 6 15:42 UTC] Resolved. “Send immediately” message functionality was detected as being impaired (noted in https://www.kony.com/status/engagement-services-send-immediately-message-functionality-impaired). Performance was improved in the short-term. A long-term fix has since been deployed (on October 1) and functionality has been performing well since deployed.

Engagement Services - "Send immediately" message functionality is impaired

• Engagement services

  • “Send immediately” messages are not functioning as intended. Please do not use this for large segments. Instead, schedule the send actions for 5 min in the future.

[September 27 11:00 UTC] Development is working on a hotfix which is expected to be available the week of October 1st.

[November 7 16:01 UTC] Resolved. The hotfix has since been deployed.

V8 Release

• Cloud management console:

  • Users can create new API Development Portal to engage with their API Consumers

  • Users can create IBM MQ integration service

  • Visual mapper enhancements

  • Support for visual mapping in Object Services of type Integration and Orchestration

  • Support for ‘Otherwise’ in choose block

  • Import-Export enhancements

  • Users can export and import individual services

  • Application & Service exported packages now contain dependent data adapters/logic packages

  • Conflict information is shown to the user as part of enhanced import experience for apps and services

  • Service Testing enhancements

  • Support for testing of complex types in integration

  • Test of Object services of type integration and orchestration does not require dependent Services to be published

  • Simplified flow for creation of data adapter & upload to marketplace

  • Addition of identity services to the published snapshots

  • Simplified enhanced identity configuration

  • URL provider support for XML, JSON, SOAP, & API Proxy service types

  • PostgreSQL support

  • Enhanced custom reporting domains by adding fields for tracking time spent loading the app and time spent by app in foreground

  • Performance enhancements for standard and custom reports

• Identity services

  • Users can create an Auth Server using Kony User Repository and Active Directory as authorization servers

• Fabric SDK

  • Added a new Log SDK for logging device logs

  • Supports logging to file, console, server

  • Log level can be dynamically modified from server for a particular user’s device using identifiers like IP address to help troubleshoot issues

  • Log SDK is integrated with Identity, Metrics, Sync, & Offline objects SDKs

  • Log SDK can be used by app developer to log application logs as well

  • Added support for invoking Logic service from Fabric SDK for Visualizer

  • Added support for Google Oauth login as google had deprecated support for login from embedded browsers recently Fabric SDK for Visualizer

  • Added support for downloading binary for windows 10 Sync based apps built using Kony Visualizer

  • Added APIs for downloading binary from box.com through integration services when device is online for apps built using Fabric SDK for Visualizer.

  • Enhanced support for Kony Fabric SDK for .NET

• Integration services

  • Users can create a new free forever Kony Fabric starter environment

  • Improved support for Scheduled Jobs

  • Note: any existing Clouds containing Kony Integration server runtime environments will not be affected during the maintenance window

• Offline Objects

  • Offline Objects is a new capability of Object Services in v8 that provides a simplified approach to synchronizing data to a client app for offline access. The following offline scenarios are supported in this release:

  • Data download & upload for a single object

  • Data download & upload for all objects in an object service

  • Data synchronization using background processes that avoids blocking the app UI

  • Running multiple sync processes in parallel

  • Logging built into offline objects SDK for ease of troubleshooting

  • Batching for data download

  • APIs for tracking sync progress

  • APIs for setting filters on data being synchronized to client

  • Upload/download for object service with hierarchical data

  • APIs for performing CRUD operations on object in the client

  • Ability to reset sync

  • Ability to rollback sync to last successful state

  • iOS and Android native app support

• You can read more about V8 on the official site

• Additional details may continue to be provided as we near the release date

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Engagement Services V8 Release

• Engagement services

  • Provide support for recent activity timestamp, which will be populated when the user is created. Also supports updates from the API.

  • Support update of user data by accepting only the data that will need to be updated and also perform the update using the email address if needed.

  • Support priority of message channels in events so that an event message is delivered using the lower priority channel when the higher is not available.

  • Support use of the date type for segment creation both by the UI and the API.

We anticipate Engagement services being unavailable for ≤ 2 hours during the maintenance window. Scheduled maintenance is designed for minimal disruption of service availability when possible.

Engagement Services Release

• Engagement services

  • Internal configuration

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Engagement Services - Virginia cluster 3 database outage

• Engagement services in Virginia cluster 3

Resolved. At 18:08 UTC an internal DB server issue required a reboot. The reboot required an outage, and the system was back in service at 19:30. For some customers, the Kony Engagement console would have been unavailable during the reboot. We are investigating the root cause of the reboot.