Skylar Compliance SyncPack, version 3.0.0

Version 3.0.0 of the "Skylar Compliance" (formerly Restorepoint) SyncPack rebrands the SyncPack to Skylar Compliance, adds the "Skylar Compliance: Pre Check" application, adds and updates multiple steps across multiple applications, and addresses multiple issues.

This SyncPack uses the "Skylar Compliance" (formerly Restorepoint) PowerPack.

Features Included in this Release

The following feature was added in this release:

  • 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).

  • 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.

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 in this Release

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)

To view the latest manuals for the Skylar Automation (formerly PowerFlow) Platform, see theSkylar Automation  page. To view the latest release notes for Skylar Automation, see Skylar Automation Release Notes.

Known Issues

This release of the "Skylar Compliance" SyncPack has the following known issues:

  • The account that is being used by Skylar Automation to authenticate into Skylar One must have the secondary organization membership set to "(All Organizations)" to enable Skylar Automation to pull device lists from all organizations. (Case: 00364872)

System Requirements

This release of the "Skylar Compliance" SyncPack requires the following:

  • Skylar Automation (PowerFlow) platform version 3.0.0 or later.
  • "Base Steps" SyncPack version 1.5.6 or later.
  • Skylar One version 12.3.x or later. For details on upgrading SL1, see the relevant Skylar One Platform Release Notes.
  • "Skylar Compliance" PowerPack version 107 or later.
  • Skylar Compliance (formerly Restorepoint) version 5.6.x or later.

The following table lists the port access required by the Skylar Automation platform and this SyncPack:

Source IP Skylar Automation Destination Skylar Automation Source Port Destination Port Requirement
Skylar Automation Skylar One API Any TCP 443 Skylar One API Access
Skylar Automation Skylar Compliance API Any TCP 443 Skylar ComplianceAPI Access
Skylar Automation Skylar One Database Any TCP 7706 Skylar One Database Access

Installing the SyncPack

A SyncPack file has the .whl file extension type. You can download the SyncPack file from the ScienceLogic Support site.

To locate and download the SyncPack:

  1. Go to the ScienceLogic Support site at https://support.sciencelogic.com/s/.
  2. Click the Skylar Automation tab and select SyncPacks.
  3. In the Search field, type the name of this SyncPack and select it from the search results. The Release Version page appears.
  4. On the Files tab, click the down arrow next to the SyncPack version that you want to install, and select Show File Details. The Release File Details page appears.
  5. Click the Download File button to download the SyncPack.

After you download a SyncPack, you can import it to the Skylar Automation (formerly PowerFlow) platform using the Skylar Automation user interface.

To import a SyncPack in the Skylar Automation user interface:

  1. On the SyncPacks page, click Import SyncPack. The Import SyncPack page appears.
  2. Click Browse and select the .whl file for the SyncPack you want to install. You can also drag and drop a .whl file to the Import SyncPack page.
  3. Click Import. Skylar Automation registers and uploads the SyncPack. The SyncPack is added to the SyncPacks page.

You cannot edit the content package in a SyncPack published by ScienceLogic. You must make a copy of a ScienceLogic SyncPack and save your changes to the new SyncPack to prevent overwriting any information in the original SyncPack when upgrading.

To activate and install a SyncPack in the Skylar Automation user interface:

  1. On the SyncPacks page, click the Actions button () for the SyncPack you want to install and select Activate & Install. The Activate & Install SyncPack modal appears.

    If you try to activate and install a SyncPack that is already activated and installed, you can choose to "force" installation across all the nodes in the Skylar Automation system.

    If you do not see the SyncPack that you want to install, click the Filter icon () on the SyncPacks page and select Toggle Inactive SyncPacks to see a list of the imported SyncPacks.

  1. Click Yes to confirm the activation and installation. When the SyncPack is activated, the SyncPacks page displays a green check mark icon for that SyncPack. If the activation or installation failed, then a red exclamation mark icon appears.
  2. For more information about the activation and installation process, click the check mark icon or the exclamation mark icon in the Activated column for that SyncPack. For a successful installation, the "Activate & Install SyncPack" Skylar Automation application appears, and you can view the Step Log for the steps. For a failed installation, the Error Logs window appears.
  3. If you have other versions of the same SyncPack on your Skylar Automation system, you can click the Actions button () for that SyncPack and select Change active version to activate a different version other than the version that is currently running.