Welcome to our latest Zammo update! We've been working hard behind the scenes to streamline your experience and solve issues with our platform. Here's what we've brought to you in the July 8th release:
Improved File Scraping in Knowledge Base Query Results:
We fixed an issue where files scraped were showing internal endpoints in the knowledge base, rather than the website endpoint. Now, you'll only see the appropriate website endpoint, simplifying your interactions.
Invite API Area Now Available:
Looking to collaborate more directly? We've added an invite API area where you can request and accept invites. This makes it easier for you to interact and collaborate with others. Watch out for the UX enhancements leveraging these features coming soon!
Better Activity Flagging:
There was a bug where certain activities were being executed even when they were flagged as disabled. We tweaked our code to ensure that an activity really stops when you disable it, allowing you to maintain better control.
Refresh Tokens Support for AzureAD and OAuth2 Authentication:
Following customer requests, we're bringing support for refresh tokens for AzureAD and OAuth2 user authentication. This feature lets you minimize the number of times you need to login, making API calls significantly more smooth and hassle-free.
Adaptive Card Update to Enhance Security:
Once you log in, we ensure that the button cannot be subsequently clicked. This protects your session and gives you peace of mind.
User "Log Out" Option with Refresh Tokens:
Together with the refresh token feature, we’ve made it possible for you to "log out" a user, i.e., remove the refresh token. We added a "User OAuth log out" action in the UI Builder to achieve this.
Improved UX on OAuth Actions:
We have tidied up labels and ensured consistent UX on "User OAuth log in" and "User OAuth log out" actions.
Instant Displayed Version Update:
We've fixed an issue that caused your displayed version not to update immediately after a save or a publish. You'll now always see your most recent work reflected correctly.
Analytics Export Issue Resolved:
Customer feedback revealed a problem with invalid characters appearing in the analytics export under certain conditions. We’ve now resolved this, ensuring your analytics data remains accurate and trustworthy.