3B Portals & Mobile App version 9.x changelog
Version 9.5
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000002P4or
Important Notice: 3B Portals Migration to 2GP
3B Portals is transitioning from a First-Generation Managed Package (1GP) to a Second-Generation Managed Package (2GP) development workflow.
Please review the guidelines below based on whether you are completing a fresh installation or upgrading an existing environment.
New Installations
For all new Salesforce organization deployments, you must use the 2GP installation link (Version 9.5 2GP or higher). New 1GP installations are no longer supported.
Existing Installations (Upgrade Path)
If an environment is currently running a 1GP version of 3B Forms (any version prior to v9.9), you cannot upgrade directly to the latest 2GP release. You must follow this specific three-step migration path:
- Step 1: Upgrade the existing 1GP environment to the Version 9.5 1GP transition package.
- Step 2: Migrate the environment from the Version 9.9 1GP package to the Version 9.5 2GP package.
- Step 3: Upgrade from the Version 9.5 2GP package to your final target 2GP package version (> v9.5).
Note: Skipping the Version 9.5 transition steps on existing 1GP orgs will result in installation failures. Ensure you follow the sequence exactly as outlined.
Version 9.5 2GP Transition Package
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tJ5000000LUNBIA4
Version 9
New
- AI Studio - Add your OpenAI API key in Portals custom settings to enable the new AI Studio companion. AI Studio allows you to use natural language prompts in building rich portal and mobile app experiences
- Sub Templates - You can now build a page and mark it as Sub Template (checkbox on the Page object). A page marked as a sub-template can be dragged and dropped into any other page, either as a static or dynamic reference.
Changes
- A UI Refresh of the builder
- Added the ability to customize the labels in the login component
- Faster loading
- Major improvements in Push Notifications and their reliability.
This version introduces tracking of the Status of a push notification:
- Clicked status will be set to the Status (b3p__Status__c) field on the Push Message (b3p__Push_Message__c) when the user clicks on a push notification. note, this isn’t guaranteed to work due to device side limitations (iOS/Android) in some edge cases, like the device is offline, the user has low data mode enabled, the device is in battery saving mode etc.
- Received status will be set to the Status on the Push Message when the push notification is received by the user.