DevResults release notes
DevResults release notes
www.devresults.com

Bookmark data tables

Users can now bookmark data tables and easily access them via the Bookmarks menu or via their dashboards!

To bookmark a data table, simply navigate to the table and click on the star icon at the top right corner.

bookmarkdt1.png

The table will now be available in your Bookmarks menu:

bookmarkdt2.png

You can also add a new Bookmark Data Tables tile to your dashboards!

bookmarkdt3.png

More intuitive gear menu

Today our newest engineer (hi Fred!) released a small update to make the gear menu options more intuitive on an activity's reporting period page. Previously the menu referred to a "results template", but it's more accurate to call it a "direct entry template", because it's only used for direct entry indicators. You can read more in our knowledge base about indicator data sources.

Gear.png

Labels on column graphs

Beta testers now have the option to add value labels to column graphs in DevResults. The option is shown in the display panel.

Note: This feature is currently only available to beta testers. Anyone can opt-in to view features in beta testing on the user profile. Once we've ensured that the feature works well, it will be made available to all users.

Show.png

Values appear horizontally if there's enough space for them, and vertically if there's not.

Horizontal.png

Vertical.png

In the future we might explore options to add labels for targets and other visualization types, but it's a complex challenge to ensure proper spacing for an infinite number of text sizes and positions.

Language choices available on login page

Users can now choose their preferred language before logging in. Admins can choose the list languages that appear on the login screen from Administration > Settings.

This update also ensures (for example) that if a French-speaking user sends a link to a Spanish-speaking user, the Spanish-speaking user will see the page in Spanish after logging in.

Login.png

SurveyCTO out of beta stage, available to all sites

We released a beta-version of the SurveyCTO integration last year, and it's now out of beta-stage and available to all sites and users.

To enable the integration, site owners need only go to Administration > Settings, and enable "SurveyCTO integration" in the list of available features.

image.png

Overlays can now be used on all maps

Like map overlays? Wish you could use them on maps besides just the activity overview? Now you can:-) Dashboards, indicator maps, embeds, you name it.

image.png

Multiple columns of the same disaggregation in a data table

Way back when, we limited data tables to include only one column for each disaggregation. The idea was to make it easy for any indicators to pick up on which column a particular disaggregation should come from.

That limitation no longer applies! In other words, you can now add multiple 'sex' disaggregation columns — for instance, "sex of patient" and "sex of caretaker". Or you can add the same set of response categories — "very likely," "likely," "not likely" — to multiple questions in a survey. Sky's the limit!

image.png

IATI background processing for large exports

For long-time publishers to the International Aid Transparency Initiative (IATI) Registry, files with a large amount of historical data and hundreds of activities can take a long time to generate.

If that's the case, you can now enable an "asynchronous queue" that processes large files in the background and emails you when they're ready. Then, when you export IATI files, you'll either get an immediate response for smaller files, or you'll see a message like this:

image.png

Once you get the promised email, you'll see a list of validation errors, or if none, you'll be able to download your IATI file instantaneously.

If you would like to enable background processing for your IATI files, please contact our Helpdesk in your site or at help@devresults.com.

Date Format Options in Forms

The DevResults Forms tool lets you auto-populate documents with your program information from DevResults. For example, with the placeholder [[Activity_Name]] in a Forms template, you can download a document for any activity with the correct name filled out for you.

Background: There are seven date placeholders in DevResults.

  • [[Activity_StartDate]]
  • [[Activity_EndDate]]
  • [[ReportingPeriod_StartDate]]
  • [[ReportingPeriod_EndDate]]
  • [[ReportingPeriod_SubmissionStartDate]]
  • [[ReportingPeriod_SubmissionEndDate]]
  • [[Today]]

Previously, the first six used an ambiguous month/day/year format, such as 2/5/2021 for Feb 5, 2021. For those outside of the US, it's not clear if it's supposed to be Feb 5 or May 2.

Now the default is the unambiguous format used throughout DevResults, for example: 5 Feb 2021. You can now customize the format by defining the format in your placeholder. For example:

  • [[Activity_StartDate:Format=M/d/yyyy]] = 2/5/2021
  • [[Activity_StartDate:Format=dddd, MMM d, yyyy]] = Friday, Feb 5, 2021
  • [[Activity_StartDate:Format=d/M/yy]] = 5/2/21
  • [[Activity_StartDate:Format=dd MMMM yyyy]] = 05 February 2021
  • [[Activity_StartDate:Format=yyyy-MM-dd]] = 2021-02-05

Date codes available to assemble in the format you prefer:

  • d - Day of month with no leading zero (e.g. 5 or 15)
  • dd - Day of month with leading zero (e.g. 05 or 15)
  • ddd - Three-letter day of week (e.g. Wed or Fri, English only)
  • dddd - Full name of day of week (e.g. Wednesday or Friday, English only)
  • M - Month number with no leading zero (e.g. 2 or 12)
  • MM - Month number with leading zero (e.g. 02 or 12)
  • MMM - Three-letter month (e.g. Feb or May, English only)
  • MMMM - Full name of month (e.g. February or May, English only)
  • yy - Two-letter year (e.g. 21)
  • yyyy - Four-letter year (e.g. 2021)

Note: The M's in month codes must be capitalized or else they will represent minutes, which will probably be zero.

Check out our knowledge base for more information about how to use forms.

Disable password-based logins for SSO accounts

You may now disable password-based logins for users that have a single sign-on (SSO) account. This is a handy way to enforce the use of single sign-on for staff while allowing partners and other non-SSO users to sign on as they always have (with their email and password).

image.png