New CaseAware Features Now Available

​Continuous improvement is one of many reasons a360inc’s CaseAware is the best case management system in the industry, we constantly strive to make your job easier via improvements and upgrades. Through communication with our clients, user surveys, and some of the brightest technological minds in the business, we identify areas of improvement and act on them. 

Over the last few months, we’ve made several enhancements centered around the referral processing user experience. The following 3 new features are the latest to be checked off the list. Here’s to getting back a few more minutes in your day.

Block/Allow referral and Document Download
This feature gives you the ability to refuse certain events or documents, so they aren’t charged for things you don’t want or need.  

You can block or allow certain rails or documents by servicer and even loan type. To prevent you from being charged to pick up a rail that you don’t intend to send/receive data on in the future. 
How was this processed previously? Users either purged the referral/subprocess from integration queue or possibly you configured the sub process map to purge certain sub processes. Either way there was still a transactional cost for processing. With this new feature it eliminates the financial burden from even processing the data giving you a direct cost savings depending on your referral volume.  ​

To implement we suggest the following:

• Use the Load BKFS to account for hundreds of combinations of combinations of events/documents you want to ingest that vary by client and loan type. By default, we are giving you everything and allowing you to pick/choose what you want to allow or block
• Once you’ve decided to allow the ingestion of the rail data, don’t forget to link it to the parent if it’s a sub process by reviewing the BKFS Desktop SubProcess Menu. 
• Review Issue 23822 for more information 

Interface Site and Sequence Mapping Imports
Now that you’ve configured your integration to ingest the most important data points, let’s talk about processing the referrals in the referral queue. 

We’ve added functionality to allow customers to create mapping to auto-populate the site selection on referrals and functionality to create related conditions.

• Now you have the ability to allow conditions to be a part of the import
• For example, if you receive a BK POC referral in Tennessee- you can condition the logic to automatically open to the correct site and sequence where you would normally process that referral. Eliminating a few clicks and a few mistakes! Or files/cases being tagged to the wrong site (which may tie to your operating accounts and financials). Whether you decide to segregate site by state or sequence (or both) the new auto-mapping feature gives you additional flexibility for automation. 
• Issue 23774 and 23775

Update Integrated Loan Info when Adding an Existing Case
We added an optional setting when the BKFS desktop integration receives a new case to an existing file, specified fields get updated with the new referral information 
​
Have you ever had a situation where the UPB or loan date was different from when you received the original referral a few years ago? Previously this information wasn’t updating (by design) because it was a perceived risk to overwrite the data. However, many of you have asked for it to assist end users who were forgetting to review or update the data. So, we provided an optional setting to allow you to bring the new information in from BKFS eliminating keystrokes and extra review.  

• Issue 23810 

What’s next on the referral enhancement roadmap?
We’re looking at enhancing the conflict check process and a comprehensive integration dashboard feature. Stay tuned!

If you have a question about how something should work, Bronze Subscribers should continue to contact CA Support. Silver and Gold subscribers can reach out to your assigned CAM.

Want more from your CaseAware? Learn about Case Aware Silver
Want it All? Learn about CaseAware Gold