Skip to content

Commit 47e0491

Browse files
authored
visual guidance in place
1 parent 2cdf4fc commit 47e0491

File tree

1 file changed

+27
-27
lines changed
  • 0_Azure/2_AzureAnalytics/0_Fabric/demos/31_FabricActivatorRulePipeline

1 file changed

+27
-27
lines changed

0_Azure/2_AzureAnalytics/0_Fabric/demos/31_FabricActivatorRulePipeline/README.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,14 @@ Last updated: 2025-03-05
1212
> This process shows how to set up Microsoft Fabric Activator to automate workflows by detecting file creation events in a storage system and triggering another pipeline to run.
1313
1414
<details>
15-
<summary><b>List of References </b> (Click to expand)</summary>
15+
<summary><b>List of Content </b> (Click to expand)</summary>
16+
17+
- [Set Up the First Pipeline](#set-up-the-first-pipeline)
18+
- [Configure Activator to Detect the Event](#configure-activator-to-detect-the-event)
19+
- [Set Up the Second Pipeline](#set-up-the-second-pipeline)
20+
- [Define the Rule in Activator](#define-the-rule-in-activator)
21+
- [Test the Entire Workflow](#test-the-entire-workflow)
22+
- [Troubleshooting If Needed](#troubleshooting-if-needed)
1623

1724
</details>
1825

@@ -34,7 +41,7 @@ https://github.com/user-attachments/assets/95206bf3-83a7-42c1-b501-4879df22ef7d
3441
- Ensure the file name and path are consistent and predictable (e.g., `trigger_file.json` in a specific folder).
3542
3. **Publish and Test**: Publish the pipeline and test it to ensure the trigger file is created successfully.
3643

37-
https://github.com/user-attachments/assets/798a3b12-c944-459d-9e77-0112b5d82831
44+
https://github.com/user-attachments/assets/798a3b12-c944-459d-9e77-0112b5d82831
3845

3946
## Configure Activator to Detect the Event
4047

@@ -60,56 +67,49 @@ https://github.com/user-attachments/assets/282fae9b-e1c6-490d-bd23-9ed9bdf6105d
6067

6168
<img width="550" alt="image" src="https://github.com/user-attachments/assets/8dcadd23-4abb-47ee-82ca-f3868cb818e1" />
6269

63-
https://github.com/user-attachments/assets/43a9654b-e8d0-44da-80b9-9f528483fa3b
70+
https://github.com/user-attachments/assets/43a9654b-e8d0-44da-80b9-9f528483fa3b
6471

6572
2. **Test Event Detection**:
6673
- Save the event and test it by manually running the first pipeline to ensure Activator detects the file creation.
6774
- Check the **Event Details** screen in Activator to confirm the event is logged.
6875

69-
https://github.com/user-attachments/assets/6b21194c-54b4-49de-9294-1bf78b1e5acd
76+
https://github.com/user-attachments/assets/6b21194c-54b4-49de-9294-1bf78b1e5acd
77+
78+
## Set Up the Second Pipeline
79+
80+
1. **Create the Pipeline**:
81+
- In Microsoft Fabric, create the second pipeline that performs the next set of tasks.
82+
- Ensure it is configured to accept external triggers.
83+
2. **Publish the Pipeline**: Publish the second pipeline and ensure it is ready to be triggered.
84+
85+
https://github.com/user-attachments/assets/5b630579-a0ec-4d5b-b973-d9b4fdd8254c
7086

7187
## Define the Rule in Activator
7288

7389
1. **Setup the Activator**:
7490

75-
https://github.com/user-attachments/assets/7c88e080-d5aa-4920-acd6-94c2e4ae0568
76-
91+
https://github.com/user-attachments/assets/7c88e080-d5aa-4920-acd6-94c2e4ae0568
7792

7893
2. **Create a New Rule**:
7994
- In `Activator`, create a rule that responds to the event you just configured.
8095
- Set the condition to match the event details (e.g., file name, path, or metadata).
8196
3. **Set the Action**:
8297
- Configure the rule to trigger the second pipeline.
8398
- Specify the pipeline name and pass any required parameters.
84-
8599
3. **Save and Activate**:
86100
- Save the rule and activate it.
87101
- Ensure the rule is enabled and ready to respond to the event.
88102

103+
https://github.com/user-attachments/assets/5f139eeb-bab0-4d43-9f22-bbe44503ed75
89104

105+
## Test the Entire Workflow
90106

107+
1. **Run the First Pipeline**: Execute the first pipeline and verify that the trigger file is created.
108+
2. **Monitor Activator**: Check the `Event Details` and `Rule Activation Details` in Activator to ensure the event is detected and the rule is activated.
109+
3. **Verify the Second Pipeline**: Confirm that the second pipeline is triggered and runs successfully.
91110

92-
### **Step 4: Set Up the Second Pipeline**
93-
1. **Create the Pipeline**:
94-
- In Microsoft Fabric, create the second pipeline that performs the next set of tasks.
95-
- Ensure it is configured to accept external triggers.
96-
97-
2. **Publish the Pipeline**:
98-
- Publish the second pipeline and ensure it is ready to be triggered.
99-
100-
---
101-
102-
### **Step 5: Test the Entire Workflow**
103-
1. **Run the First Pipeline**:
104-
- Execute the first pipeline and verify that the trigger file is created.
105-
106-
2. **Monitor Activator**:
107-
- Check the **Event Details** and **Rule Activation Details** in Activator to ensure the event is detected and the rule is activated.
108-
109-
3. **Verify the Second Pipeline**:
110-
- Confirm that the second pipeline is triggered and runs successfully.
111+
https://github.com/user-attachments/assets/0a1dab70-2317-4636-b0be-aa0cb301b496
111112

112-
---
113113

114114
## Troubleshooting (If Needed)
115115
- If the second pipeline does not trigger:

0 commit comments

Comments
 (0)