XPLAN CODING

A long time ago, in a blog far away…

Risk Profile descriptions are an interesting test case for all the weird and wonderful ways you can go about delivering results for clients.  If you were to grab a handful of coded advice templates you’d find a mix of risk profile descriptions and charts either hard coded in the template, right through to all sorts of half dynamic solutions, involving the document library and or fields.

We’ve previously looked at the advantages of getting these out of your template (amongst other mechanisms) and storing the Risk Profile descriptions in the dedicated spot within your xplan sites Assumption set > Risk Profiles.  Since that article, this area of xplan has been further integrated with Prime and the Robo Advice tools, both drawing on the descriptions and data in this area for their respective interfaces.

What’s changed?

Not only do we have  more rich text fields – so there’s now plenty of space to store everything related to your risk profiles – but we have xmerge for it all.  This, combined with the point around how its integrating with other products you might like to use in the future (Prime and Robo), makes a strong case to start using this area if you aren’t already.

Coding to extract all the descriptions from Assumptions

Use the below code to extract the description (and other rich text fields) for the entities risk profile.

Client

Partner

Joint

Client Group

Notes

• If you want to shorten the code, a common approach is to assign a portion of the path to a variable, such as: <:let clientATR=$client.risk_profile.attitude_to_risk():>  Under this approach, calling the description would then look like: <:=clientATR.risk_profile_desc_rtf:>
• Remember, the output will be based on the clients group associations – not yours.  So if you get unexpected results in the text outputs just double check the clients groups and what assumption set their primary group is associated with.