Xplan of today is interconnected with its data, the general idea being that a user should only enter client data once and that same data then flows to all the advice tools and modelling. To do this though means using standard areas and locations to draw the data from. The result is that today's solutions need to be double checked before falling back on custom fields and groups in order to maximise this linking and reduce double entry for users wherever possible.
"Walking on water and developing software from a specification are easy if both are frozen" Edward V Berard True enough even for when building with Xplan :)
At the same time as practices and licensees are striving to get the most out of xplan and expand usage and adoption levels, the need for help, guidance and training increases. We look at a simple but powerful approach to instantly informing and guiding users when using advice tools.
Developer considerations The entity advice selector