Skylar Compliance v3.0.0 SyncPack and Skylar Compliance v107 PowerPack are released

Hello, 

We are pleased to announce the release of the Skylar Compliance (formerly Restorepoint) v3.0.0 SyncPack and the associated Skylar Compliance v107 PowerPack. These releases contain many important updates, detailed here and in the Release Notes. 

With this release, ScienceLogic has rebranded the "Restorepoint" SyncPack to the "Skylar Compliance" SyncPack. You will notice this rebranding throughout the SyncPack, along with the Skylar Automation (formerly PowerFlow) platform. This change, as well as similar branding changes to the other products offered by ScienceLogic, reflects ScienceLogic's commitment to delivering intelligence that accelerates outcomes through service-centric observability, AI-driven operations, and intelligent automation. For more information, see the ScienceLogic website (https://sciencelogic.com/platform/overview)

Features Included

• Updated the "CreateSkylarComplianceDevice" step to improve device creation and onboarding in
  the following ways:
  • Updated plug-in retrieval to ensure the latest plug-in data is fetched, which will improve
    configuration of device backup protocols.
  • Updated logic when preparing credentials to prevent duplicate creation of credentials.
  • If a Skylar Compliance Device ID already exists for a device, it will not be created as a
    duplicate, and the Skylar One custom attribute will be updated."
• Updated the "Get Plugin Details" step to use real-time plug-in data. This ensures that whenever you
  update a device's configuration and/or protocols, you can log in to Skylar Compliance and adjust the
  default configuration of the plug-in. Subsequently, when a new device is registered, the real-time
  plug-in default configuration will be fetched, along with the protocol, enabling the creation of a new
  device using these updated details.
• Combined three of the steps in the "Skylar Compliance: Sync Devices" application into the "Retrieve
  Device Group Data from Skylar One" step to improve the efficiency of the process when retrieving
  devices under the "Skylar Compliance Devices" group and fetching the device limit from Skylar
  Compliance.
• Combined multiple steps of the "Skylar Compliance: Sync Devices" application into the
  "CreateandValidateCustomAttribute" step to allow a custom attribute to be created for a device if one does not exist. Additionally, added logging if a custom attribute already exists for a device.
• Added the "Skylar Compliance: Pre Check Application" Application, which runs a series of checks
  against Skylar Compliance (to ensure successful authentication and capacity) and Skylar One (to
  ensure proper connectivity, permissions, and API access). Running the application generates a
  detailed report that outlines the system's health, checks authentication compatibility with both Skylar Compliance and Skylar One, and highlights any necessary actions to take before proceeding.
• Added the "Device Provisioning Report" step to the "Skylar Compliance: Onboard Device"
  application. This step compiles information from previous steps and generates a "Device
  Provisioning" report.
• Added the "Enrich Devices with Credentials data " step to the "Skylar Compliance: Onboard Device"
  application. This step fetches and validates credential data from Skylar One using the globally
  unique identifiers (GUIDs) of the associated credential. Devices with missing or invalid credentials
  are flagged for review, then the enriched data is passed to the next step in the Skylar Compliance
  onboarding workflow.
• Added the "Get Device Details" step to the "Skylar Compliance: Onboard Device" application. This
  step gathers relevant information for each device, such as device property details, linked credentials,
  device class information, and device collector group information.
• Added the "Get collector group from Skylar One" step to the "Skylar Compliance: Onboard Device"
  application. This step fetches Data Collector information responsible for mapping agents in Skylar
  Compliance.
• Report data will now be generated when creating devices, both when a device failed to be created
  and when a device is successfully created.
• Updated the logic used when finding the Skylar Compliance domain and mapping it to a new device.
• Improved security when transferring data from one application step to another, such as transferring
  credential information.
• Added the "Skylar Compliance: Create or Update Custom Links" application, to allow for the creation
  and update of custom links for devices in Skylar Compliance. This application replaces functionality
  that was previously handled by the "Skylar Compliance: Sync Devices" application.
  
  NOTE:  In order to successfully use the "Skylar Compliance: Create or Update Custom Links"
  application, you must set the "create_custom_link" configuration option value to zero in the
  "Skylar Compliance: Sync Devices" application before running the new application.

Issues Addressed

The following issues were addressed in this release:

• Addressed an issue with the "Skylar Compliance: Onboard Device" application that caused an error
  to be generated due to the default assignment of values from the SyncPack. (Cases: 00523695,
  00527168)
• Addressed an issue that prevented Skylar Automation from successfully accessing the Skylar
  Compliance API. As a part of the fix for this issue, Skylar Automation will now check the HTTP
  response code during the "GetSkylarComplianceLicenseDetails" step, and will raise a
  "StepFailedException" error if a "401 - Unauthorized error" message is received. (Case: 00500459)

Thank you, 
Release Management