Release V2.27

Kemicard Release Version 2.27

This release focuses on making passes smarter, more location-aware, and more reliable to generate. We’ve also done some long-overdue housekeeping — two of the tools you use most have been renamed to better reflect what they actually do. Here’s everything that’s new.

New Features & Highlights

• Geofencing & Maps: Passes can now respond to where your users actually are. With geofencing built into Kemicard, you can define a location and have the right pass surface automatically when someone walks into range — no manual triggers, no extra configuration on the user’s end. And because we know that not everyone has a latitude and longitude sitting around, we’ve made it possible to use plain street addresses instead.
  • Geofencing support– Define geographic boundaries for your passes. When a pass holder enters a fenced area, Kemicard handles the trigger — no extra setup required on the recipient’s device.
  • Plain-address geofencing– You no longer need to convert addresses into coordinates manually. Enter a street address and Kemicard resolves the location for you automatically, powered by Google Maps.
  • Google Maps API integration– All address lookups and geolocation resolution are now backed by the Google Maps API, giving you accurate, consistent location data without any third-party set

• Barcode Improvements: Barcodes are often the first thing a scanner sees — so they need to work correctly, every time. This release brings a couple of targeted improvements: accessibility gets a boost with alternate text support for Google generic pass barcodes, and a frustrating display bug that was making dynamic values look empty during template setup has been resolved.
  
  • Alternate text for Google generic pass barcodes- You can now add alternate text to barcodes on Google generic passes, improving readability for accessibility tools and giving scanners a fallback text value alongside the barcode itself
  • Dynamic barcode value display — fixed– When previewing a template with a QR field selected, barcodes would previously show “(empty)” instead of pulling in sample record data. That’s now fixed — previews accurately reflect what the barcode will look like with real data.
    

• Pass Generation Reliability & Error Reporting: Pass generation is the core of what Kemicard does — so when something goes wrong during that process, you need to know about it immediately, not after a user reports a problem. This release introduces the Pass Generation Request object, which gives you real-time visibility into the status of every generation job. We’ve also closed several gaps where failures were happening silently with no indication that anything had gone wrong.
  • Pass Generation Request objectNew– A new object in Kemicard now tracks every pass generation request from start to finish. You can see the current status at a glance — whether it’s in progress, completed, or failed — and investigate from there without hunting through logs.
  • Improved error reporting for Google & Apple generation– Previously, a failed Google or Apple pass generation could fail without surfacing a clear error. Generation failures now produce actionable error messages, so your team knows exactly what went wrong and can act on it quickly.
  • Silent failure prevention– Several paths through the generation flow that were previously able to fail without any status update have been addressed. The entire flow is more predictable, and status is now consistently updated at each stage.

• UX & Admin Improvements: Two of Kemicard’s core tools have new names that do a better job of describing what they actually offer. If you’ve been using Template Builder or Bulk Actions, nothing has changed about how they work — but you’ll find them under new names that make their scope a little clearer at a glance.
  • Template Builder is now Kemicard Studio– The pass design and template configuration experience is now called Kemicard Studio. The rename reflects its role as the central creative workspace for building and managing pass designs — not just a builder, but a full studio environment.
  • Bulk Actions is now Kemicard Campaigns- The tool for sending passes to large audiences is now called Kemicard Campaigns. The new name better captures the intent — you’re running a coordinated campaign, not just executing a bulk operation.
  • Optional default values for fields- Fields in your templates can now carry an optional default value. This simplifies configuration when most of your records share a common value — you set it once and override it only where needed.

Bug Fixes

Beyond the headline features, the team resolved a number of issues that were getting in the way of everyday work. Here’s a summary of what was fixed and what it means for your workflow.

Kemicard Studio & field configuration

• Barcode preview showing “(empty)” — When setting up a QR barcode field and switching to preview mode, the barcode was showing a blank value rather than pulling in sample data from your records. This is now fixed, so what you see in preview accurately reflects what your customers will receive.
• Google templates blocked in field config editor — Existing Google Wallet templates that used dynamic header fields were unexpectedly blocking access to the field configuration editor. This has been resolved, and those templates are now fully editable again.

Notifications & UI

• Apple links with labels not working — Pass links that included a label on Apple Wallet passes were failing to open correctly. These links now behave as expected.
• Campaign Manager showing no records — The report view inside Campaign Manager was rendering empty even when there were active records. This was a display issue and has been corrected.
• Org Contact Layout replacement broken — Replacing the Org Contact Layout was not applying correctly in some configurations. The issue has been resolved.

Installation & admin

• Integration user missing metadata access — The integration user’s Profile and Permission Set was missing access to the App_Configuration__mdt custom metadata type, which could cause unexpected behaviour during setup. This has been resolved.
• Security issues addressed — Several security issues identified against version 2.27 have been investigated and resolved. No action is required from admins.

Other

• Investigated and addressed security issues surfaced for 2.27.

Installation Info

Ready to upgrade? Use the links below to install Kemicard 2.27 in your org. If you’re testing first, start with the Sandbox link — the package ID is the same for both environments, so you can validate in Sandbox before pushing to Production.

Sandbox & Scratch Orgs:

https://test.salesforce.com/packaging/installPackage.apexp?p0=04tJR000000Gh7RYAS

Production & Developer Edition Orgs:

https://login.salesforce.com/packaging/installPackage.apexp?p0=04tJR000000Gh7RYAS