# What's new in medic-conf 3.2.0

**URL:** <https://forum.communityhealthtoolkit.org/t/whats-new-in-medic-conf-3-2-0/732>\
**Category:** Releases\
**Tags:** configuration, release\
**Created:** [April 23, 2020, 1:35am UTC](https://forum.communityhealthtoolkit.org/t/whats-new-in-medic-conf-3-2-0/732 "2020-04-23T01:35:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gareth](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/gareth/32/62_2.png) [@gareth](https://forum.communityhealthtoolkit.org/u/gareth)\
**Post date:** [April 23, 2020, 1:35am UTC](https://forum.communityhealthtoolkit.org/t/whats-new-in-medic-conf-3-2-0/732/1 "2020-04-23T01:35:01Z")

</div>

The latest version of the medic-conf CLI tool is now [available on npm](https://www.npmjs.com/package/medic-conf).

New features include prompting before overwriting configuration, only uploading configuration if it’s changed, and a new bulk-edit contacts action. We also fixed a range of bugs.

Read the [release notes](https://github.com/medic/medic-conf/blob/master/release-notes.md#320) for full details.

---

<div class="post-metadata">

**Author:** ![Max](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/max/32/112_2.png) [@Max](https://forum.communityhealthtoolkit.org/u/Max)\
**Post date:** [May 19, 2020, 1:28pm UTC](https://forum.communityhealthtoolkit.org/t/whats-new-in-medic-conf-3-2-0/732/2 "2020-05-19T13:28:02Z")

</div>

Medic-conf 3.2.1 was released (thanks @gareth!) . This fixes one bug where task generation would fail for reports with no contact.

> <https://github.com/medic/cht-conf/issues/325>
>
> To reproduce
> 
> 1. Upload declarative configuration with a task that has \`applie…sToType\` defined
> 2. Create a report that doesn't have an associated person or place
> 3. Load the tasks tab
> 4. Error loading tasks
> 
> \`\`\`
> inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3 Error getting tasks for all contacts TypeError: Cannot read property 'type' of undefined
> at i (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:15288)
> at e.exports (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:17014)
> at Object.eval (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:6054)
> at n (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:397)
> at eval (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:1189)
> at n.anonymous (eval at \<anonymous\> (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3), \<anonymous\>:5:1198)
> at n.fire (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3)
> at n.fireNext (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3)
> at n.callNext (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3)
> at u (inbox.js?\_sw-precache=efde4a014d3edf17f489717a82f889b2:3)
> \`\`\`
> 
> This is a supported use case and elsewhere in the code we handle it gracefully.