Iress Contributor12th Feb AMA: I'm Courtney Youngblutt, Xplan Design Consultant & efficiency expert, Ask Me Anything!
Hi courtney.youngblutt,
OFA, great topic now it's been 1 month since the new requirements have commenced! I have a couple of questions (and wish lists)!
1. What widgets can be used for tracking the new OFA requirements (if using the standard Opt-in fields)?
We have a couple already set up to track changes, who is due in the next 60 days, those whose status has changed to lapsed out after 150 days, do you have any other suggestions on helpful widgets?
2. It would be great if the terminology in the widgets and opt-in fields could be updated to replicate the new terminology, is this on the roadmap any time soon? 😁
3. Search Criteria - we would like to create a search criteria for clients due for OFA 60 days before their reference day to be able to schedule workflow to commence. That one is possible. Then another search criteria that includes clients that have a reference date that is say 120 days old we can schedule a report to be sent to advisers as they only have 30 days left, then another that is 150 days old so we can identify clients that either haven't been updated in XPLAN or they need fees turned off. If the opt-in section is used correctly, we can see those that have lapsed - opt-out, however if the status was not changed to pending, we need to be able to identify those clients as well. However, to add this search criteria, the fields do not allow 3 digits to be entered, the max is 2. Do you have any suggestions on work arounds for this?
Thanks
Jackie
Note to anyone from Xplan who is following the issue Jackie mentions about the 3 digits for search criteria - this should have been resolved years ago. It was raised as an issue when the first version of FDS and consent process commenced, and we needed to be able to search on 120 and 150 days post the anniversary date. And it has been raised a number of times since and nothing has happened!
- courtney.youngblutt
Hi susie.vincent,
I understand that this has been raised before and fully agree that it would be useful.
I checked in with the product team to see why we haven’t just gone ahead and just done this. They also get that this would be helpful, and updating it has not been ruled out, but unfortunately it would be a massive job behind the scenes and would have flow on impacts to lots of other areas.
It's not a quick fix and can't be considered in isolation, so needs to form part of a much larger piece of work.... not what you wanted to hear, I know. 😬
