Salesforce (enh)
Monitoring & Analytics
Smart Insights Daily Summary
Monitoring & Analytics
Document Audit (enh)
Maintenance
Monitoring & Analytics - Salesforce (enh)
Description
Six pre-configured enhancements in Germain to further improve real-time insights while monitoring Salesforce.com.1. Enhancement: Additional real-time analysis of SFDC Log
- New KPIs being preconfigured in/monitored by Germain (and other KPIs already available)
- PlatformEventUsage
- Custom Log Objects
- LogEvent__c (This is new one will be available after 05/13/2022)
- System_Error__c
- Metadata/Settings
- CustomLabel
- Custom Metadata Objects
- Custom Setting Objects
- Other objects like
- AsyncApexJob
- FlowInterview
- PlatformEventUsage
- Dashboards/portlets

Salesforce logging - GermainUX

Salesforce Log Apex - GermainUX

Salesforce system error - GermainUX
2. Enhancement: Click Duration Breakdown
Time breakdown of a User Click, from the browser to the backend application and database of Salesforce.com.
Salesforce click analysis - GermainUX
3. Enhancement: Alerts when a Salesforce Case (in this example, Cases are Credit Card or Membership Orders) stays in “submitted” status longer than 30 minutes
This client required alerts whenever a Case in Salesforce (related to Credit Card or Membership Orders) remained in a ‘submitted’ status for over 30 minutes. Problem: The client previously relied on a VB script to execute the following SOQL query and monitor the status of the Cases, but this approach proved ineffective due to various reasons. Solution: Germain now runs the following two SOQL queries against the Salesforce database every minute and stores the results in Germain datamart. Subsequently, Germain generates an event whenever it detects a change to the Credit Card or Membership Order status based on the execution of a predefined rule. This enhancement is not specific to Salesforce, thus the same mechanism and approach can be applied to data stored in other data sources of any other application. Credit Card Cases in Submitted Status for more than 30 minutes:- SOQL Statement to check on Credit Card staying in Submitted status for more than 30 minutes
from Case
where Status = ‘Submitted’
and Type__c = ‘Billing/Payment Maintenance’
and Sub_Type__c like ‘Credit Card%’
and SR_Number__c = null
and CreatedDate >= 2022-01-06T00:00:00Z
ORDER BY Type__c, Sub_Type__c, CreatedDate DESC
- SOQL Statement to check on Membership Orders staying in Submitted status for more than 30 min
from Case
where Status = ‘Submitted’
and Type__c = ‘Program Maintenance’
and Sub_Type__c in (‘Membership Enrollment’,‘Membership Renewal’,‘Renewal with Update’)
and SR_Number__c = null
and CreatedDate >= 2022-01-01T00:00:00Z
ORDER BY Type__c, Sub_Type__c, CreatedDate DESC
- Rule
sfdc-document-change-status.drl
sfdc-document-change-status.drl
sfdc-document-change-status.drl
4. Enhancement: Aura Error “Sorry to interrupt”
Germain captures (records, enables client replay of the recorded session, provides business impact analysis, etc.) whenever a Salesforce user encounters this error message:
Salesforce “Sorry to Interrupt” - GermainUX

5. Enhancement: Capture External Domain
Now, when a mouse click occurs on a button, link, or image that directs to an external domain, Germain assigns that external domain as the ‘target,’ allowing for analytics derivation and search functionalities. Example of a click routing the Salesforce user to an external domain:
6. Enhancement: “Click Name”
This feature generates a ‘name’ for each click performed by a user on Salesforce. The naming convention is configurable.
Monitoring & Analytics - Smart Insights Daily Summary
Description
In addition to receiving individual email alert whenever a kpi is exceeding SLA, you can receive a summary email once per day that summarizes all the kpi that have exceeded SLA that day. Example: @ Germain, we receive daily summary email that looks like this helping us identify the biggest variations that occurred that day, variations relative to what happened last week, last month, last quarter, last year. currently ~1100 kpi/sla are being analyzed for any given cloud instances that we maintain. This Daily Summary email comes in addition to any real-time alert and automation that get automatically triggered and processed by Germain. Last but not least, these 1100 KPIs are of various natures: Technology, Process, User or Business. By default, we just enable our Smart Insight engine for all active KPIs.
Configure / example
- Automation > Alerts > analytical-sla-alert

- Analytics > SLA > Smart Insights SLA - Day

Maintenance - Document Audit (enh)
Description
Here are four use cases illustrating how clients benefit from the Document Audit mechanism in Germain:Use Case 1: Data Audit Trail
Track changes / auditing any Structured Data (records) in any external system (e.g. via REST, SQL, SOAP, etc)Use Case 2: Business Data Status
Track how long a record stays in a specific state. Examples- Time to respond to a ticket
- Time to resolve a service request
- Alerts when a Case (in this example, Cases are Credit Card or Membership Orders) stays in “submitted” status longer than 30 minutes.
- Germain runs every minute, these 2 SOQL (below) against the application database. Stores the result into Germain datamart. Then Germain generates an event whenever it detects a change to the Credit Card or Membership Order via the execution of a Rule (below)
- SOQL Statement to check on Credit Card staying in Submitted status for more than 30 minutes
SELECT Id, CaseNumber, Id__c, Status, Partner__c, System_Category__c, Type__c, Sub_Type__c, Payment_Frequency__c, CreatedDate
from Case
where Status = ‘Submitted’
and Type__c = ‘Billing/Payment Maintenance’
and Sub_Type__c like ‘Credit Card%’
and SR_Number__c = null
and CreatedDate >= 2022-01-06T00:00:00Z
ORDER BY Type__c, Sub_Type__c, CreatedDate DESC - SOQL Statement to check on Membership Orders staying in Submitted status for more than 30 min
SELECT Id, CaseNumber, Siebel_Id__c, Status, Partner__c, RecordType.name, System_Category__c, Type__c, Sub_Type__c, Payment_Frequency__c, CreatedDate
from Case
where Status = ‘Submitted’
and Type__c = ‘Program Maintenance’
and Sub_Type__c in (‘Membership Enrollment’,‘Membership Renewal’,‘Renewal with Update’)
and SR_Number__c = null
and CreatedDate >= 2022-01-01T00:00:00Z
ORDER BY Type__c, Sub_Type__c, CreatedDate DESC - Rule
sfdc-document-change-status.drl is shown in full earlier on this page.
Use Case 3: User Behavior Analytics
Collect statistics on User behavior Examples:- Times a User edits a record
- Most prolific editors
- etc.
Use Case 4: Alert on Content
Alert based on content of document fields; Example:- Look for keywords that trigger alerts / events in a system.
Get Help
Contact GermainUX Support
The Germain Team can help you set this up.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE LLC.

