The biggest releases of 2025 and 2026, and every change back to 2019.
Updated October 28, 2026 from our code, roadmap and release notes.
Helping every organization and every user put the full power of CommCare to work, from AI that understands the page you are on to data that flows straight into your own tools.
The new Bulk Form Action API lets you archive or delete up to 5,000 forms with a single API request, and unarchive forms you archived earlier. Each request starts a background job, and the API gives you a status link to follow the job until it finishes. Read more in the Bulk Form Action API documentation.
Big releaseThe CommCare Companion, the AI assistant in CommCare HQ, now uses the page you are working on to answer your questions. Starting with the App Builder pages, the Companion receives the page you are on, your project space, and your role, so its answers match what you are looking at.
Version 1.16.0 of the CommCare Data Export Tool can export your CommCare data as Delta Lake tables, which Databricks, Microsoft Fabric, and Azure Synapse can read directly, so teams that analyze data in those platforms can keep their CommCare data up to date there on a schedule.
The new Face Capture question type helps frontline workers take a photo of one person's face, for example for an ID card or a profile photo. On CommCare Mobile 2.64 and later, CommCare shows the worker where to position the face and then takes the photo automatically. Read more on the Media Capture Questions wiki page.
App builders can now lock specific questions and groups in the Form Builder so they cannot be edited, moved, or deleted by users who do not hold the new locked questions permission. This protects critical form logic, structure, and case mappings while still allowing the rest of your team to make everyday edits.
Advanced Case Actions now enables a single form to create, update, index, or close related cases. The capability previously required a feature flag that had to be requested along with a dedicated training session. Alongside this release, we redesigned how case management is configured in the Form Builder.
Geospatial projects got a meaningful upgrade this quarter on both mobile and HQ. On CommCare Mobile 2.62, mobile workers can now see administrative boundary overlays directly on case list maps, making it easier to understand where cases sit relative to the geographic areas your program cares about.
A project space admin can now enable messaging for their own project space, rather than having to contact support to have it enabled via the internal account settings form.
Bulk user upload no longer lets a project exceed its plan's mobile worker limit when the plan doesn't allow excess users. Previously the limit was only enforced when creating or reactivating a single mobile worker in the UI, so uploading users bypassed it.
Introduces a new Pragma to enable "Dense Mode" for forms:
CommCare HQ now requires new passwords to be at least 14 characters long, up from 8.
Before (potentially overlapping with form information):
When you copy an app to another project space, CommCare now also copies the lookup tables the app uses and lists them in the confirmation message.
A form whose create action updated a case that already existed can now be archived, as long as no later form has changed that case.
A case list module that has Select Parent First turned on keeps pointing at the parent case list after that case list is deleted. Opening the child module's settings page then failed with a 500, so the builder could not open the page to fix or turn off the setting.
Currently, when a user tries to downgrade from an annual plan, the "Next" button is already disabled, however user can manipulate the DOM to remove the disabled flag of the "Next" button and proceed with the downgrade.
The Report an Issue modal retained values from the previous report after it was closed and reopened.
You can now copy an app from a linked project space to its upstream project space, which was previously blocked.
A web user whose role has neither the Edit Applications nor View Applications permission can currently open any App Manager page (app, module, form, settings, releases) by navigating directly to its URL.
GPS questions in Web Apps no longer display or save longitudes over 180 degrees.
Will no longer send monthly invoice emails to customers on Pay Annually subscriptions when that monthly invoice has a $0 balance at generation (e.g. it was fully paid by credits).
Prevents project spaces without the correct privileges from being shown as eligible Linked Project Spaces in MRM/ERM choices.
Adds a Cloudflare Turnstile form field that, when keys are correctly set, can be used to verify a user before a form is submitted.
The Applications tile on the project dashboard now has a + button that opens the New Application page.
- Using a domain-scoped OAuth token to access the list_domains endpoint now returns only the domains that token can access, in line with how we handle domain-scoped API keys.
Enterprise customer shouldn't see this low credits alert because their renewals are handled differently, and at an HQ level.
Makes OAuth authorization requests ask for domain scope - allows selection of any number of project spaces but removes the implicit "all domains" access that this page used to apply.
Replaces the generic OAuth request template with one styled for CommCare
CommCare Mobile 2.64 was released in August, followed by a 2.64.1 update in September. Along with the Face Capture question described above, CommCare Mobile 2.64 includes a redesigned audio recorder, a framing guide for photos, and more accurate automatic location capture.
In the Repeat Records report, clicking Payload previews the payload of a repeat record. Until now, if the underlying form or case had been soft deleted, its data was still fetched and shown in the preview modal.
There was a bug with the record status filter on the repeat record report. In code, it mentioned that the success and empty states were combined in the UI, as were the payload rejected and error generating payload states.
Replaces links to the Confluence wiki pricing page and the old CommCare page on dimagi.com with the new CommCare website's pricing page.
This PR updates the pricing link in the documentation to point to the official CommCare pricing page ( instead of the confluence page
Adds two new metrics to the feature usage metrics reported in Salesforce. They track whether users have exported a report ("cp_n_enterprise_console_exports"), or changed a setting ("cp_n_enterprise_settings_edits").
The form settings page in App Manager moved to our current UI framework, with cleaner layout and more consistent styling.
"Select Parent First" on a child case's module is supposed to ask the user to pick a parent case, then narrow the child list to that parent's children. Today it only works when the child case is indexed under the reference id parent.
Migrates the app_manager form view (form_view.html) from Bootstrap 3 to Bootstrap 5. User-facing effect is layout/styling parity with the B3 version — visual changes are intentional B5 equivalents.
Web users who sign in through SSO now always need an API key for API access.
A new version of CommCare Mobile (2.63) is on the Google Play Store, followed by a 2.63.1 patch release. This release focuses on form entry reliability and stability during case loading. See the 2.63 release notes for the full list.
Fixes a bug where clicking the Print button in web apps would break breadcrumb navigation. No visual changes.
The "Enable All Add-Ons" button in App Settings is now disabled when every add-on is already enabled.
A fix for the bulk-user api returning all users instead of filtering for valid users when using query string.
The Edit Form Details modal now lives inside the Form Builder, and changes to a form's name and comment save together with the rest of the form.
Update user facing text from "Save to Case" to "Advanced Case Actions" since we renamed this feature
A new version of CommCare Mobile (2.62) is on the Google Play Store. Beyond the geospatial improvements called out above, this release focuses on stability and reliability on newer Android versions, alongside a handful of meaningful bug fixes. See the 2.62 release notes for the full list.
Improves the user-facing alert shown when a case property mapping is concurrently changed and deleted in separate sessions — the wording is now clearer about what happened.
The API rate limiter no longer applies a weekly window.
Case API v2 now supports "fields" and "exclude" query parameters, so API consumers can trim responses down to exactly the data they care about. This makes integrations faster and payloads smaller, especially for cases with many properties. The full API reference lives in the CommCare API documentation.
Fixes two bugs in the /api/v0.5/user_domains/ endpoint:
Forms with emoji fail to save when reordering question lists. This is the server-side companion to the Vellum fix.
This reverts parts of commit f4df216e2a42761fd78d9729f8911d18553f5dc9. The search box for searching in case db search should not have been removed The persistent menu should still behave differently when split screen case search is enabled * Use sidebarEnabled instead of…
Email confirmation invites for mobile workers now expire after 72 hours instead of 24, giving field teams more time to confirm their accounts without needing an admin to resend.
The user_domains API currently only includes domains that have the 'ZAPIER' privilege. This PR removes that restriction so that the API returns ALL domains the user is a member of.
A trailing space in the API key display has been removed so keys copy cleanly.
SSO users attempting to use basic authentication on API endpoints now receive a clear, actionable error message directing them to use API key authentication instead.
Add validation so that if a save to case question want to create a case but doesn't provide case_type and case_name will not be allowed to make new version.
This change adds metrics to track usage of advanced app features, so that they are available to Salesforce.
We are continuing a long-running effort to modernize the HQ interface under the hood. This quarter, several of the most-used pages in App Manager were migrated to our current UI framework: the Releases page, App Settings, App Summary and a number of smaller screens.
Users can now select multiple recipient types when configuring Connect Messages and Connect Surveys, rather than being restricted to only mobile workers. The system validates that selected recipient types are compatible with Connect (i.e., they resolve to CommCareUser…
Move case search workflow settings and related configuration behind new FFs.
Configuring roles in CommCare used to happen in a cramped modal that made managing permissions for larger projects tedious. We have now rebuilt the role editor as a full standalone page, giving admins the space to see every permission at once and the breathing room to configure more complex roles without scrolling…
Adds this error message when subscribing to a plan if an autopay card is required and has not been added - and somehow frontend validation has been bypassed:
Before: As shown in the video: The delete button will have 3 spinners
The form attachments area has a cleaner layout that is easier to scan when a form has many attachments.
Web users and mobile workers with view permission on the user lists can now download the lists, a permission that previously required edit access.
CommCare HQ now uses just 4 feature flag tags:
Before: - no overall error notification - 'next error' is always below the submit button and also it does not work - 'submit' spinner never disappears
Adds documentation for the new DET Exports API. The API was added for CommCare Data Pipeline, to be able to list the Case and Form Exports available, and to download their config files automatically.
Makes markdown tables with many columns scroll instead of wrap. This does not prevent wrapping of table cells entirely - they will still break at appropriate locations between words. Before:
- Adds four new formats in the case list config section for display properties. 1. Geo Boundary (requires Address) 2. Geo Boundary Color (requires Geo Boundary) 3. Geo Points (requires Address) 4.
A new version of the CommCare Data Export Tool is out. Version 1.14.0 focuses on performance and observability: CSV exports now use significantly less RAM, which means they run faster on large projects and are far less likely to hit memory limits.
Teams faced shrinking budgets and growing needs, so we built CommCare around what they needed most: faster and easier ways to get work done.
Big releaseStarting now, new CommCare projects can be hosted in three secure regions: the EU (Ireland), India (Mumbai), or the US (Virginia). This flexibility supports internal policies, funder conditions, or team data preferences, all at the same price and features.
Big releaseWe are excited to introduce the CommCare Companion, an AI-powered chatbot designed to assist you directly within CommCare HQ. Whether you need help building an app, managing cases, or troubleshooting an error, the Companion provides real-time guidance and answers to help you work more efficiently.
Big releaseIn May, we released our first ever bulk in-product data editing tool for cases! This tool allows you to make bulk case data editing without having to export cases then re-import them! This takes Excel files out of the equation, and provides a beautiful new interface to perform one update or thousands.
Big releaseWe've made a number of improvements to CommCare HQ, ranging from the Form Builder, to the Report Builder, and Case Management. See more about each below!
In April, we released an update to our Standard Plan to reduce the price from $250 to $100 USD per month paid annually. We believe that cost shouldn't limit our partners from being able to run impactful, digitally enabled programs around the world.
Fixes a bug where autopay card appears as undefined on the enterprise billing statements page, whether there is an autopay card set or not:
Disables Cancel and Subscribe to Plan buttons on submit when confirming signup for a new subscription:
Remove unused case tile templates. We want users to use the manually configured case tiles. Remove all templates that are not used by a production app.
Adds text showing the customer their next scheduled autopay date, when autopay is enabled and there is an invoice due in the future:
Fixes two related bugs where users could not make a bulk payment on the Billing Statements page with an unsaved card: - when the customer had no saved cards, they would see a "Your card number is incorrect" error - when the customer had any saved cards, they would see…
We are enhancing role-based access control by introducing the ability to limit which user profiles a web user can assign to others. Previously, any user with permission to edit users could assign any profile.
- Requires customers subscribing to Pay Monthly subscriptions to add an autopay method. - Updates the "invoice reminder" notification to 1 day before the due date and includes information about autopay, if applicable.
Non-superusers will see the ToS modal once and must click "I agree" to continue using CommCare HQ. This can appear on either a Bootstrap 3 or Bootstrap 5 page with slightly different appearances.
Collapsed, billing information page:
Makes auto-renewal feature generally available and allows it to be set as the default for user-created subscriptions with end dates. Removes an older subscription reminder email that is replaced by newer auto-renew emails.
Release Location Columns In App Status Report feature flag as GA (generally available) to advance and up. Improvements were made to the feature in to get it ready for GA.
Removes the current Cloud Location dropdown in the "Create Account" form fields. Adds a "Choose Cloud" step before entering user information in signup. When a location different from the current one is selected, it will navigate directly to the "Create Account" step in that…
We have released a new version of CommCare Mobile on the Google Play Store: 2.60.0. This update focuses on modernizing the app interface for the latest devices, improving update reliability, and ensuring greater stability for mobile workers.
We are excited to release a significant improvement to the web user invitation workflow. Previously, inviting a user only allowed you to select a profile. Now, the invite page offers the same flexibility as the "Edit User" page, allowing you to define individual user fields and permissions directly during the…
We are introducing a powerful new way to ensure your project data remains high-quality and standardized. You can now define specific data types for your case properties directly in the Data Dictionary, enforcing validation rules whenever cases are imported.
We have expanded our data export capabilities to support GeoJSON, making it easier than ever to integrate CommCare data with GIS systems like ArcGIS. This new export format allows you to extract case data along with its geolocation properties in a standardized file format, streamlining geospatial analysis and mapping.
We updated our Terms of Service to streamline operations and ensure a smoother billing experience for all customers. Beginning December 11, 2025, new and renewing subscriptions began following an updated renewal process designed to prevent service interruptions and simplify payment management.
Update the help link for custom icon badges to the new public link,
We are excited to introduce Custom Icon Badges, a new feature that brings high-level insights directly to your application's home screen. Now, mobile workers can view critical data, such as the number of active cases or pending reviews, right on the module or form icon before they even open it.
At present, case lists in web apps will only save the column configuration if the path to get to the case list doesn't involve selecting another case first (this is a bug). This change makes child case lists save the config too
Addresses a likely cause of
Upgrade the OCS chat widget:
Catch validation in CSQL parsing (case search and/or case list explorer)
Prevents users from deleting a profile that is assigned to an open invitation, just as they are prevented from deleting a profile assigned to an active user.
Move the profile field to its own section to make it more obvious that it is not just one of the other user fields Make the "Additional Information" and "Unrecognized Information" sections collapsible * Fix "Unrecognizable Information" section on user invites was not showing up…
Allows Customer Invoices (for "customer billing" accounts) to be autopaid. There's no user-facing (customer or accounting admin) indication this wouldn't work, so likely it was just never implemented.
We received feedback from ops to hold off on fully requiring autopay for monthly accounts until we update our terms. This softly rolls back that change for an easy revert when the terms are ready.
In a recent PR I moved the profile field to its own FieldSet. That meant that custom-data-fieldset was not set on an ancestor node of the fields anymore breaking the knockout bindings.
Adds the ability to pay with the autopay card on file for the account in payment modals (even when current user does not own the card).
This PR updates the confirm billing info step (3rd step) when signing up for a new subscription: - Most crucial billing information fields are now required in order to subscribe: first_name, last_name, first_line (of address), city, postal_code, country.
The project settings form is currently raising a 500 because the form is trying to render a field (enable_all_add_ons) when it was deleted due to a lack of privileges.
This adds the status of whether autopay is "enabled" or "not set", with a Manage link after linking to the Billing Information page where folks can manage the autopay method.
There was a bug where elements that use data-binding slideVisible show the sliding animation upon page load or element creation.
This adds a new section called "Account Autopay Card" to the Billing Information page, which shows the current autopay for the account (or an alert if none selected), regardless of the owner of the autopay card.
Mobile worker email invites will expire after 24 hours, rather than 1 hour.
When bulk uploading web users, locations get removed from invites for new web users when the upload does not contain location column(s). In such a case, instead, no updates are expected for the location information on the invites. This PR fixes that bug.
Mostly applies in emails; anywhere the address is used it has been updated.
There was a bug where clicking on a repeat group's "delete" button would trigger the group's collapse/uncollapse, and then it would delete the group. This resulted in a weird UI behavior. This PR fixes that bug so that the group does not collapse/uncollapse upon deletion.
This PR fixes a bug where the help message is blocked by the navigation menu on web apps.
Just a minor change to fix the help link for web user bulk download/upload which was originally pointing to the one for mobile users and then also update the one for mobile users so it goes to the intended hyperlink on the page.
There was a bug where if markdown is used for a question display text, it would result in the required asterik being displayed on the next line instead of inline.
The core change (replaced usercase_enabled flag checks with privileges.USERCASE) does not have user facing effects.
A bug fix to clean up location data on user case when a user is removed from all locations with no assigned locations and no primary location.
We've simplified and standardized the authentication process for all CommCare APIs. We're happy to announce that now all CommCare APIs support using your API key as the password when authenticating via Basic Auth.
This change allows commcare-user to be defined as the case type. When it is used, a warning message is displayed that notifies the user that it is a reserved case type and refers the user to the docs.
Enable usercase automatically on upgrade
The previous wording asked a user if they wanted to "mark this case property as deleted", suggesting it was a status, similar to deprecation. Because deleting a case property entirely removes the property from the data dictionary's knowledge, I updated the wording to try to…
Before: In Project Settings > Internal Data ( Dimagi Only ) > Project Information This is default to "Yes"
GAing two feature flags: * EMWF_WORKER_ACTIVITY_REPORT * WEB_USERS_IN_REPORTS
Adds a loading spinner for the main content of the Data Dictionary when loading the page:
When performing exports, the Project Data filter was not performing as documented. According to the documentation, Project Data, by default, should exclude Web Users. Instead, specifying only the Project Data filter would display Web User cases.
Updates the error shown when a username is already taken Before:
The Date Range filter in report is offset by an extra day for users in a timezone behind UTC. For example: 1) when checking the worker activity report on April 16th, we expect the default range to be April 9th-16th. Instead we see April 8th-15th.
This change allows users to select the email addresses of web users when emailing a report.
The User Case Property is now sorted in alphabetical order.
Simply change the requests for access to messaging feature to be received on email address configured for accounts instead of sales.
Following the major UI update to CommCare Mobile, we're excited to bring the same modern look and feel to Web Apps and the App Preview feature. This visual refresh aligns these platforms with Dimagi's updated brand, creating a more cohesive and intuitive experience for all users.
We're excited to release a powerful security enhancement for user management. For mobile workers with an email address, project admins can now trigger a password setup link directly from the user's profile.
We've made managing web user access much more flexible. Previously, if you needed to temporarily remove a user's access, you had to delete their account and manually re-add them later, losing all their settings.
We're excited to extend a powerful feature—previously available only for mobile workers—to web users. Every web user will now have an associated commcare-user case, functioning identically to the user cases for mobile workers.
We have released two new versions of CommCare Mobile on the Google Play Store: 2.58.0 and 2.59.0. These updates ensure compatibility with the latest Android OS, introduce a new navigation menu, and include a number of bug fixes and performance enhancements.
Uses flag graphics instead of emojis so they will display consistently across operating systems and browsers.
Changes text from "CommCare HQ" to "CommCare" in too many places to include all of them here. Some specifics are called out in the ticket.
Allows "Step 1 of 2" etc. to be translated correctly, as in the signup form:
Fix a bug with the image upload question type in web apps
CMC: Manual Deactivation of Web Users Releases the DEACTIVATE_WEB_USERS feature flag, allowing web users to be deactivated by individual projects. This deactivates them only on that project, not site-wide.
For an Image Upload Question, the user is no longer able to select a "pdf" to upload.
Right now, raising the SingleSignOnError error shows the standard 500 page. This makes it look like the issue is on our end, when it is really an SSO configuration issue.
Fixes an issue where the display language could change partway through 2fa login, and also ensures logging in from any source (including SSO) will set the display language to the user's account language.
Before We used to default api key's scope to all projects this web user has access to
I discovered that the multiple choice filter value select2 only worked when the case property was marked as "multi select" data type in data dictionary. If the data dictionary isn't set up to mark data types for case properties, the input never gets activated with select2…
This PR introduces functionality that restricts users from adding new domains to feature flags (FFs) if they do not have edit permissions.
Changes the numeric inputs in web apps to use numeric keyboards when viewed on mobile devices. Here are text, integer, phone number, and decimal input types as displayed on my Android phone. Previously these all rendered with the same keyboard (the one used by text input)
Adds a user facing app setting for the cc-gps-auto-capture-accuracy setting, which has existed in the mobile app for a very long time but previous required a flag (the generic "set custom properties" one) to access.
Some company or organization has a long name, raise the limit to 100 characters.
Sets a new web user's language in HQ upon creating their account, which will be able to be changed prior to login with #36733
These fields under contact information are not always relevant for every customer since address formats can change from country to country. Make it to be not required.
This is just some clean up commits: - move files - rename functions to be more descriptive - change text - change translate tag
This PR is to add the third step in the import app workflow — show user how to import multimedia from the source app to the new app.
Mobile workers (belonging to domains that use TWO_STAGE_USER_PROVISIONING) will get a confirmation email after successfully confirming their new accounts in the domain.
This PR removes the old page for importing an app from another server. The old page was a single page that could only be accessed by manually entering the URL in the browser’s address bar.
Users will now be able to see 2 new events in the User History Report:
🐠 Review by commit because there is one prettify html commit.
This addresses the issue described here:
Sorting case property groups in the Data Dictionary UI did not work right - changes to ordering were neither reflected immediately in the UI nor applied correctly on page load. This aims to fix that. Before:
User account level settings
Defaults to "Pay Annually" on the Select Plan page unless a customer is already on a paid monthly plan.
When printing forms in web apps, makes the appearance of checkbox and radio buttons match what appears in the browser. Before:
This PR adds a "View Submissions" button to the form designer that will take user to the form-specific submission history. It dynamically generates a filtered SubmitHistory report URL with form-specific parameters and date range filtering.
Allows limited plan changes when moving from a Pay Annually software plan: a move to Pay Monthly or Pay Annually of a higher edition are allowed. Prior to this, no changes from Pay Annually plans were allowed.
Now all users on paid subscriptions can choose to pay annually instead of monthly which unlocks lower pricing! No need to talk to our Sales team, this can now be done by going to Settings → Current Subscription → Change Plan in CommCare HQ.
Enables selecting a Pay Annually plan instead of directing users to "Talk to Sales" and adds a contact section on the Select Plan page. Before:
There's a javascript error triggered in the case list/details tab of the menu settings page when you try to interact with a property that uses icons.
This is generated by running vellum-to-hq script for
This PR adds description attributes to reports, with description attributes, the report navigation column will show a tooltip when hover over. It also renames "Application Status" report to "User Last Activity Report"
Now you can add multimedia and file upload type questions to Web Apps! Read more about it here.
CommCare HQ now alerts users directly on the page if the number of case properties has the potential to affect the performance of apps.
Work seamlessly in your preferred language. CommCare HQ now offers always up-to-date, AI-powered translations in 9 languages. The supported languages are:
CommCare Mobile got two updates in this quarter! Among various bug fixes, we released the ability to log into CommCare via PersonalID, a new, more secure way to log into mobile applications.
Release Bulk Edit Case Data tool to Advanced plans and above.
A small change that disables enabling feature flags during copying app from the modal. The modal just shows the list of feature flags with a link to project's feature flags settings page.
Sends out a prepayment invoice for the length of the subscription when a customer signs up for a new Pay Annually subscription.
Previously the loading indicator would show up in the middle of the table. This means that the user will not see the loading indicator if the table is very long.
Changes a link on prepayment invoices:
In the rare circumstance someone manages to schedule a downgrade of their subscription when one is already scheduled (normally future subscriptions are cancelled first), this message would have given an "incomplete format" error and likely shown a 500.
This PR partially GAed feature flag WEB_USERS_IN_REPORTS.
Adds a new disclaimer blurb and requires confirmation when a user selects to sign up for a Pay Annually plan. This is not possible through the UI as of yet, but will be soon.
Filter definitions hyperlink for User(s) and Case Owner(s) is broken. Kai noticed and requested here.
Changes wording from > Please note that you have reached 65 mobile users, the maximum user limit included in your plan.
If a permission entry did not exist in the database, it was previously assumed that all superusers would have access to edit the feature flags under the tag. This was done to ensure that superusers would retain the same access after deployment unless modified.
GA use of multimedia for web apps. See CMC
Fixes a bug introduced in where CLE export to excel fails.
Prevents an error when generating app status report when location name has special characters.
Discussed in product channel to update the text of dropdown placeholder
Adds zero-width spaces after underscores in custom data field labels, for better line breaks on long names. Before:
When user click on "Case List" to create a new Case List Menu, we ask user to define the case type in the next step.
Renames Community Edition/Community Plan to Free Edition (almost everywhere) in HQ.
Update this pagination to only show if there are multiple pages:
Hides the following for customers not on an Enterprise software plan: - "Pay By Wire" button on Subscription > Billing Statements page - Information about wire payment in emails for invoices, customer invoices, and invoice reminders - Wire payment, flywire, and ACH details on…
Adds a tooltip for the app settings button.
Visual and text updates to the "Select Plan" and "Confirm Plan" pages, specifically: - adds "free edition" plan card, only when currently on that plan - removes "Community" blue banner that would appear when currently on that plan - updates descriptive text for all plans - swaps…
Adds a tooltip to the case property header within a form's case management page
Updates the Generate Prepayment Invoice form with several new fields and uses these when generating the associated invoice.
For prepayment invoices only: - Don't show "Credit" line at bottom of invoice - Do show statement period (as "Prepayment term")
- Make "Edit Form" a secondary button
Android code will truncate the patch version if the version is 'x.y.0', so it becomes 'x.y' This results in the commcare_version we collected in hq is not consistent. Sometimes it is 'x.y.z', sometimes it is 'x.y'.
Adds a new email reminder to billing admins 7 days before an invoice's due date, if the invoice is not yet paid.
Added a border to App Summary and Case Management button to make it more like a button.
Shrinks and centers icons on the HQ dashboard and keeps them the same size regardless of window width.
This PR adds 2 missing comparison options to advanced date filters, as shown below:
Changes the two-factor setup field to use a text input.
Makes the Dashboard navbar link visible on projects that don't have any applications. This is particularly relevant because new projects no longer have default template apps and therefore wouldn't see this link, which may be confusing for new users trying to navigate the…
Makes app version comment box wider, left-aligned, not overflow on small screens (relevant now that the box is wider), and fixes the 2px vertical jump when clicking into the box. Before:
Adds a warning that deleting this mobile worker "Will delete all cases owned by" the user and any forms associated with those cases:
Swaps out one build label (pulled directly from the version number) for another (using the intended-to-be-human-readable name), to show notes like "dev" that are added into these labels.
A bug was preventing Norwegian-locale users from entering dates into CloudCare. This PR updates the date format to better accommodate non-US dates by changing the date format to be ISO-standard.
Persistent Menu Navigation in Web Apps enables users to set up a navigation sidebar, allowing easy access to menus and forms within an application. This feature is particularly beneficial for applications requiring frequent navigation across multiple menus and forms.
In addition to the new APIs, the Enterprise Console just got more robust with information about:
This updates the CommCare flower logo and dimagi logos to their new versions across HQ. This is a revert of the revert of this PR opened a year ago:
CommCare Mobile just got a major user interface update! The new, modern UI showcases Dimagi's refreshed brand, softer color palette, and more user friendly buttons & icons.
Nothing matches yet. Try another word, or see what’s coming.