Smart Navigation: Provide a property to limit the number of chars entered into search box

Hi Gokhan,

As part of our efforts to be transparent about our intentions with each enhancement suggestion, the offering team has initiated an annual process to carefully review the list of open enhancements.
As agreed through the account manager for MSD, we are closing this RFE as it was confirmed that it is no longer required.

We acknowledge the benefit of your suggested enhancement and although we will not take any further action at this time your suggestion will be available in our ideas repository for future consideration.

We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

Regards,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Note: we are currently in the process of improving your RFE experience and will soon transition to an Ideas Portal provided by our trusted business partner Aha!
Further communications with additional details will be shared shortly.

Hi Gokhan,

Thanks for replying with the extra information. We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development and we have no short term plans to provide this enhancement. However, the theme is aligned with our current multi-year strategy and will be considered for a future release.

IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

IBM will update this request in the future.

Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team

Hi Shane,

I am afraid I don't agree with "making the character limit configurable may not make the performance gains anticipated so we are questioning the value in adding this into the product."
Because limiting number of characters will essentially limit the number of words that can be entered as search criteria which will then have impact on the number of db calls made per full search criteria.

I am aware that there is a property that controls the debounce time and type-ahead search can be disabled when this is set to -1.
This property controls the search trigger behaviour. But this enhancement is about limiting the number of characters that can be entered as search criteria.

Smart Navigator search logic fires a facade call with user entered search criteria. This facade then parses the criteria and invokes the following two methods to perform searches using different word combinations:
1) searchPersonByIDAndDateOfBirth(String alternateID, Date date)
2) searchPersonByTermsAndDateOfBirth(String[] termsToSearch, String[] allTerms, Date date)


For example when user enters "John Smith Mary Simpson", facade makes the following invocations:
1) 4 X searchPersonByIDAndDateOfBirth --> one for each word in criteria, this method validates the input so won't invoke db searches when charset is not fully numeric.
2) 4 X searchPersonByTermsAndDateOfBirth --> For combinations of "John Smith", "John Smith Mary", "Smith Mary" and "Mary Simpson", all 4 calls will trigger db search.

If you increase the number of the words in search criteria like "John Smith Mary Simpson Shane Larkin Francesco Mariani James Connolly", this will perform 10 searchPersonByTermsAndDateOfBirth and each of them is a separate person search at db level.
Above criteria is about 70 chars length and includes 10 full names. Users may tend to use this search with partial names, therefore enter shorter words. This means more words can fit for same number of characters and that means more searches being performed.

Hope this makes sense,

Regards,
Gokhan

Hi Gokhan,

We have investigated this issue further and making the character limit configurable may not make the performance gains anticipated so we are questioning the value in adding this into the product.

As a user types in the input field, IBM® Cúram Smart Navigator searches for results. However, the search is not performed on every keystroke. The debounce technique groups every keystroke into a single event until the user stops typing for a specified time. By default, the debounce timeout is set to 500 milliseconds (ms), so the search is triggered only when the user stops typing for 500 ms. This value is configurable and can be disabled by setting the value to -1.
Debounce timeout documented here in KC: https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.8/com.ibm.curam.content.doc/WebClientReference/t_WEBCREF_config_debounce_timeout.html

We believe the configuration options provided by the debounce technique offer a better approach to managing the search load than the character limit requested in this RFE.

Please let me know if you are in agreement or can provide further feedback to support this request.

Thank you,
Shane McFadden, Cúram SPM Product Management team

Hi Gokhan,

We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development and we have no short term plans to provide this enhancement. However, the theme is aligned with our current multi-year strategy and will be considered for a future release.

The Smart Navigator, by default, will fire off requests to the server every 500ms (referred to as debounce - https://www.ibm.com/support/knowledgecenter/en/SS8S5A_7.0.4/com.ibm.curam.content.doc/WebClientReference/t_WEBCREF_config_debounce_timeout.html). If you are facing performance issues you could change this to fire less often (less requests to the server) or even turn it off altogether (by setting the value to -1) in which case the search only fires when the user hits enter. This could be a better option to control the rate of requests to the back end in production.

IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.

IBM will update this request in the future.

Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team

Hi Gokhan,

In order to evaluate your request, it would assist us if you could provide the specific use case(s) where you might need to enter more than 100 characters and share them with us.

The Smart Navigator feature was extensively tested for performance issues so it would be interesting to hear if you are experiencing any in production?

If we do not receive this information within 30 days, this request will be closed.

Thank you,
Shane McFadden, Cúram SPM Product Management team

Hi Gokhan,

Thank you for your enhancement request.
We require some further analysis to determine whether or not this enhancement can be considered in a future release.
I will provide another response when our investigation is complete.

Thank you,
Shane McFadden, Cúram SPM Product Management team

Attachment (Use case)