|
Welcome to Pharos 1.850 - Bia Bia is the goddess of power and strength in Greek mythology. Synonymous to this, our new release contains more powerful features like AI Issue Analysis and Issues Dashboard, along with other enhancements. Read on and don't forget to upgrade. |
Highlights
- AI-powered Issue Analysis is GA
- Added support for new flow elements: collection sort and filter
- New Issues dashboard on the home page
- Flows errors inside managed packages are now logged in Pharos
- Quickstart wizard got even quicker
- Error reporting opt-out
- New Ticketing Actions view
- Update based ticketing and notification rules (beta)
- Government Cloud support (beta)
- Allow using using action templates on the "create ticket" form
- Add ticket comments in Jira or ADO via the new Ticketing Comment Action
Upgrade Instructions
- Perform the package installation as normal.
- IMPORTANT: Please perform this step if you are using MS Teams in order to ensure that you continue to receive notifications without interruption.
In Pharos Admin navigate to Integrations -> Teams -> Authentication and re-authenticate to your Teams instance.
Beta Functionality
For functionality labeled as "Beta" please inquire with us for enablement. If your org doesn't already have a beta feature enabled it won't be available even after upgrade. However, we're happy to work with you to get into our beta program and look forward to your participation!
New Functionality Details
Pharos Admin
- Quickstart wizard simplified. It's now easier than ever to get Pharos configured. We removed the extra steps so the focus is only on the core setup. Integrations and monitoring setup can still be performed in the respective pages of Pharos Admin.
- Updated default notification text for Logs and Issues. We adjusted the default notification templates so it's straight and to the point. You are welcome to adjust them further, as needed.
Architecture
- Create Pharos logs for inbound emails that fail to parse. Sometimes we're not able to capture an exception email. If that does occur, Pharos will now create an internal log so this problem can be tracked.
Flow Errors
- Added support for new elements: collection sort and filter. These elements are now available in the flow debug view.
- Updates to post processing logic for VERY large flow stack traces. Once in a while, Salesforce will send a giant stack trace email. These are typically due to a run-away recursion problem within the flow itself. We are now tracking these properly as Logs.
- Managed package flows are now properly logged in Pharos.
Azure DevOps Integration
- Dynamic comments on Azure DevOps inline view. Comments on your ADO work item will now render on the inline Azure DevOps view from an Issue record.
- Added permission checks for tags on ADO ticket creation. Pharos will no longer fail to create an ADO work item when the user doesn't have "tag" permissions.
- Remove required Assignee on ADO form.
Bulk API Error Tracking
- Added memory optimization for bulk api log processing to avoid heap size errors.
Issue Tracker
- Added issues dashboard to home page. You can now get a detailed view into your Issues back log with a single glance.
- Update average frequency calculation logic. To improve accuracy and performance, issue occurrences are grouped by day and the frequency is calculated between each of the days.
- Added 2 new values to Issue Status picklist: Triaged and Actioned
- Update based ticketing and notification rules (beta). You can now send notifications or create tickets when an Issue record is updated. A great set of use cases to try in your today are the following:
- When an Issue exceeds 100 logs, send a Slack/Teams message to your channel(s) to notify of high urgency.
- When an Issue user impact exceeds 10 users, create a ticket.
- When Issue average frequency drops below 30 days, send a note in Slack/Teams to close the corresponding Issue.
- When an Issue exceeds 10 occurrences, send a Slack/Teams message, then create a ticket if an Issue has over 100 occurrences.
OpenAI Integration
- Issue Analysis is GA! Ask for your API key today and jumpstart your troubleshooting efforts.
- Producing a root cause analysis.
- Resolution options.
- Severity estimate and justification.
Slack Integration
- Allow custom slack app to be used for Pharos integration. Those customers that aren't able to utilize the Pharos Slack application can now build their own app in their Slack workspace and connect it to Pharos.
Dynamic Tracing (beta)
- If no user is available from Issue, all users are displayed in user picklist. Sometimes the running user isn't accurately captured on an Issue. In those scenarios you have a choice to select any user from your org to enable tracing for.
Pharos Admin
- Government Cloud support (beta). If your org is on a government cloud, Pharos now supports a quick configuration run-through via the Quickstart wizard. The application automatically detects GovCloud instance and enables a new configuration path.
- Error reporting opt-out. If you'd like to opt-out of our automated error reporting, you can do so from the Admin page by navigating to Advanced -> Error Reporting. Opting out will not prevent you from submitting a manual error report.
BUG FIXES
Some highlights below:
Architecture
- EmailService - after refresh sandbox and quick start, second email is added
- Error during notification processing: Aggregate query does not support queryMore(), use LIMIT to restrict the results to a single batch
Issue Tracker
- Fixed error on Issues with very high log count: Non-selective query against large object type (more than 1000000 rows). Consider an indexed filter or contact salesforce.com about custom indexing
- Issue were not getting created for some Async Job logs
Flow Errors
- Handled flow errors no longer generate a parse exception and a Pharos log in some cases
- Unable to toggle flow error tracking during Quickstart wizard
- Failed step indicator misplaced for some flow logs
- Some auto-layout flows with loops weren't rendering correctly on flow debug view
Environment Info
- Some logs for async jobs from managed packages were missing a namespace
- Lightning red error message showing up on log details for some logs
Microsoft Teams Integration
- Teams integration broken due to expired client secret
Jira Integration
- Jira epic values in dropdown showing 'undefined' during manual ticket creation from a form
Monitoring
- Some rule filter logic highlighted as "not valid" on monitoring rule edits
Bulk API
- Bulk API processing should stop re-trying in case of unhandled faults
- Some Bulk API Issues were showing a question mark (?) icon
Log Retention
- Some retention rules weren't firing after rule edit
Notifications
- Duplicate notifications were sent out for some notification rules
Pharos Admin
- Unable to add filter criteria to a re-activated ticketing rule
Azure DevOps Integration
- Sync for linked or duplicated issues doesn't work in some cases
Comments
0 comments
Article is closed for comments.