What We're Working On

Custom Field Logic

It would be great to have custom fields that can be based on logic. For example, If field A is “1” then make field B and C available. Else do “do nothing” (or make field D or E available if you wanted). You get the idea.

http://forums.webhelpdesk.com/forums/comments.php?DiscussionID=747&page=1#Item_0

  • I believe you could accomplish what you are wanting to do by making use of the "Process\Action Rules". Under the Criteria tab, choose "Custom Field" from first drop down, then whatever other fields you want to specify. You would need to create multiple Actions to send out the different emails to the specific recipients based on the criteria specified. Hope this helps.

  • Would this not work the same way you can add custom fields when a certain Status is selected? So it seems the WHD has the capability to do this in my opinion. We are new customers [Healthcare organization] and are finding this to be a HUGE issue in creating online security requests.

  • Would like the following Field Type added - Calculation. So Field E can be the sum of Fields A, B, C, and D

    Would like dependent value list, so dropdown field B can display different content depending upon the selection in Field A. ie Field A has Wisconsin, so field B could show Green Bay; Neenah; Appleton; Oshkosh. If Field A has Indiana, Field B would show Fort Wayne; Indianapolis; Gary

    I would then like to design the Form so I can have fields horizontal and/or vertical.

    I would like Checkboxes to display horiztonal or vertical, not be confined to only vertical.

  • This would fix a problem I NEED to find a fix for.

    We use WHD internally and one of our tech groups "bills" based on their time.  We need an ability to have fund numbers listed but need it to drill down either based on department or another custom field (I could work with either).  Then the last option could be "Other" and if that's selected, another custom field could appear allowing them to manually enter a fund number.  We need to do this on a per ticket basis as each ticket might be working off a different fund related to that group.

    I don't want our users to have to filter through hundreds of different fund numbers when they really only have a few that matter to them.

  • This request is a bit like the logic used in the FAQ. Not hard to do. Just like creating the request types and sub-types to be presented in the FAQ, we do it in other areas of the platform.