Skip to main content
Kinetic Community

What's New in 5.1

New Features in v5.1.1

Pure Java Remedy API Support

In Kinetic Request v5.1.1, the entire code base was updated to support the pure Java Remedy API.  This provides major benefits in the form of better stability with Remedy 7.6.04+ servers, no longer dependent on the Remedy C API, and 64-bit Java support.

 

Support for Remedy Overlays

With the upgrade to the pure Java Remedy API, Kinetic Request now supports overlays that were added in Remedy 7.6.04.  Previous versions could not deal with fields added or modified on overlays because the JNI Remedy API did not support them.  Enhancements in the Remedy workflow have also been made so fields on overlays are avialable in the administrative dialog menus as well.

 

 

 

New Features in v5.1.0

Kinetic Bridging

kinetic-bridges.png​​Kinetic Bridging is a strategy for utilizing distributed and disparate data systems within Kinetic Request.  Through Kinetic Bridging, Kinetic Request can populate service items with live, dynamic data from BMC Remedy (including OnDemand), Active Directory, custom database solutions, or any other data storage solution.

​To find out more about Kinetic Bridging, please see the Kinetic Bridging section of our Kinetic Request documentation.

Kinetic Bundles

request-theme-box.pngrequest-theme-air.pngKinetic Bundles is a new framework designed to simplify and organize the specification of your Kinetic Request web presence.  The Kinetic Bundle framework defines a series of conventions intended to increase reusability throughout your theme and provides new strategies for the development of even more powerful and innovative Kinetic Request interfaces.

To find out more about Kinetic Bundles, please see the Kinetic Request Bundle Guide section of our Kinetic Request documentation.

Events Tab

request-builder-events.png

New in Kinetic Request 5.1 is the Service Catalog Console Events Tab.  This tab provides a complete list of events associated to the current Kinetic Request template, allowing for direct and easy access for search and modification.  

Submission Locking

Each template can define whether customer submissions (KS_SRV_CustomerSurvey_base records) for the template are locked to a specific user.  This ensures that only one person can submit answers for the specific request record, particularly useful for Fulfillments, Work Orders, and Approvals.

Review Request Configuration with Template Attributes

Review Request can now be configured using Template Attributes.  This alleviates the need to explicitely include the rendering JSP as a URL parameter, and provides a simple way to default Review Request Configuration values for a given template.

Enhanced Question Defaulting

request-builder-enhanced-question-defaulting.pngQuestion defaulting has been enhanced to leverage template or submission field values and answer values, very similar to the Dynamic Text element type.  This provides a simplified strategy for defaulting a question based on the answer from a previous page, or concatenating multiple values into a single answer.

Read-Only Question Configuration

question-read-only-default.pngThe Question style configuration has been enhanced to provide the option of making a question Read-Only by default.  The simplifies the interface and removes the need to set a page load event to change the question or section to be Read-Only.

Performance

Kinetic Request 5.1 includes significant improvements to performance on both the client and server sides of the application.  On the client side, the internal Javascript was refactored to cache references to common elements.  This small change reduces the number of DOM traversals necessary to interact with page elements and events.  These improvements affect all browsers, but have an especially effective impact on Internet Explorer.

On the server side, the submissions process was enhanced and template caching was implemented.  The submission process was changed to write answer information to the database in a separate thread.  This allows Kinetic Request to return the next page of a Request immediately, without waiting for all of the answer data to be serialized.  Template caching further improves the user experience, increasing the speed at which a Kinetic Request form can be generated for display.