RapidPro 7.4 Released

[Rowan Seymour]

It's here! Big thanks to everyone who chooses to host with TextIt/Nyaruka which makes all this ongoing development possible.

The major focuses in this release were 1) the new UI, 2) enabling accurate previews of flow starts and 3) improving data validity. We'll send a followup email to this one with a preview of what the new UI looks like, and how to opt-in to start using it.

All the stable versions are listed at https://github.com/rapidpro/rapidpro as always.

So here's what has changed...

Contacts

• Add Open Tickets system group to all workspaces which is all of the active contacts with one or more open tickets (i.e. tickets > 0).

• Contact flow history now searchable as history = "Flow Name".

• For consistency with other fields, group = "" and group != "" now work and can be used to find contacts with no groups or any group.

• Allow searching on status, e.g. status = active. Not particularly useful yet since most views implicitly filter by status, but that will become explicit at some point.

• Add scheduled triggers to upcoming event list on contact detail page.

• Fix != "X" query conditions when a field value isn't set for a contact.

• Fix search query simplification so it doesn't generate overly nested queries for repeated boolean combinations.

Flows

• Rework flow start modal so that all options affect the preview and predicted count of contacts. This has been implemented by turning everything into a query under the hood and ensuring that all options used on that modal are queryable.

• Require flow names to be unique so they can be reliably used in search queries. Existing flows with non-unique names are fixed via a migration.

• Start Somebody Else actions now generate an error event if specified flow is missing.

• Added concat expression function for joining arrays.

• Change groups, globals and subflow dependencies in flows to be soft - i.e. you can delete them and flow is marked as having issues. All flow dependencies are modelled like this now.

• Fix language selection for WhatsApp templates where contacts don't have a language set.

• Fix Call Webhook actions so that trailing whitespace is trimmed from URLs.

• Fix failing when session exceeds resume count limit so that no runs are left in active state which causes problems later for archiver.

• Fix uploading of message attachments when filename contains spaces.

Channels

• Add support for Cloud API WhatsApp as a new channel type. 

• Instagram channels no longer beta users only.

• Add support for stopping contacts in response to a status callback with a stop notification (currently only Twilio and Telegram do this).

• Add support for URL previews in WhatsApp messages.

• Enforce workspace limit on channels (default is 10, can be overridden per workspace).

• Improve attachment type detection.

• Fix not being able to delete Facebook channel when credentials are no longer valid.

• Fix Start Mobile to use latest API endpoint.

• Fix stopping of Telegram contacts for certain send errors.

Tickets

• Add support for attachments (images, video and audio) on incoming messages in ticket chat view.

• Start tracking activity counts - tickets opened, assigned, response time etc.

• Add endpoint to generate Excel export of daily ticket activity counts.

API

• Add status to contacts endpoint.

• Add modified_on to tickets endpoint.

• Add indexes for fetching tickets via the API.

Indexing

• Significant refactor of indexer to enable more controlled shutdowns and make it much easier to add support for indexing other things in the future (e.g. tickets).

• Add analytics: number of contacts indexed etc.

• Make indexer's polling interval configurable.

• Replace several UUID based fields with ID equivalents to reduce elastic search storage.

• Fix handling of invalid numerical contact fields so that the rest of the document is correctly indexed.

Archiving

• Add analytics: number of records archived etc.

• Fixed archiver scheduling so that archiving starts at configured time after launch.

• Fixed performance issue doing monthly rollups when archives table has gotten large.

• Improved archiver logging so that we output less when configured level is info.

Miscellaneous

• Performance improvements on pages which check user permissions.

• Add scheme column to flow results exports for anonymous workspaces.

• Add flow name to message exports.

• Add Service button to workspace update page.

• Add support for shared usage workspace plans.

• Add database constraints to prevent sessions without output or output_url, or waiting runs without sessions.

• Enforce uniqueness of message label names. 

• Fix searching on calls list page.

Developer Notes

• This is the last release which will support topups and it's planned to remove that code before the next release.

• All Go services now use an analytics abstraction layer to enable easier integration of different analytics backends.

• All Go code updated to 1.18.

Deployment Notes

• rp-archiver config option -exit-on-completion replaced by –once which makes it run once immediately and then exit.

• All Go releases have ARM64 builds.

• Supported PostgreSQL versions are still 12 and 13.

• Supported Redis version is still 5.0.

• Supported Elasticsearch version is 7.17 (last of 7.x series).

[Gift Marimo]

Thanks for this great,

I upgraded to RP7.4.2 but for some reason, I can't see the WhatsApp Cloud API. How can I see it under my channels?

[Rowan Seymour]

That channel type is still beta gated for now whilst we iron out any last bugs, so either add users to the Beta user group or modify temba.channels.types.WhatsAppCloudType.beta_gated in your own fork.

-Rowan

--
You received this message because you are subscribed to the Google Groups "rapidpro-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rapidpro-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/0071aaeb-b647-43de-837d-38247eb8b579n%40googlegroups.com.

[Gift]

Ok, thank you so much for the clarification. 

[Gift Marimo]

Hie.

Is WhatsApp Cloud API Channel still on Beta gated? if so when is it likely to be included on Stable Release?

[Rowan Seymour]

We'll likely find some way to gate it because it's not going to be an option for all deployments yet, but next stable release (Nov) will probably remove the beta user gating.

[Andre Lesa]

Hi

When are we going to have WhatsApp cloud API on Nyaruka hosted Rapidpro. 

To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/CAAwM7XAdBC8U5iAGyO9C9nnkBf2Vk%2B0SpQKbRG5fvY3aGjT9GA%40mail.gmail.com.

[Rowan Seymour]

The issue there is that we have no support in TextIt for tracking and billing WhatsApp cloud usage. We might open it up to organizations with fee-waivers from WhatsApp or explore if there is a way to let users set it up with their own line of credit. I think last we checked it wasn't completely clear what was possible there.

-Rowan

[Andre Lesa]

Hi Rowan,

Thank you for that. Understood.

Regards 

To view this discussion on the web visit https://groups.google.com/d/msgid/rapidpro-dev/CAAwM7XDPcU7sL%2B%2B9-FwUZN1HO0qMDL%2BEb-txOmv8GEsWyMhB2Q%40mail.gmail.com.