3B Portals & Mobile App version 5.x changelog
Jump to navigation
Jump to search
Version 5.14
Changes
- Under the hood changes to improve loading times and API usage
- Inverted evaluation logic, so that it aligns with Hide If functionality
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS0000013N5x
Version 5.10
Changes
- Added missing metadata
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS00000100p3
Version 5.9
Changes
- Security Enhancements
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000zovx
Version 5.8
Changes
- Reduction in the number of API calls from the app
Security
- Security patches
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000mRp7
Version 5.7
Changes
- Previously, Screen Flows and LWCs embedded in 3B Portals were running as the guest site user. This is now updated and we will use the user linked to the Authorization Service (in the Named Credential).
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000mLyD
Version 5.6
New
- Admins (managers) can now suspend access to 3B Portals. A new checkbox on the Contact called "Disabled Portal User" controls whether a portal user has access to portals or not. If this checkbox is checked, we will immediately suspend access to 3B Portals and will display the error "Looks like your session has ended or your access has been turned off. Let us know if you need help getting back in.". If the user attempts to log in or register, they will see the error "Looks like your user access has been suspended."
Fixes
- Embeddable native LWC components were not rendering correctly as we missed to add specific metadata in the 5.5 release. This is fixed now.
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000mJun
Version 5.5
New
- Added partial support for embedding native LWC components in portals
- Added native support for screen flows in portals
- Added a new global variable "contextData" that allows users to define hide-if conditions using the contextually loaded record
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000lwTZ
Version 5.4
New
- Introducing Passwordless login - with this version, we will no longer support Username + Password logins. Post installation, you will need to create a new email alert to the contact that sends them the Temporary Password. When a user attempts to log in to the portal, we will issue them with a unique code in the Temporary Password field on the contact. If the user enter a wrong temporary password code (verification code), we will generate a new code.
- Attempted to fix support for embedded screen flows. This version should allow you to use the "Flow" component in portals.
Fixes
- DEV-633- Push notifications - if you specify a protal link in a push notification, we will open the PWA app on that particular page. Upgrade Instructions: If you have already configured any push notifications, make sure to add the "Link" property to the invocable action. Set this link property either to the specific portal page you want the user to land on when they click on the notification or set it to the Web Portal name. (e.g. https://3b-demo-org.my.salesforce-sites.com/onboarding/b3p__Portal#MobileApp or https://3b-demo-org.my.salesforce-sites.com/onboarding/b3p__Portal#SpecificPage)
- DEV-750 - Further improvements on Rich Text Fields support
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000jy85
Version 5.3
New
- DEV-749 We have added support for filtering and sorting repeatable child related records. Documentation is available here
Changes
- DEV-750 - Added support for Rich Text Fields that are embedded inside of portal pages. Previously, rich text fields would output the raw HTML format and with this release, we will output the actual rendered HTML
- DEV-752 - Previously, we would cache the data to be retrieved for merge mapping variables on a page. This was wrong as that data could be updated rapidly. So, if let's say you were using {{record.Name}} and a form updated the contextual record, the update wasn't reflected immediately (we purged cache 2 minutes later)
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000gkUf
Version 5.2
Fixes
- When a user has requested a logout (@logout), we will clear cache completely
- Some minor adjustments to the upgraded communications mechnism
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000ge97
Version 5.1
Changes
- Upgraded communications mechanism
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000g5w9
Version 5.0
Changes
- The default behaviour has been changed from a Single Page behaviour to a regular navigation. Previously, we weren't re-loading the entire page, which meant that Onboarding/WFM components could suffer with namespace clashing, making pages containing components with shared namespaces impossible. This was happening as we were using Single Page Application behaviour, which wasn't un-registering web components correctly. This behaviour is now changed, so when a user navigates to a page, we will reload the entire page instead of just replacing the content of the page. The impact is slightly slower loading times, however reliability and long term stability will be enhanced. You can still change the behaviour to an SPA navigation behaviour from
Setup.b3p__Portal__c.b3p__Portals_are_SPA__c
Link
https://login.salesforce.com/packaging/installPackage.apexp?p0=04tWS000000dycD