[Salesforce RTEM connector] Username field mapping and LoginAsEvent missing fields#14694
Closed
Bhagya767 wants to merge 4 commits into
Closed
[Salesforce RTEM connector] Username field mapping and LoginAsEvent missing fields#14694Bhagya767 wants to merge 4 commits into
Bhagya767 wants to merge 4 commits into
Conversation
v-atulyadav
added
Solution
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
This PR updates the Salesforce Service Cloud RTEM connector packaging to fix a Username field casing mismatch and to include additional LoginAsEvent fields required for Transaction Security Policy visibility.
Changes:
- Bumped solution/package versions to 3.4.1 and updated release notes.
- Renamed DCR stream column UserName → Username and updated KQL transforms to reference
Username. - Extended the
LoginAsEventpolling query to includePolicyId,PolicyOutcome, andEvaluationTime.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| Solutions/Salesforce Service Cloud/ReleaseNotes.md | Documents 3.4.1 changes (Username casing fix + LoginAsEvent fields). |
| Solutions/Salesforce Service Cloud/Package/mainTemplate.json | Version bump + DCR/polling query updates embedded in the solution template. |
| Solutions/Salesforce Service Cloud/Data/Solution_TSalesforceCloudtemplateSpec.json | Updates template spec version to 3.4.1. |
| Solutions/Salesforce Service Cloud/Data Connectors/SalesForceRealTimeEventMonitoringConnector_CCF/SalesforceRealTimeEventMonitoring_PollingConfig.json | Adds missing fields to LoginAsEvent SOQL query. |
| Solutions/Salesforce Service Cloud/Data Connectors/SalesForceRealTimeEventMonitoringConnector_CCF/SalesforceRealTimeEventMonitoring_DCR.json | Fixes input schema casing and aligns transform projection to Username. |
Contributor
|
Hi @Bhagya767 Kindly review the Copilot comments above and resolve them if applicable. Once addressed, please mark the comments as resolved. Thanks! |
Bhagya767
changed the title
Bhagya767
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(UserName -> Username) causing empty UserNameDetail column in Sentinel
polling query to enable Transaction Security Policy visibility