Skylar Automation v3.3.0 and Skyautoctl v2.9.0 are Released
Hello, We are pleased to announce the release of Skylar Automation platform v3.3.0 and the Skylar Automation skyautoctl Command Line Utility v2.9.0. You can download these releases from here: https://support.sciencelogic.com/s/release-version/aBuVL00000019Vt0AI/skylar-automation-33 Skylar Automation (formerly PowerFlow) version 3.3.0 rebrands PowerFlow to Skylar Automation, rebrands powerflowcontrol (pfctl) to skyautocontrol, updates the user interface of the SyncPacks page, and addresses multiple issues. Features PowerFlow is now Skylar Automation. With this release, ScienceLogic has rebranded PowerFlow to Skylar Automation. You will notice this rebranding throughout the 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). The powerflowcontrol (pfctl) command-line utility has been rebranded to skyautocontrol (skyautoctl) as part of the rebrand from PowerFlow to Skylar Automation. All of the older pfctl and iservicecontrol commands still function. Updated the user interface of the SyncPacks page in Skylar Automation to improve clarity around the installed version of SyncPacks: Updated the Active Version column to Installed Version Updated the Change Active Version option in the Actions menu to Change Installed Version Skylar Automation v3.3.0 includes package updates to improve security and system performance. Among other things, these updates address critical vulnerability CVE-2025-49844. Updated Skylar Automation to prevent search engines from indexing Skylar Automation systems by default, improving system privacy and reducing the risk of external exposure. Updated the Redis service to Redis 7.4.6. The following images are included in this release of Skylar Automation: registry.scilo.tools/sciencelogic/sa-api:rhel3.3.0 registry.scilo.tools/sciencelogic/sa-couchbase:6.6.0-15 registry.scilo.tools/sciencelogic/sa-dex:2.37.1-12 egistry.scilo.tools/sciencelogic/sa-worker:rhel3.3.0 registry.scilo.tools/sciencelogic/sa-gui:3.3.0 registry.scilo.tools/sciencelogic/sa-pypi:6.3.1-16 registry.scilo.tools/sciencelogic/sa-rabbit:3.8.35-8 registry.scilo.tools/sciencelogic/sa-redis:7.4.6-0 Issues Addressed The following issues were addressed in this release: Improved stability when using the broker_load_from_backend feature. Skylar Automation steprunner services now handle missing task bodies in Redis more effectively. If a task's payload has been evicted from Redis, the worker will mark the task as failed instead of hanging. This keeps the worker healthy and allows other tasks in the queue to process normally. (Cases: 00554106, 00554534) In some Dex OIDC connector configurations used for Skylar Automation authentication, the email claim may not be provided. Previously, this caused endpoints that relied on the current user identity to fail, showing 500 errors. Now, when the email is missing, Skylar Automation uses the username to identify the user. This ensures widgets, favorites, and related features work correctly by consistently associating data with the authenticated user, even when the email claim is unavailable. (Case: 00524073) Updated the Skylar Automation backup application to clean up the staging directories inside the steprunner containers and to ensure that if the backup fails to copy to a remote system, the temporary files do not hang in the system. (Case: 00513115) Improved error handling to provide more information about why the graphical user interface is not displaying the SystemHealth diagram after logging into Skylar Automation. (Case: 00467441) Addressed an issue that prevented the "Timed Removal" application from running. Thank you, Release ManagementServiceNow CMDB SyncPack v3.6.4 Released
Hello, We are pleased to announce the release of our ServiceNow CMDB SyncPack v3.6.4. This SyncPack includes the following update: Addressed an issue caused by changes to the ServiceNow batch endpoint format when sending CIs to ServiceNow. Spaces are no longer accepted in the URL starting with ServiceNow Zurich. Thank you, Release ManagementSL1 PowerFlow v3.2.0 & PFCTL v2.8.0 Release
Hello, We are pleased to announce the release of SL1 PowerFlow v3.2.0, as well as the release of SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0. Both of these releases are included on the customer portal for download under Product Downloads > PowerFlow Platform > SL1 - PowerFlow 3.2.0. SL1 PowerFlow v3.2.0 adds the ability to bulk download reports, adds a new API endpoint to support bulk downloading of reports, adds two new configuration options to the docker-compose.yml file, and addresses multiple issues. Read on for more details or see the SL1 PowerFlow Release Notes. SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0 updates Couchbase-related checks, updates pfctl checks to require HTTPS certificates, and updates the pfctl init-sps action to use the HOST_ ADDRESS for the PowerFlow system. See the SL1 PowerFlow powerflowcontrol (pfctl) command-line utility v2.8.0 Release Notes. Features (SL1 PowerFlow v3.2.0) This section covers the features that are included in SL1 PowerFlow Platform version 3.2.0: You can now bulk download reports in PowerFlow. When bulk downloading, you have the option to select multiple specific instances of a report to download, or you can select all available instances to download. Added the new DELETE/api/v1/reports/batch API endpoint, which allows you to delete reports in a batch. For more details about using the new endpoint, see the API documentation in the PowerFlow user interface. Added two new configuration options to the docker-compose.yml file to allow access to the Couchbase and RabbitMQ user interfaces without requiring Dex authentication: DISABLE_DEX_AUTH. This option allows you to disable Dex authentication for the Couchbase and RabbitMQ services. ENABLE_SECONDARY_CB_UI. This option allows you to access the Couchbase user interface on port 8091 through secondary nodes without additional port openings. NOTE: The DISABLE_DEX_AUTH and ENABLE_SECONDARY_CB_UI configuration options are intended only for troubleshooting and should be turned off when the PowerFlow system is stable. Blank spaces in configuration options or application variables are now automatically stripped by the PowerFlow API to prevent the spaces from causing issues when PowerFlow reads the values. Updated API service initialization messages to improve clarity when Couchbase indexes are created. Updated the db_host configuration option to function more uniformly across all PowerFlow services. The following images are included in this release of PowerFlow: registry.scilo.tools/sciencelogic/pf-api:rhel3.2.0 registry.scilo.tools/sciencelogic/pf-couchbase:6.6.0-14 registry.scilo.tools/sciencelogic/pf-dex:2.37.1-11 registry.scilo.tools/sciencelogic/pf-worker:rhel3.2.0 registry.scilo.tools/sciencelogic/pf-gui:3.2.0 registry.scilo.tools/sciencelogic/pf-pypi:6.3.1-15 registry.scilo.tools/sciencelogic/pf-rabbit:3.8.35-7 registry.scilo.tools/sciencelogic/pf-redis:6.2.14-6 Issues Addressed (SL1 PowerFlow v3.2.0) The following issues were addressed in this release: Addressed an issue that caused device sync to fail due to region-specific cache key issues. (Case: 00422286) Addressed an issue that caused intermittent authentication failure when using SSO credentials to access PowerFlow. (Case: 00352925) Addressed an issue that caused the pfctl utility to fail when changing the PowerFlow password if the "dollar-sign" character ($) was used in the new password. You can now use the $ character in the PowerFlow password. (Case:00484230) Updated custom mappings values so that you can set any value you want before PowerFlow checks whether the value is unique. Previously, if you attempted to add a custom value and any part of the string matched an existing custom value, you could not attempt to save the value. Addressed an issue that prevented users with view-only permissions from accepting the End User License Agreement (EULA). Additionally, we have released SL1 PowerFlow System Utils v1.2.1 SyncPack today. This release is available on the customer portal here. This SyncPack requires the Base Steps SyncPack. Thank you, Release ManagementBase Steps SyncPack v1.6.0 Release
Hello, We are pleased to announce the release of Base Steps SyncPack v1.6.0. This release deprecates the QueryGQL step from the SyncPack (although it is not removed) and adds the GQLRequest step, which you should use to make GraphQL steps going forward. This release addresses two more issues: Addressed an issue that caused the "Sync Service Requests from ServiceNow to SL1" application to fail after upgrading SL1 from version 12.1.2 to 12.3.5. (Case: 00532575) Addressed an issue that caused the "DeleteFromCache" step to fail when using the 'equals' lookup type instead of 'like'. This release is now available on the customer portal under Product Downloads > PowerPacks & SyncPacks here. Read the full release notes here: https://docs.sciencelogic.com/powerpack_release_notes/sciencelogic_base_steps_syncpack-v160_release_notes.pdf Thank you, Release ManagementServiceNow Service Graph Connector SyncPack v1.1.1 Release
Hello, We're pleased to announce the release of ServiceNow Service Graph Connector SyncPack v1.1.1. Issues Addressed The following issues are addressed in this release: Addressed an issue which prevented the interface sync GraphQL query from working if the SL1 AP2 version was JellyBean or later. Addressed an issue where devices merged in the Service Graph Connector with topology relationships caused an error. As part of the fix for this issue, a new enable_advanced_topology toggle was added to the device and interface syncs. The toggle is disabled by default. Additional System Requirements: "Base Steps" SyncPack version 1.5.5 or later. "ServiceNow Base" SyncPack version 3.8.0 or later. ServiceNow version Tokyo or later with Web Services enabled. ServiceNow CMDBCI Class Models version 1.49.0 or later. You can download the class models from the ServiceNow Store. "Service Graph Connector for ScienceLogic" application version 1.0.2. You can download the application from the ServiceNow Store. NOTE: The Service Graph Connector will not work with Incidents synced to ServiceNow. As a result, the Configuration Item field and the related list on the [Affected CIs] tab will not be populated when using the Service Graph Connector. The Device field on the Event record will also be blank. This issue is addressed in version 4.0.0 of the ServiceNow Incident SyncPack. You can find this SyncPack via the Product Downloads > PowerPacks & SyncPacks tab on the Support portal. Thank you, Release ManagementServiceNow CMDB SyncPack v3.6.3 Release
Hello, We are pleased to announce the release of the ServiceNow CMDB SyncPack v3.6.3. This SyncPack addresses the following issues: Addressed an issue which prevented the interface sync GraphQL query from working if the SL1 AP2 version was 8.18.43-81 (JellyBean) or later. Addressed an issue that caused the device sync to fail due to the "EM71" region being overwritten. To address the issue, the "/api/v1/cache/dev-classes" API endpoint was updated to make the "default_dev_ class_id" and "servicenow_default_id" options configurable. You can download this and other SyncPacks from the Product Downloads > PowerPacks & SyncPacks tab on the Support portal. Please review the release notes for this SyncPack carefully before installing it. Thank you, Release ManagementPowerFlow v3.1.1 & PFCTL 2.7.11 Release
Hello, We are pleased to announce the release of PowerFlow v3.1.1 and PFCTL v2.7.11, which contain important fixes to the PowerFlow 3.1.0 and PFCTL v2.7.10 releases. Please read the Release Notes carefully before installing these releases. These are the highlights only. FEATURES This section covers the features that are included in SL1 PowerFlow Platform version 3.1.1: The following images are included in this release of PowerFlow: registry.scilo.tools/sciencelogic/pf-api:rhel3.1.1 registry.scilo.tools/sciencelogic/pf-couchbase:6.6.0-13 registry.scilo.tools/sciencelogic/pf-dex:2.37.1-10 registry.scilo.tools/sciencelogic/pf-worker:rhel3.1.1 registry.scilo.tools/sciencelogic/pf-gui:3.1.1 registry.scilo.tools/sciencelogic/pf-pypi:6.3.1-14 registry.scilo.tools/sciencelogic/pf-rabbit:3.8.35-6 registry.scilo.tools/sciencelogic/pf-redis:6.2.14-5 ISSUES ADDRESSED The following issues were addressed in this release: Addressed an issue that prevented new schedules from functioning correctly if an application used an ID with both upper and lowercase letters. (Case: 00495740) Jinja2 is now available in the PowerFlow Devpi Server, which allows the ServiceNow CMDB SyncPack to use it while rendering templates. (Case: 00492419) Thank you, Release ManagementServiceNow Base SyncPack v3.8.2
Hello, We are pleased to announce the release of the ServiceNow Base version 3.8.2 SyncPack. The following feature was addressed in this release: Added updates to support "ServiceNow CMDB" SyncPack version 3.6.2. This release is made to work with SL1 version 12.1 or later SL1 PowerFlow version 2.6.0 or later Base Steps SyncPack version 1.5.5 or later ServiceNow version Tokyo or later, with Web Services enabled With the release of this SyncPack, older versions of the ServiceNow Base SyncPack have been suspended. Thank you, Release ManagementServiceNow CMDB v3.6.2 SyncPack
Hello, We are pleased to announce the release of the ServiceNow CMDB v3.6.2 SyncPack. The following enhancements and issues were addressed in this release: Addressed an issue that caused incorrect relationships to be sent to ServiceNow when only child devices were sent for updates. (Case: 00492036) Addressed an issue with the "Sync Devices with SQL" application that caused the device collection mode/state to always show as "active" when synced to ServiceNow, regardless of the actual device state. (Case: 00489043) Addressed an issue where CI classes in ServiceNow with a 'region' field caused issues with disconnects being sent from PowerFlow. The 'region' field from ServiceNow on a CI is now saved on the Python object as "snow_ci_region". (Case: 00493761) Updated the SyncPack to correctly handle an SL1 platform change starting in version 12.1.0 for creating custom links through GraphQL. This release is made to work with SL1 version 12.1 or later SL1 PowerFlow version 2.6.0 or later Base Steps SyncPack version 1.5.5 or later ServiceNow Base SyncPack version 3.8.2 or later ServiceNow version Tokyo or later, with Web Services enabled ScienceLogic SL1: CMDB & Incident Automation certified application version 1.0.81 With the release of this SyncPack, older versions of the ServiceNow CMDB SyncPack have been suspended. Thank you, Release ManagementMicrosoft Teams SyncPack v2.0.0 and Microsoft Teams Automation PowerPack v200
Hello, We are pleased to announce the GA release of the Microsoft Teams v2.0.0 SyncPack and the Microsoft Teams v200 Automation PowerPack integrations for PowerFlow. These releases represent a complete re-architecture of the Teams integration and was driven by a change by Microsoft to the ways Teams works, as detailed in this blog post last fall. Essentially, Microsoft 365 Connectors have been retired, and Microsoft Power Automate was introduced as a replacement. Our new packs make use of Microsoft Power Automate. Please read the release notes and manual carefully, as we have included important details you will need to know before configuring your integration. Here are some highlights from the release notes: Updated the "Create Channel For Event" application to trigger event notification in Microsoft Teams based on the "ms_teams_webhook_url" configuration option, which is a webhook URL generated from Microsoft Teams. When acknowledging an event in Teams, the username of the user who acknowledged the event message is now displayed in SL1. When an event occurs and the event message is posted to Teams, you have three options for handling the event message: Add Note Acknowledge Resolve Added the "enable_existing_channel" configuration option to the "Create Channel For Event" application to allow event notifications to post to an existing Teams channel specified in the "channel_id" configuration option. Updated the "Delete Event From SL1" step name to "Resolve Event From SL1". The Microsoft Teams PowerPack will now create events and event notifications for both major and critical events. Removed the "Major Event Notification to MS Teams" application from the SyncPack. The PowerPack now handles both Critical and Major event notifications using the "Create Channel for Event" application. Removed the "Outage" and "Create Channel Event Notification" applications from the SyncPack. Previously, a refresh token was used to gather user information from adaptive card reactions. The refresh token was removed, and now the user ID is retrieved directly from the workflow using authentication through the Microsoft Authentication Library (MSAL). Optimized the "Microsoft Teams Power Automate" application by reducing API permissions to ensure minimal permission exposure while maintaining essential functionality. This enhancement improves security and aligns with best practices for access control. Microsoft is changing its API policy and the way to use it for adaptive cards. As a result, ScienceLogic has upgraded this SyncPack with the Microsoft authentication library, which is the new way to interact with Microsoft applications in a more authenticated process. For more information, see Microsoft's documentation on MSAL . NOTE: Group calling is not available currently with these packs. Thank you, Release Management
