# New CommCare HQ Features

**URL:** <https://forum.dimagi.com/t/new-commcare-hq-features/620>\
**Category:** Users\
**Created:** [August 5, 2011, 2:52pm UTC](https://forum.dimagi.com/t/new-commcare-hq-features/620 "2011-08-05T14:52:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dannyroberts](https://dimagi.b-cdn.net/letter_avatar_proxy/v4/letter/d/94ad74/32.png) [@dannyroberts](https://forum.dimagi.com/u/dannyroberts)\
**Post date:** [August 5, 2011, 2:52pm UTC](https://forum.dimagi.com/t/new-commcare-hq-features/620/1 "2011-08-05T14:52:31Z")

</div>

Hey All,

I want to highlight a few new features in CommCare HQ.

- _Improved detail screen configuration_. As many of you may have noticed, a  
couple weeks ago we changed the detail screen configuration tool. This is  
where you can design how your case lists and referral lists will look. Due  
to poor internet in many areas, we decided it was best to let you make all  
the changes you wanted before saving, thus avoiding the tediously slow page  
reloads. One big difference in the new interface is that you can configure  
the short view (i.e. the case list) and the long view (i.e. full screen for  
one patient) _in a single table_, thus cutting out redundancy. You'll notice  
that the checkboxes at the left; you can use these to decide whether to put  
a property on the short view, the long view, or both. We hope you like the  
new layout!

- _Search Only format in case list_. We've heard from a number of people  
that when selecting a patient from the case list, it would be nice for there  
to be searchable fields that don't actually show up in the table. This is  
now possible: just add a property to your case or referral details and  
choose the "Search Only" format.

- _Date ranges on more reports_. We went through and added support for date  
ranges on a number of the reports. For example, _Submissions by Form_ now  
allows you to choose any date range you want instead of just the last 7  
days.

- _Custom user registrations_. Sometimes you want to collect more  
information from your CHWs than just their username and password. For  
example, you may want to know what district they work in. You can now go  
enter whatever data you choose by using our Custom User Registration  
feature. To enable, in the application's Advanced Settings, select Use  
Custom User Registrations: _Use_. Then on the bar at the right, choose _User  
Registration_. _This feature is still rough around the edges and is most  
suitable for advanced users_. You cannot use the old form designer to edit  
this. Instead you may start with the default that HQ provides, download the  
form, make any additions you want and re-upload it. You must also refer to  
[https://bitbucket.org/commcare/commcare/wiki/CommCareProfile](https://bitbucket.org/commcare/commcare/wiki/CommCareProfile) to make sure  
your form prepares the data correctly.

- _Export cases, referrals, and users_. This new data export feature gives  
you access to your entire patient list (cases), all their referrals, and the  
list of all your CHWs (users) with their meta data. To use this feature  
select the report called _Export cases, referrals, and users_.

Thanks for all your tireless work, and we hope these features can help you  
continue to improve upon these fantastic deployments!

Cheers,  
Danny

p.s. Don't forget to check out two recently announced features:

- _Custom Exports_. When doing a data export, you can now configure a custom  
export that includes only certain fields that you're most interested in.
- _Multimedia File Checker_. This tool looks into your forms to give you a  
complete list of multimedia files (images, audio, etc) that you should have  
in order for your multimedia deployment to work. It also lets you download a  
python script that you can use to check your actual multimedia directory  
against this list and alert you of any missing or extra files. This tool can  
be found the front page of your app under "Multimedia (beta)"

---

<div class="post-metadata">

**Author:** ![Ray\_B](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/ray_b/32/618_2.png) [@Ray\_B](https://forum.dimagi.com/u/Ray_B)\
**Post date:** [November 16, 2011, 10:07pm UTC](https://forum.dimagi.com/t/new-commcare-hq-features/620/2 "2011-11-16T22:07:20Z")

</div>

Hi Danny,

Re: _Search Only format in case list. We've heard from a number of people  
that when selecting a patient from the case list, it would be nice for  
there to be searchable fields that don't actually show up in the table.  
This is now possible: just add a property to your case or referral details  
and choose the "Search Only" forma_t

I'm trying to use the "Search" functionality, but cannot seem to get it  
working. In my scenario, I have a case property called 'community\_name'  
that I would like to be able to search by. I've added this property to the  
CCHQ case details twice: once with 'long' selected and using the '_Plain_'  
format; and once with neither 'short' nor 'long' selected and using the '_Search  
only_' format. While it looks like both of these were saved initially,  
later looks like the second one may have disappeared. Should I be  
attempting to include the same property twice (ie. once to include in the  
detailed case information and once with a 'Search' format), or should I be  
handling this in a different way?

Thanks, Ray

---

<div class="post-metadata">

**Author:** ![dannyroberts](https://dimagi.b-cdn.net/letter_avatar_proxy/v4/letter/d/94ad74/32.png) [@dannyroberts](https://forum.dimagi.com/u/dannyroberts)\
**Post date:** [November 17, 2011, 6:32pm UTC](https://forum.dimagi.com/t/new-commcare-hq-features/620/3 "2011-11-17T18:32:42Z")

</div>

Hi Ray,

Thanks for your probing questions. The desired effect is that you should be  
able to select Search Only for both long and short, and that it would be  
invisible in short but indistinguishable from Plain in long. It looks like  
the code worked imperfectly, but I've made changes and this should be  
working fine now. Let me know if you have any more problems or questions.

Cheers,  
Danny

> **···**
>
> 2011/11/16 Ray Brunsting
> 
> > Hi Danny,
> > 
> > Re: _Search Only format in case list. We've heard from a number of people  
> > that when selecting a patient from the case list, it would be nice for  
> > there to be searchable fields that don't actually show up in the table.  
> > This is now possible: just add a property to your case or referral details  
> > and choose the "Search Only" forma_t
> > 
> > I'm trying to use the "Search" functionality, but cannot seem to get it  
> > working. In my scenario, I have a case property called 'community\_name'  
> > that I would like to be able to search by. I've added this property to the  
> > CCHQ case details twice: once with 'long' selected and using the '_Plain_'  
> > format; and once with neither 'short' nor 'long' selected and using the '_Search  
> > only_' format. While it looks like both of these were saved initially,  
> > later looks like the second one may have disappeared. Should I be  
> > attempting to include the same property twice (ie. once to include in the  
> > detailed case information and once with a 'Search' format), or should I be  
> > handling this in a different way?
> > 
> > Thanks, Ray

---

<div class="post-metadata">

**Author:** ![Ray\_B](https://dimagi.b-cdn.net/user_avatar/forum.dimagi.com/ray_b/32/618_2.png) [@Ray\_B](https://forum.dimagi.com/u/Ray_B)\
**Post date:** [November 17, 2011, 7:49pm UTC](https://forum.dimagi.com/t/new-commcare-hq-features/620/4 "2011-11-17T19:49:27Z")

</div>

Hi Danny,

Thanks. Search is now working as expected -- both with CC-J2ME and CC-ODK.

One suggestion for future consideration: allow the user to enable/disable  
search for all (text?) fields.

Use case: the CHWs we work with cover several communities, and we are  
hoping to have them use the search field to list all patients in the  
community they are visiting. While they can do this now, they would end  
up listing patients from other communities that happen to have a name  
similar to the community name (e.g. "Boston" is both the name of a fine  
city, and was used as a baby name by 118/1,000,000 US babies in 2009).

Also, separating enable/disable search configuration from the format  
selection may be less confusing for some users (like me!).

Cheers, Ray

> **···**
>
> On Thu, Nov 17, 2011 at 1:32 PM, Daniel Roberts wrote:
> 
> > Hi Ray,
> > 
> > Thanks for your probing questions. The desired effect is that you should  
> > be able to select Search Only for both long and short, and that it would be  
> > invisible in short but indistinguishable from Plain in long. It looks like  
> > the code worked imperfectly, but I've made changes and this should be  
> > working fine now. Let me know if you have any more problems or questions.
> > 
> > Cheers,  
> > Danny
> > 
> > 2011/11/16 Ray Brunsting [ray@tula.org](mailto:ray@tula.org)
> > 
> > > Hi Danny,
> > > 
> > > Re: _Search Only format in case list. We've heard from a number of  
> > > people that when selecting a patient from the case list, it would be nice  
> > > for there to be searchable fields that don't actually show up in the table.  
> > > This is now possible: just add a property to your case or referral details  
> > > and choose the "Search Only" forma_t
> > > 
> > > I'm trying to use the "Search" functionality, but cannot seem to get it  
> > > working. In my scenario, I have a case property called 'community\_name'  
> > > that I would like to be able to search by. I've added this property to the  
> > > CCHQ case details twice: once with 'long' selected and using the '_Plain_'  
> > > format; and once with neither 'short' nor 'long' selected and using the '  
> > > _Search only_' format. While it looks like both of these were saved  
> > > initially, later looks like the second one may have disappeared. Should I  
> > > be attempting to include the same property twice (ie. once to include in  
> > > the detailed case information and once with a 'Search' format), or should I  
> > > be handling this in a different way?
> > > 
> > > Thanks, Ray
