{"componentChunkName":"component---src-templates-blog-post-js","path":"/blog/2026-09-30-september-release/","result":{"data":{"site":{"siteMetadata":{"siteUrl":"https://avniproject.org","twitterHandle":"@avniproject"}},"post":{"id":"2057a16e-429e-51e2-acdc-bb73bfa1aaf9","html":"

Approval and Rejection forms

\n\n
\n
\n \"An\n
\n
\n

Turn approval decisions into data you can count

\n

Rejecting a record used to mean typing a sentence into a comment box. The field worker knew what to fix, but nobody could count those sentences.

\n

Now an organisation can build an Approval form or a Rejection form in App Designer. In the mobile app, tapping Approve or Reject opens that form instead of the comment box. The field worker whose record was sent back sees the approver's answers where the comment used to appear.

\n

→ View technical details

\n
\n
\n\n
\n
\n
\n \n \n \"A\n \n
A summary screen listing submissions as Approved or Rejected, with the reasons for each rejection shown beside it
\n
\n
\n
\n

See why records are sent back

\n

The answers flow into reports and integrations like any other form data. If the Rejection form asks for the reason as a list of options, a program manager can count how often each reason comes up.

\n
\n
\n
\n
\n

Set it up in App Designer

\n

Build the form, then attach it to anything that already has approval switched on. Follow the steps in Approval and rejection forms in the Avni docs.

\n
\n
\n

Rules work here too

\n

The rule builder in App Designer works on Approval and Rejection forms, so you can hide or validate questions without writing code.

\n
\n
\n

Optional and backward compatible

\n

Either form can be attached on its own. Where no form is attached, approving and rejecting work exactly as before.

\n
\n
\n
\n

Minor enhancements

\n
\n
\n

Buttons no longer hidden on Android 16

\n

On Android 16 phones, buttons at the bottom of the screen, such as Apply on the Filter screen, were drawn underneath the phone's navigation bar and couldn't be pressed. They now sit above it and work again. (avni-client#2114)

\n
\n
\n

Clearer media sync errors

\n

When a photo or other media file stopped a sync, field workers saw only an error code. They now see a readable message, and the sync is recorded as failed rather than incomplete, so it's clearer what went wrong. (avni-client#2097)

\n
\n
\n
\n

Performance improvements

\n
\n

Attendance report refreshes in about a minute, not hours

\n

For organisations that track attendance, refreshing the attendance report used to take one to two hours. It now takes under a minute and a half. The report's contents are unchanged. (avni-etl#175)

\n
\n
\n

Share Feedback and Stay Updated!

\n

Join our Avni community on Discord to share your thoughts, ask questions, and get the latest updates.

\n

Need a walkthrough or have questions? Feel free to schedule a demo call here.

","frontmatter":{"date":"September 30, 2026","title":"Avni September Release","author":"Avni Team","description":"Structured Approval and Rejection forms, a fix for hidden buttons on Android 16, clearer media sync errors, and an attendance report that refreshes in about a minute instead of hours. Here's what changed.","tags":["release"],"image":null},"fields":{"slug":"/blog/2026-09-30-september-release/"}}},"pageContext":{"id":"2057a16e-429e-51e2-acdc-bb73bfa1aaf9"}},"staticQueryHashes":["1175525803","4080856488"]}