v4.13.11 - Added tracking of logging user's federation identifier #684
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Core Unlocked Package Changes
This release adds new fields & automation to track the logging user's federation identifier - this field is used in SAML SSO (Single Sign-On) settings, and is often a person's unique identifier in multiple systems. By capturing it in Nebula Logger, it makes it easier for Salesforce logs to be tied to logs for the same user in other systems.
Added new long textarea (512) fields
LoggedByFederationIdentifier__conLogEntryEvent__eandLog__cto track the value ofSchema.User.FederationIdentifierfor the logging userAdded new field
Log__c.HasLoggedByFederationIdentifier__cto make it easier to filter/identify records where the user's federation ID has been populatedAdded field-level security (FLS) for the new
Log__cfields to the permission setsLoggerAdmin,LoggerLogViewer, andLoggerEndUserAdded new field
Log__c.LoggedByFederationIdentifier__cto the flexipageLogRecordPage- it conditionally shows, based on the value of the other new field,Log__c.HasLoggedByFederationIdentifier__cBig Object Archive Plugin Changes
LogEntryArchiveIndex.indexe-meta.xmltoLogEntryArchiveIndex.index-meta.xml(indexe-->index) to fix an issue with newer versions of thesfcliPipeline Changes
package.jsonand in the directory./scripts/buildpackage-lock.json.prettierrcbuild.ymlto use v4 (compatible with Node 20)Installation Info
Core Unlocked Package - no namespace
Full Changelog: v4.13.10...v4.13.11
sf package install --wait 20 --security-type AdminsOnly --package 04t5Y0000027L98QAEsfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000027L98QAEThis discussion was created from the release Added tracking of logging user's federation identifier.
Beta Was this translation helpful? Give feedback.
All reactions