We are very excited to release this version of Dezide.
Highlights of Dezide Summer 2016:
- Phone Code!
- Advanced questions
- New constraint: “Force step after action or after question answer”
- Show number of used constraints on constraint button
Phone Code!
We are very proud to announce the general availability of the Phone Code feature. For customers working in highly controlled environments like factories and laboratories with no connections to the outside other than traditional landline phone calls, the Phone Code makes it possible to transfer an active troubleshooting session from the on-site field service engineer to the surveillance center without a network connection.
The Dezide Offline Troubleshooter used inside the factory generates a code, that can be read out loud to the surveillance center agent who enters the code in the Dezide Contact Center and a complete view of the actual troubleshooting session that the field service engineer has just performed is displayed to the agent. It is even possible for the agent to resume the session and continue troubleshooting online.
Advanced Questions
Sometimes it necessary to configure how certain questions behave in more detail than what is possible using the standard question editor using only the “Identify” and “Eliminate” options. In some cases the troubleshooting scenario is so complex that we need to specify in more detail how a question behaves.
We have introduced the Advanced Configuration Questions that lets you explicitly set the desired probability for each cause based on the answer to the question and we have introduced the Advanced Symptom Questions that lets you explicitly control the probabilistic nature of the question. These options are very powerfull and makes it possible to build guides for even the most advanced troubleshooting cases.
New constraint: “Force step after action or after question answer”
In some cases there are logical, political or security reasons for overriding the results of the decision engines suggestions for the next best step and it can be difficult to build this in the editor using probabilities and causes. To remedy this situation, we have introduced the “Force constraints” which lets you control the exact sequence of troubleshooting steps regardless of the recommended next step.
Show number of used constraints on constraint button
It might seem like a small feature, but by visually indicating the number of constraints created in a guide on the main guide edit page, you quickly become aware that the number is getting high, which indicates that it might be necessary to take at step back and review where the guide is going. Remember that contraints are overriding the intelligence in the system thereby limiting the options for the decision engine to suggest the next best step, so in general we want to limit the amount of constraints used in the guides.
Complete change log
New Features
- [WA-856] – Add support for advanced symptom questions
- [WA-910] – Add support for advanced configuration questions
- [WA-952] – Add guide warning box to edit constraints page
- [WA-962] – Import translated XML
- [WA-964] – Ability to configure user menu permissions
- [WA-971] – Manage feedback in portal
- [WA-972] – Manage portal menu
- [WA-975] – Security system authorization improvements
- [WA-981] – Add information box on edit advanced configuration page
- [WA-982] – Add table component for setting marginal probabilities
- [WA-983] – Create radio buttons for changing between cause selection and probabiilty editation
- [WA-987] – Add “Other causes” row in tree and make it editable [WA-990] – Add more heading options to the content editor Format drop down
- [WA-1000] – Add support for user type “Content Editor”
- [WA-1011] – Add spellchecker – browserbased
- [WA-1019] – Add support for constraint “Force step after action or after question answer”
- [WA-1025] – Add title and functionality to import translation page
- [WA-1026] – Generate report for import
- [WA-1031] – Add support for translation XML export
- [WA-1033] – Add page for selecting languages for models before translation export
- [WA-1037] – Ability to change order of answers to a question
- [WA-1039] – Show number of used constraints on constraint button
- [WA-1048] – Phone Code Support
- [WA-1054] – Extend publish page in phone code mode
- [WA-1074] – Show force constraints on constraint overview page
Improvements
- [WA-969] – Only the Administrator role must be allowed access to the Content Space Editor
- [WA-970] – All portal User Types should be available in the Administration
- [WA-994] – Show stop sign icon when hovering cells that cannot be edited
- [WA-998] – Make conversion/warning before editing advanced question a page without a base
- [WA-1003] – Add icon on main guide edit page indicating advanced question
- [WA-1004] – Replace radio buttons with buttons on advanced question edit page
- [WA-1005] – “Select relevant causes” should be selected per default when editing an advanced question with no associated causes
- [WA-1007] – Lock down advanced question editors when there is only one answer.
- [WA-1008] – Converting a simple configuration to simple symptom question should always work
- [WA-1028] – Add security translation import/export pages
- [WA-1035] – Updated help and support links on the dashboard
- [WA-1036] – Remove Activity Stream from the Dashboard
- [WA-1067] – Remove expert level column from causes on dynamic guide edit page
- [WA-1068] – Postponed step constraints with empty lists should give a warning
- [WA-1070] – Hide list of actions on data collection refkeys page
Bug fixes
- [WA-1006] – “Copy contents from default language” generates a Tapestry error for non translatable items
- [WA-1015] – After editing one answer, when you edit the next, it gets the same name
- [WA-1017] – Configuration of advanced questions not used for advanced symptom questions
- [WA-1040] – Taxonomy page reloads and changes are gone
- [WA-1069] – Conditions for postponing a step cannot be removed
- [WA-1077] – Solution editing in paginated tables on dynamic guide edit always edits the items on first page
1