Customer Portal

Get Involved. Join the Conversation.


    Shiloh Madsen
    Feedback widget...first time editing a widget
    Topic posted September 19, 2008 by Shiloh MadsenBronze Trophy: 5,000+ Points, last edited October 29, 2011 
    1245 Views, 1 Comment
    Feedback widget...first time editing a widget

    One of the elements of functionality that our redesign will require is a way to gather feeback which is a little different from what the precanned widget seems to be able to do. I think I am going to need a little assistance in understanding what will need to change in order to accomplish this. 


    What we will need to display is the feedback question with three options: Yes, No and Yes, but. Two out of these three (ideally all three) need to display their own interstitial feedback window when selected. Out of box functionality dictates only a single window, displayed when the selection is below threshhold. Adding to this, we will be gathering details of either why the article didn't help (in the case of no) or what was wrong with it (in the case of yes, but). This data gathering will be presented as such: When a customer selects either "no", or "yes, but", the div will display several radio buttons which should help narrow and categorize what went wrong. These values should be stored in a custom field. They will also be presented with a feedback textarea to fill out more detailed information. 


    To summarize: We need to display different feedback divs based upon which of three feedback options a customer selects. Those divs need to gather data which can be inserted into a custom field in the db for tracking feedback. Is this something the folks on the forums can help me to understand how to begin coding, or will we need to go to our direct account rep for something like this? 



    • david fulton

      Hey Shiloh - interesting use case. It shouldn't be a major issue to deal with through a custom widget - it just sounds like instead of one hidden div containing the feedback form, you probably need two of them - as long as they essentially submit the same kind of data, it sounds like most of the work is in changing the view and some work changing the logic to support the additional events - the only change I can think of to your model is probably to support that incident custom field addition.


      Have a look at the out of the hidden divs (you'll also want to look at the out of the box CSS for that object as it may control the placement and visibility of the form object) and work from there.