3B Onboarding version 5.11 changelog: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "== Changes == * Optimized loading/refresh time for user-documents component where Document Packs implement multiple visibility conditions. Previously, we would execute each rule consecutively, whereas now, we execute each rule concurrently. Initial testing shows 60% faster load/reload speeds of the user-documents component * Added a new Flow Action "3B Recalculate Candidates Compliance" under the "3b onboarding" label. This action accepts a list of contactIds that admin...")
 
No edit summary
 
Line 4: Line 4:
* Added a new Flow Action "3B Recalculate Candidates Compliance" under the "3b onboarding" label. This action accepts a list of contactIds that admins would like to re-calculate the compliance profiles for. When you pass a contact's Id, we will re-calculate all Compliance Profiles. Tip: do not run this synchronously, instead, use async/scheduled flows to avoid performance impacts.
* Added a new Flow Action "3B Recalculate Candidates Compliance" under the "3b onboarding" label. This action accepts a list of contactIds that admins would like to re-calculate the compliance profiles for. When you pass a contact's Id, we will re-calculate all Compliance Profiles. Tip: do not run this synchronously, instead, use async/scheduled flows to avoid performance impacts.
* We are now respecting Sharing/Profile/Permission Set permissions for the user-documents component. This only applies to internal and community users. If the running user doesn't have access to the b3o__Document__c or b3o__Document_Assignment__c object/record (through sharing), then the document won't be displayed on the component. When upgrading, please ensure that internal users using the user-documents component through the MyDocuments visualforce page have the relevant permissions.
* We are now respecting Sharing/Profile/Permission Set permissions for the user-documents component. This only applies to internal and community users. If the running user doesn't have access to the b3o__Document__c or b3o__Document_Assignment__c object/record (through sharing), then the document won't be displayed on the component. When upgrading, please ensure that internal users using the user-documents component through the MyDocuments visualforce page have the relevant permissions.
== Notes ==
Please make sure that the SF org has Individuals enabled. Setup>Data Protection and Privacy>Edit>Make data protection details available in records>Save


== Installation Link ==
== Installation Link ==

Navigation menu