Practical Use-cases of Sitecore Connect
Welcome back to the series on Sitecore Connect! Here's what we have covered in the previous posts.
In the next 2 blogs, we'll explore some practical use cases of Sitecore Connect, demonstrating how it can be applied to real-world scenarios to drive business value. By examining these use cases, you can gain insights into how Sitecore Connect can be leveraged to address your organization's unique integration and automation needs.
Use Case 1: Orchestration of Workflow Data
In our first use case, we look at Bev Incorporation’s Marketing Services team, which wants to automate its workflow management system. The content creation workflow in Sitecore Content Hub must integrate with the delivery team’s workflow in JIRA.
Key Requirements
·?????? New assets must lead to ticket creation, and modified assets must lead to ticket updates.
·?????? JIRA ticket fields should be automatically filled, and asset ticket information must be updated accordingly.
?
Solution
Using Sitecore Connect, the team can set up a real-time webhook event from Content Hub to trigger the automation process. This involves creating issues in JIRA and updating the assets with the JIRA ticket ID, ensuring seamless integration between Content Hub and JIRA. This approach not only streamlines the workflow but also provides data consistency and reduces manual effort.
Step-by-Step Process to Build the Use Case in Sitecore Connect
Step 1: Set Up Real-Time Webhook Event from Content Hub
Sitecore Connect -> New Recipe, that triggers from a Webhook. The Webhook activates when the first event is sent from Content Hub. Copy the Webhook.
Content Hub – Action, to send events on Asset to the webhook copied from Step 1. Hit Test Connection. This completes the connection between Content Hub and Sitecore Connect.
Content Hub – Trigger. Configure the Content Hub DAM to use the action created in Step 2. Post the Ticket ID value if available when an asset is created or modified.
?
Step 2: Configure Connection to JIRA
In Sitecore Connect, create a connection to JIRA.
Step 3: Build the Automation Recipe
?
1.????? Set up conditional actions:
2.????? If the asset is new (Ticket ID value is not available in the Webhook Event), create a new issue in JIRA and update the asset with the JIRA ticket ID. Here we will be using the OOTB JIRA action. Update the newly created ticket ID back to Content Hub’s Asset. For this we will be using a custom action since we do not have OOTB Content Hub actions yet.
?
3.????? If an asset is modified, update the corresponding JIRA ticket. Also using the OOTB JIRA action. Map the relevant data fields from the asset in Content Hub to the corresponding fields in JIRA. Ensure that the JIRA ticket is updated with the latest Ticket ID from Content Hub. It can get confusing for complicated recipes. Ensure you are mapping the right step’s output.
Step 4: Test the Integration
·?????? Create a new asset in Content Hub and verify that a new JIRA ticket is created.
·?????? Modify an existing asset in Content Hub and verify that the corresponding JIRA ticket is updated.
Step 7: Monitor and Maintain
·?????? Regularly check the logs to ensure that the integration is working smoothly.
·?????? Update the recipe as needed to accommodate any changes in the workflow.
By following these steps, you can leverage Sitecore Connect to seamlessly integrate the content creation workflow in Sitecore Content Hub with the delivery team's workflow in JIRA, ensuring data consistency and reducing manual effort.
In the next blog, we will review another use case of Sitecore Connect as a Sync Layer. Stay tuned!