Connect with a PowerFlow Product Manager
We Want Your Insights! We would love to connect with you one-on-one to gather your feedback and insights about PowerFlow. Your experiences are key to shaping the future of our product! Why Chat? Share your thoughts on how we can improve Discuss any challenges you’ve faced Help us prioritize features that matter to you Please note that these calls are not intended to address issues that can be resolved through Support Cases. Ready to make an impact? Book a call with us now! Thanks for being part of our journey!ServiceNow 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 ManagementScienceLogic - ServiceNow Integrations: ITOM Licensing Requirements
ScienceLogic maximizes customers' investments in ServiceNow through its powerful suite of pre-built integrations, referred to as SyncPacks. ScienceLogic offers certified ServiceNow scoped applications for streamlined platform integration, accessible via the ServiceNow Store, ensuring seamless compatibility. Understanding the licensing requirements for ServiceNow integrations is crucial for informed decision-making. This document seeks to clarify the IT Operations Management (ITOM) licensing requirements for ScienceLogic integrations with ServiceNow. Its purpose is to eliminate any confusion regarding which integrations necessitate ITOM licensing. Note: ServiceNow’s ITOM licensing is further organized into different tiers. This document is not intended to help identify the suitable tier for your requirements. For any questions related to this, please contact ServiceNow. Scoped Application ServiceNow Module ITOM License requirement ScienceLogic SL1: Customer Service Management Integration Customer Service Management - Cases No ScienceLogic SL1: Incident Automation IT Service Management - Incident No ScienceLogic ServiceNow Integration IT Service Management - CMDB * Situational ScienceLogic SL1: Service Catalog Automation IT Service Management - Service Catalog ** Situational Service Graph Connector for ScienceLogic IT Operations Management - CMDB Yes ScienceLogic Event Integration IT Operations Management - Events Yes * ScienceLogic is actively adding support for cloud infrastructure mappings within our integrations. To effectively leverage these features in accordance with ServiceNow best practices, you might require ITOM licensing. Customers can contact their ScienceLogic representatives for cloud mapping questions. ** ITOM licenses are necessary only if you are implementing a CMDB using ITOM FAQs Here are some frequently asked questions (FAQs) from our customers Q: Are there other scenarios where one would need IT Operations Management (ITOM) licenses for CMDB? A: The necessity for ITOM licenses is primarily influenced by the specific goals of your organization. Customers of ScienceLogic are not required to adopt ITOM unless their integration module is inherently ITOM-based. We observe that customers generally opt for ITOM in the following situations: To deploy out-of-the-box ServiceNow automation for ensuring data quality and reliability. When transitioning to a more advanced, ServiceNow-defined CSDM (Common Service Data Model) framework. Q: Do Business Services in ScienceLogic need IT Operations Management (ITOM) licenses to be integrated into ServiceNow? A: No, it does not. ScienceLogic integrations leverage out-of-the-box ServiceNow CMDB tables, eliminating the need for ITOM licenses. You can effectively replicate ScienceLogic Business Service Models in ServiceNow by leveraging our integrations. Customer Testimonials Discover what our customers are saying about our integrations. “ We like that ScienceLogic has a tight integration with ServiceNow and particularly the fact that we don't need to deploy the additional discovery modules from an integration perspective. ” “ We are able to have a single pane of glass using ServiceNow. All monitoring events and CMDB population is managed by ServiceNow. ScienceLogic is a great monitoring system that integrates well with ServiceNow using its integration server, which provides workflow and rules that work with our systems. ”Microsoft 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 ManagementServiceNow Cases SyncPack v1.1.0 Release Notification
Hello, We are pleased to announce that the ServiceNow Cases SyncPack v1.1.0 has been released. The download for this release can be found on the Support Portal here:https://support.sciencelogic.com/s/release-file/aBtVL0000000LhB0AU/servicenow-case Version 1.1.0 of the ServiceNow Cases SyncPack adds OAuth2 support to the SyncPack. Version 1.1.0 of the ServiceNow Cases SyncPack includes the following feature: Added OAuth2 support to the SyncPack. There are four required parameters you can add to a configuration object to facilitate OAuth2 connection to ServiceNow: snow_oauth_client_id: OAuth2 Client ID from ServiceNow snow_oauth_client_secret: OAuth2 Client secret from ServiceNow snow_oauth_token_url: Full authentication URL, including host and protocol from ServiceNow. For example, "https://<test-instance-name>.service-now.com/oauth_token.do" snow_auth_method: You can enter 'oauth' or 'http_basic' as the value. If no value is provided, 'http_ basic' will be used for connection.Restorepoint SyncPack v2.3.1 Release Notification
Hello, We are pleased to announce that the Restorepoint SyncPack v2.3.1 has been released. The download for this release can be found on the Support Portal here: https://support.sciencelogic.com/s/release-file/aBtVL0000000LfZ0AU/restorepoint-synchronization Version 2.3.1 of the Restorepoint SyncPack updates the compatibility of the "Create Custom Link (GQL)", updates timeouts, and addresses multiple issues with logging. The following features were added in this release: Updated the "Create Custom Link (GQL)" step to be compatible with SL1 versions greater than 12.x.x Replaced SL1 and Restorepoint specific timeouts in all Restorepoint applications with a common read timeout. Updated all API calls to Restorepoint to ensure that the read timeout configuration option scales appropriately to the number of logs. The following issues were addressed in this release: Improved logging and messaging of logs when non-SSH credentials are improperly aligned to Restorepoint based devices. If invalid credentials are provided, those devices are now skipped during the sync instead of causing the sync to fail. (Case: 00433253) Addressed an issue that prevented the "Restorepoint: Get List of Logs" from running successfully due to timeouts. (Case: 00437554)Who will be our next SL1 Innovators?
Hello Nexus Members, Looking to showcase your creativity, innovation, and inspiration? Look no further. In case you're opted out of email, we just launched our SL Innovators Awards!! Our ScienceLogic Innovators Awards were established to recognize and learn from those nerdy by nature, tech buffs, and visionaries using SL1 in pioneering ways to power a better way to work. Show the Nexus Community something cool and innovative you've been working on to achieve real business outcomes. We want to hear your ideas! Submit your application by September 12.
