bitHeads employees
Hi folks,
MongoDB is ending support for MongoDB 6.0 at the end of July, so we will upgrade all environments to MongoDB 8.0 by that date.
The upgrade of the Public BaaS is targeted for Monday, July 7th.
The official notice can be found link text.
Let us know if you have any questions or concerns!
Paul.
Oh - and one thing that wasn't in the release notes... we bumped up the Design Portal session timeout -- so if you go away from the portal and come back to it later -- there's a better chance that you can pick up from where you left off (instead of being booted and having to re-login).
<crickets>
D'oh! We get it - we're all busy - and some folks are shy.
That said - the more feedback we get, the better we understand what features the community is looking for! (We've got plenty of features queued and/or in development - but it's prioritizing them that's the real trick.)
So let us know what works and what doesn't!
For example, is the Self-Service Account Deletion useful? Or were you all just planning to handle it manually, making it less important?
Paul.
Hi folks,
We have just released brainCloud 5.7 - and are eager to hear what you think!
Do you like the new Team Dashboard?
The new Node Usage pane in the Server Monitor?
How about the Self-Service Branding and Account Deletion Features? Are they useful?
Full details on the release here.
We are eager to hear your thoughts!
Paul.
Ah! Thanks for letting us know!
HI @francesco-lenolli - definitely log into our support chat to provide that information. Thanks.
Could you provide us with the appID and the user's profileID associated with the transaction?
@francesco-lenolli
For both of your questions, a single call -- GetEligiblePromotions() will do the work. It will return the values of maxPurchases and the caller's purchased, as well as the Unix timestamps for triggeredForUserAt and 'expiresForUserAt` for automated promotions.
@francesco-lenolli
Could you specify which part you are still confused about?
@francesco-lenolli
Excellent observation! You are correct. Our server-side validation was set to filter out any duration above 596 hours and mark it as "expired". However, we have thoroughly reviewed this validation and have since removed it. This patch will be deployed to our server today, meaning a duration limit will no longer exist. We appreciate you bringing this to our attention. Thank you.
