Collaboration Tool Integration with HCL Launch

Gone are the days of email as the only team communications tool. With the rapid shift to remote working, dynamic enterprises have embraced tools like Slack and MS Teams to seamlessly file share, chat, and connect.

Now with the latest version of HCL Launch 7.2.0, users can enhance these team communication tools by integrating with HCL Launch. Integration gives you real time visibility into your value stream status with notifications appearing directly in your collaboration tool! Simply use the webhook integration, then subscribe to a Teams, Slack, or communications tool’s Launch channel to get notifications.

HCL Launch Webhooks Integrations

What are webhooks?

Webhooks are essentially HTTP callbacks driven by events. A webhook enables a notification whenever a particular event happens. The webhook URL stores all the required information about the service that needs the information. The text body of the webhook provides details about the event for which the webhook is generated. Webhooks are commonly used in DevOps automations. Now, HCL Launch version 7.2.0 supports outgoing webhooks!

To make keeping in touch with the status of deployments easier, notifications (webhooks) can be triggered according to HCL Launch events like:

• Process started
• Process success
• Process failure
• Scheduled process not started
• Approval completed
• Approval Failed
• External approval completed
• External approval failed.

If you’re not currently using Slack or Teams, the notifications (webhooks) can be sent to any product or application that accepts webhooks. For the application you want to connect to Launch notifications, you will need to create a webhook template that uses the Apache Velocity template formats. For every event type listed above, you can create any number of templates.

 

For example, the webhook template below was created for Microsoft Teams. Notice that the template includes only the body of the webhook and not the URL.

Webhook Templates also have a Teams association with them. This keeps access limited to who can view the webhook template.

The webhook URL is configured at the Application environment level. This way, at the enterprise level the templates can be reused, and individual teams can setup notifications to different destinations at their application environment level.

See below that at the application environment level, you can setup multiple webhooks by specifying:

1. Webhook URL (You can get this from your Slack/MS-Teams integration)
2. HCL Launch event for which this URL needs to be triggered.
3. The webhook template that needs to be used.
4. Multi-select different environments on which you need webhooks to be trigged.

Drown out the noise and keep your team focused. Only get relevant notifications by setting alerts according to the team a user is on. For example, a webhook triggered notification for lower environments can be sent to a specific Teams or Slack channel, and production notifications to a different channel.

Your enterprise deployments are important. Our on-demand webinar What’s New in Launch 7.2.0, covers the newest features like that enable Launch users to deploy anything, anywhere – faster!