3B Onboarding version 6.9 changelog: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== Fixes == * An upgrade on Portals means that onboarding components could be rendered un-operational. This upgrade is required for 3B Portals & Mobile Apps v1.31+ == Changes == * ‼️ Admins no longer need use the b3o__P page over b3p__Portal. We have found a mechanism that allows us to connect to managed package components and this workaround is no longer needed. You may continue to use the b3o__P page, however it is not required. Link") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Fixes == | == Fixes == | ||
* | * Version 1.31 of the 3B Portals & Mobile apps package introduces a breaking change that could render portals inoperable. This patch fixes this behaviour and updates all Onboarding components to be compatible with 3B Portals v 1.31 and newer. | ||
== Changes == | == Changes == | ||
| Line 7: | Line 7: | ||
* ‼️ Admins no longer need use the b3o__P page over b3p__Portal. We have found a mechanism that allows us to connect to managed package components and this workaround is no longer needed. You may continue to use the b3o__P page, however it is not required. | * ‼️ Admins no longer need use the b3o__P page over b3p__Portal. We have found a mechanism that allows us to connect to managed package components and this workaround is no longer needed. You may continue to use the b3o__P page, however it is not required. | ||
Link | Link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tJ5000000D4Wy | ||
[[Category:3B Onboarding Changelog]] | |||
Latest revision as of 18:48, 29 October 2024
Fixes
- Version 1.31 of the 3B Portals & Mobile apps package introduces a breaking change that could render portals inoperable. This patch fixes this behaviour and updates all Onboarding components to be compatible with 3B Portals v 1.31 and newer.
Changes
- ‼️ Admins no longer need use the b3o__P page over b3p__Portal. We have found a mechanism that allows us to connect to managed package components and this workaround is no longer needed. You may continue to use the b3o__P page, however it is not required.
Link: https://login.salesforce.com/packaging/installPackage.apexp?p0=04tJ5000000D4Wy