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
-
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__c
onLogEntryEvent__e
andLog__c
to track the value ofSchema.User.FederationIdentifier
for the logging userAdded new field
Log__c.HasLoggedByFederationIdentifier__c
to make it easier to filter/identify records where the user's federation ID has been populatedAdded field-level security (FLS) for the new
Log__c
fields to the permission setsLoggerAdmin
,LoggerLogViewer
, andLoggerEndUser
Added new field
Log__c.LoggedByFederationIdentifier__c
to the flexipageLogRecordPage
- it conditionally shows, based on the value of the other new field,Log__c.HasLoggedByFederationIdentifier__c
Big Object Archive Plugin Changes
LogEntryArchiveIndex.indexe-meta.xml
toLogEntryArchiveIndex.index-meta.xml
(indexe
-->index
) to fix an issue with newer versions of thesf
cliPipeline Changes
package.json
and in the directory./scripts/build
package-lock.json
.prettierrc
build.yml
to 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 04t5Y0000027L98QAE
sfdx force:package:install --wait 20 --securitytype AdminsOnly --package 04t5Y0000027L98QAE
This discussion was created from the release Added tracking of logging user's federation identifier.
Beta Was this translation helpful? Give feedback.
All reactions