issue with the sample csui-sdk-16.0.3 widgets custom search

Lili_Yu

I'm testing the provided sample widget in the shipped csui-sdk-16.0.3 zip file.

first of all, I'm confused with the sample code listed in the "csui-sdk-16.0.3\samples" vs."csui-sdk-16.0.3\lib\src\csui". The sample-index.html page seems refer to the code listed in the 2nd directory. So not sure the purpose of the first one.
I was testing the code in the 2nd directory"csui-sdk-16.0.3\lib\src\csui\widgets\search.custom", was able to change the connection, disable the mock, and load with real saved search query on the testing page; however, when click "search" button, it does nothing. The console indicates an error "Uncaught TypeError: Cannot read property 'map' of undefined at alpcsuiselectfield.js line35". I really have no clue how to correct this.
3rd, I tired to understand the difference between this custom widget vs. the core "Custom Vew Search" widget. it looks the same to me when loading the search prompt page, and the core widget works well while this provided sample code is broken at the moment. Can you explain the difference and purpose?

Thanks

Lili

Find more posts tagged with

Comments

Ferdinand Prantl

The contents of "csui-sdk-16.0.3\samples" are custom code samples. They can be observed, how and why it works, or copied to your development project and adapted to implement a similar scenario. The contents of "csui-sdk-16.0.3\lib\src\csui" are csui sources, which can be used to debug your sources with better performance and more useful context. That's why they are referred from development pages instead of the released "<cs cgi script>/widgets".
The demostration page "csui\widgets\search.custom\test" shows how to display the search.custom widget. It doesn't show search results; it sets properties in the search query model and expects, than some other component will watch it and react by updating search results or opening a new page with them. The errors, which you saw, were probably bugs in form fields. You could add SearchResultsView to the page, as it is done at "csui\widgets\search.results\test".
What do you mean by "this custom widget"?

Lili_Yu

Thanks for the clarification. I think your point#1 answers my point#3 questions.

So far, I was able to test through the csui source code widgets, for the shortcut widget, i've changed the connection, disable the mockup, changed the id; but when click the widget of given shortcut, no action follow - expect to go into the requested folder. So, what change needs to be done to make clicking & action?

Thanks

Ferdinand Prantl

Demo pages in "csui\widgets\shortcut\test" show how to create the widget with different configurations. It doesn't show, what can happen outside the widget, if you click on it. Shortcut widget sets ID of the contextual next node model (maintained by the 'csui/utils/contexts/factories/next.node' factory).

Navigation controls in CS UI do not navigate by changing the window location. They set attributes of particular contextual model and expect, that some other component is watching. For example, Smart UI pages shown for users and nodes are called perspectives. The perspective context is watching a couple of context models and if the next node model gets the node ID set, for example, it tries to open the perspective for the particular node.