Kinetic Request CE 2.1.0 introduces powerful new capabilities that enables users to store and query for large datasets in a scalable, performant way via Datastore Forms. This release also adds a feature which allows form and workflow developers to evaluate exactly what's changed when an Update Webhook is called. Various other enhancements and bug fixes have also been included in this release which you can read more about here.
New Installation Instructions
Install Links & Guides
Detailed installation instructions for setting up Kinetic Request CE can be found here: Kinetic Request CE Install Guide
Related Product Installation Guides
Typically, customers will extend Kinetic Request CE's functionality by installing the following components as well:
Kinetic Task: The workflow automation and integration hub for Kinetic Request. Kinetic Task helps business deliver approvals, fulfillment, notifications and other integrations to nearly any application. (Install Guide)
Kinetic Bridgehub: The front-end integration hub used to store and run various Bridge Adapters that will be used to access data from different systems and convert it into a single, standardized bridging interface. (Install Guide)
Kinetic Filehub: The file storage and retrieval hub containing various Filestore Adapters that can be used to access files from different systems using a single, standardized interface. (Install Guide)
- You must have a download of the new Kinetic Request CE 2.1.0 web archive (.war).
- Update your DB schema for the keyspace used by Kinetic Request CE (version 2.1.0 includes schema changes - this step is necessary). https://s3.amazonaws.com/kineticdata.com/downloads/kinetic-request-ce/2.1.0/schema.cql
- If you are upgrading from a version before v1.0.4, please see the Upgrade Instructions from v1.0.3 to v1.0.4+ guide.
- If you are upgrading from a version before v1.1.0, any custom bundles that leverages the built in password reset will need to update their passwordReset.jsp to match changes in request-ce-bundle-base.
- Backup the existing web application directory (%TOMCAT%/webapps/kinetic).
- Deploy the Kinetic Request CE web archive (.war) file.
- Copy the following directories:
- %BACKUP%/kinetic/app/bundles to %TOMCAT%/webapps/kinetic/app
- %BACKUP%/kinetic/app/root-bundle to %TOMCAT%/webapps/kinetic/app
- %BACKUP%/kinetic/app/shared-bundles to %TOMCAT%/webapps/kinetic/app
- %BACKUP%/kinetic/WEB-INF/config to %TOMCAT%/webapps/kinetic/WEB-INF
- Copy any non-standard .jar files to the tomcat shared lib (this is not typical, and only needs to be done if you've added custom .jar files to the application):
- %BACKUP%/kinetic/WEB-INF/lib/... to %TOMCAT%/lib
- If SAML is being used (and if upgrading from a version lower than 2.0.0):
- Find the name of the IDP file by looking for the security.saml.idp.filebased.url value in the %BACKUP%/kinetic/WEB-INF/classes/security.%SPACE_SLUG%.properties file(s).
- Copy the IDP files from %BACKUP%/kinetic/WEB-INF/classes/... to %TOMCAT%/webapps/kinetic/WEB-INF/config
- Restart tomcat.
|Implements Datastore as a component of the CE Platform.||Implements Datastore as a component of the CE Platform, allowing Datastore forms to define and build up referential data that can be effectively leveraged. Datastore forms can store hundreds of thousands to millions of records and still perform searches quickly and effectively on any field or combination of fields by allowing administrators to not only define the form, but the indexes on those forms. For more information on Datastore, click here.||KCORE-1755|
|Adds ability to compare current (previous) and updated values for update webhooks||Adds the ability to access both the current (previous) and updated values in the update webhooks, which means both the old and new values are available to the receiving system (eg. task tree).||KCORE-2069|
|Adds support for single page app bundles by adding a new space Display Type.||The necessary files for the CE server part of a REACT bundle (webpack) now ships with the application, and a single page app are more easily specified with a Display Type on the space.||KCORE-1921|
|Implements ability to return only specific attributes or values via the API using the ?includes parameter.||Previously, either all or no attributes could be returned via the API. This update implements the ability to return only specific attributes or values via the API using the ?includes parameter. Ex. ?includes=attributes[my-attribute-name]||KCORE-1798|
|Improved Stability of Submission Indexing/Searching||This addressed many sub-issues, including adding the ability to check and rebuild submission indexes, the ability to do blue/green submission indexing, WriteTimeoutException handling for Submissions, and a number of changes to support datastore form indexing.||KCORE-1912|
|Adds Origin and Parent GUID submission properties to the CE Console Forms > Submissions > (guid)||
When viewing the submission in the CE console, the Origin and Parent GUIDs are shown.
|Adds compatibility for Java 9 without configuration||This addresses an issue in CE caused by changes to what is included (and not) in the default path in Java 9. This allows use of Java 9 without having to update the path.||KCORE-2007|
|Introduces use of an attribute map when using the CE API to interact with attributes.||Improved ability to set specific attributes by providing an attribute map when updating a CE object via the API. Also implements the ability to return attributes as a map instead of an array by specifying `?includes=attributesMap` instead of `?includes=attributes`. Note this can also be used to get a specific attribute with a map using '?includes=attributesMap[ATTRIBUTE NAME]'||KCORE-2025|
|Exposes the form type to the front end via the form object (K('form')) and the K.config.ready selector.||
The form type property is now available to the form object with the call:
It is also available to K.config.ready.
|Update the K.load js method to pass a status code to the error callback||The error callback on K.load (calling subforms) is called for any error not 401, 403, or 404 (these have different callbacks). This enhancement passes the status code to the callback to allow for conditional handling if desired.||KCORE-2104|
|Don't fire the User Updated webhook on auto.update (when using an identity provider) because nothing has actually changed.||When authenticating to CE using an identity provider, if the auto.update setting was set to true, the user record was being updated even if no changes were made to the user. This was causing User Updated Webhooks to be triggered even though nothing changed. This enhancement cleans that up and prevents the webhook from firing in this particular nothing-changed scenario.||KCORE-2192|
|Page navigation to the "first" page should not require a reference page||KCORE-1810|
|Fix regression with LDAP groups not being applied when using LDAP authenticator||When using the LDAP authenticator, the individual who logs in should have their LDAP groups added to their UserDetails to be able to be used by the system, including by KSL for security rules. This was lost in a previous release and is restored in this release.||KCORE-2094|