Pharos 1.7 - Coeus

Welcome to Pharos v1.7 - Coeus! Coeus is the Titan of Resolve and Intelligence and that is exactly what this new release is all about - empowering you to make better decisions with more accurate data and better tools throughout. See beyond the obvious and action your insights quicker!

Major Highlights

1.7 was a huge release for us for many reasons. One reason is that it's, well, HUGE in terms of the sheer volume of changes. All good things, we can assure you! Thanks to our amazing customers and partners we have received a great deal of feedback and worked hard on incorporating it into our core product. There are lots of improvements in almost all areas. Here are the most notable ones:

• Flow Orchestrator Support

• Improvements to Flow Debug and Error Tracking

• Issue View Updates

• Support for Notification and Jira Rules on Issues

• Connected Orgs Log Broadcasting 

• Architecture Improvements

Details

Flows

• Flow Orchestrator Support
  By now most of you have probably heard about the new Flow Orchestrator. It's an amazing tool for building complex logic. We are pleased to announce that Pharos is now tracking Orchestrator errors in a similar fashion as Flow errors. There's no need to enable or configure anything, simply install the latest Pharos package and start getting visibility into Orchestrator failures.
  
  
• Improved Auto Layout Support in Debug View
  Simple flows are often built using the Auto Layout functionality in Flow Builder. This is a great way to produce a neat looking Flow without moving a single element around. Pharos now has an improved debug view that accounts for Flows built in this fashion.
  
  
• Improved Flow and Process Builder Fingerprinting 
  Fingerprinting is a very important concept in the Pharos application. This release we made it our goal to address some pain points around tracking same and similar Flow errors. Our new algorithm now takes into account more attributes and does a better job of processing the raw error messages. All this so you can have more accurate occurrence and impact data.

Issues

• Clickable Occurrence Charts in Logs and Issues
  All of our occurrence charts are now clickable and will link to relevant reports. This allows for faster analysis and troubleshooting experience! Here's quick demo.
  
  
• Improved Tracking of Impacted Objects and Users
  Did you know that errors can impact more than one object at a time? Or even more than one type of object? With this latest version you'll have all that visibility from Log and Issue details. 
   
• 'Mark Related' and 'Duplicate Issues' Buttons on Issues List View
  Working from a list view is often more convenient than sifting through Issue records one by one. We've made it even easier now to relate and duplicate Issues in bulk. One button click is all it should take. Here's a quick demo. 
  
  
• New Jira Task Button on Issue Details
  This feature is for those of you that would like to selectively create Jira tickets from Issues vs utilizing automated rules. Simply click a button from Issue details to create a Jira ticket and track progress via the new inline Jira page.
  
  
• Inline Jira Ticket View on Issue Details
  View Jira ticket summary and comments from Issue details directly. Here's a quick demo.
  
  
• Added a Related Issues View on Issue Details
  Last but not least in this category is the ability to browse the entire related Issues tree. This view shows child Issues, parent Issues and even sibling Issues, allowing you to navigate between quicker.

Notifications

• Notification and Jira Rules Now Support Issues
  This is a big one! All the same rules functionality that was previously only available for Logs is now available for Issues! Moreover, we've added some cool Jira logic around Issues such as: automated priority and status synchronization, automated bidirectional ticket and Issue linking and duplicating. No matter where your source of truth is: Jira or Salesforce, the other system will now always stay up to date.
   
• New Autosuggest Team/Channel Picker for Slack and Teams Notifications
  We've added an improved way to select channels and teams in notification rules. Those customers that are a part of large organizations with hundreds of channels or teams can now move very quickly when configuring notifications in Pharos!

Connected Orgs

• Broadcast Setup No Longer Requires Bidirectional Logins
  To improve security and efficiency, we've removed the need for a Target to Source connection. All that's required is to provide an org id of the Source org at Target and logs will flow between the environments same as before.
  
  
• New Valid Connection Indicator for Connected Orgs
  Should the connection to any external org expire or become otherwise unavailable, Pharos will show a red indicator on the Connected Orgs page.  
  
  

Architecture

• Improved Metadata Caching Mechanism
  In effort to increase the efficiency of metadata retrieval we have made several improvements to our caching layer. By utilizing caching Pharos is able to reduce the amount of resources it consumes in your org, giving you those cycles back!
  
  
• Improved Refresh Token Process for Jira and Teams Integrations
  Due to recent updates from Microsoft and Atlassian APIs we have reworked our entire auth token refresh process. This resulted in more stable and reliable integrations that are always on!

General Error Handling

• Add Support for Zipped Bulk API Requests
  Pharos is now supporting archived Bulk API requests in the same manner as their raw counterparts. 
  
  
• New Summary View for Bulk API Errors
  New and improved summary view of Bulk API errors will now show only unique errors, with the ability to drill down into all records that failed with a given error message.
  
  
• Improved Fingerprinting of Apex Errors
  In the spirit of improvement, we have updated our fingerprinting algorithms for Apex errors to bring you more accurate occurrence and impact data.

Log Util

• Added New Rest Methods for Integration Logs
  In addition to HttpRequest and HttpResponse our Apex Log Util now support RestRequest and RestResponse parameters when creating integration logs.
  
  
• LWC and Lightning Logging Framework
  This is a major update that brings you the ability to perform logging straight from LWC and Aura controllers. No need to pass things over to Apex or roll your own custom logging - simply use our JS log util to do the heavy lifting for you! 
  
  
• New Invokable Methods for Flow Logging
  Trying to figure out why a flow isn't doing what you need it to? Well, now there's a way to create Pharos logs directly from Flows. Just use our Invokable Apex action and pass any data that you need.

Get to know your Greek Gods & Goddesses

Coeus is the Titan of Resolve and Intelligence. The name itself means query, questioning and intellect. Coeus had an inquisitive mind and desire to learn, and with his gained knowledge and understanding, he was able to see beyond the obvious. Perhaps that is why he was also identified as the god of wisdom. Having knowledge is one thing, but being able to truly understand it and use it for predicting future occurrences and events is being wise.