From d514425c0585fb6996a97eb3c66160a5755f570b Mon Sep 17 00:00:00 2001 From: Vamshi Sagar <224952223+vamshi-pm@users.noreply.github.com> Date: Thu, 30 Apr 2026 13:45:18 +0530 Subject: [PATCH 1/5] Learn Editor: Update sharepoint-connector-actions-triggers.md --- .../sharepoint-connector-actions-triggers.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/business-apps/power-automate/sharepoint-connector-actions-triggers.md b/docs/business-apps/power-automate/sharepoint-connector-actions-triggers.md index 6566e5ef0b..17b88eb4cf 100644 --- a/docs/business-apps/power-automate/sharepoint-connector-actions-triggers.md +++ b/docs/business-apps/power-automate/sharepoint-connector-actions-triggers.md @@ -79,6 +79,16 @@ Allows users of document libraries to trigger a flow after selecting a file. > [!NOTE] > Only flows within the default environment can be executed manually from a SharePoint library. +### When a form is submitted + +Triggers a flow when a form in SharePoint is submitted. + +Use this trigger to start a Power Automate flow when a supported form in SharePoint receives a response. Supported form types include list forms, file upload forms, and document generation forms. This enables automation of downstream processes such as approvals, notifications, routing, or document workflows based on submitted responses. + +The trigger provides submission-level details, including the form ID, responder information, submission time, and responses to form questions. For forms that support file uploads or document generation, the trigger also includes metadata about uploaded or generated documents, where applicable. + +Document generation forms are part of *AI in SharePoint Public Preview*. Access may be limited to customers enrolled in the preview program. List forms and file upload forms are not part of the AI in SharePoint preview. + ### When a site has requested to join a hub site Triggers a flow upon hub site join approval request. @@ -156,6 +166,12 @@ Discards the checkout, rather than saves the file, if you check out a file and d Extracts an archive file into a SharePoint folder (for example, .zip). +### Generate a document from a form + +Creates a document using a document generation template associated with a document generation form in SharePoint. Use this action to generate documents by mapping template fields to corresponding content from supported data sources such as SharePoint lists, Excel, or dynamic values provided within a flow. + +This allows customers to automate document creation scenarios using published document generation forms as part of business processes. The generated output includes file metadata such as the Name, link, location, and generation status of the created document. This action is supported only for document generation (DocGen) forms. Document generation forms are part of *AI in SharePoint Public Preview* and are available only to customers enrolled in the preview program. + ### Get all lists and libraries Gets all lists and libraries. @@ -215,6 +231,12 @@ Gets info about the folder. Uses a file identifier to select the folder. Gets info about the folder. Uses a folder path to select the folder. +### Get form metadata + +Gets info about the form. Use this action to obtain the metadata and schema definition of a selected form before executing downstream automation logic in a flow. The returned metadata includes information such as the form identifier, title, link, form type, defined output format, and the questions used to collect responses. This action can be used in automation scenarios where the structure of the form must be evaluated dynamically at runtime before performing additional operations such as validation, transformation, or routing of collected data. + +Document generation forms are part of AI in SharePoint Public Preview. Access to document generation capabilities may be limited to customers enrolled in the preview program. List forms and file upload forms are not part of the AI in SharePoint preview. + ### Get item Gets a single item by its ID from a SharePoint list. From b6791304a018a08ef25120edd4d5300606a0a57f Mon Sep 17 00:00:00 2001 From: Vamshi Sagar <224952223+vamshi-pm@users.noreply.github.com> Date: Thu, 30 Apr 2026 13:46:09 +0530 Subject: [PATCH 2/5] Learn Editor: Update sharepoint-connector-actions-triggers.md From 8703d52a364f2b16a150026c6a9db8616199a322 Mon Sep 17 00:00:00 2001 From: Vamshi Sagar <224952223+vamshi-pm@users.noreply.github.com> Date: Mon, 4 May 2026 13:14:48 +0530 Subject: [PATCH 3/5] Update pull request template file --- .github/PULL_REQUEST_TEMPLATE.md | 42 ++++++++++++++++++++++++++------ 1 file changed, 34 insertions(+), 8 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 99aeec9af7..4e63199c44 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,10 +1,7 @@ ## Category - [ ] Content fix -- [ ] New article -- [x] Example checked item (*delete this line*) - -> **DELETE THIS LINE BEFORE SUBMITTING** | *For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the `PREVIEW` tab at the top right to preview the rendering before submitting your issue.* +- [x] New article ## Related issues @@ -12,11 +9,40 @@ - partially #issuenumber - mentioned in #issuenumber -> **DELETE THIS LINE BEFORE SUBMITTING** | *If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.* - ## What's in this Pull Request? -> **DELETE THIS LINE BEFORE SUBMITTING** | *Please describe the changes in this PR. Sample description or details around bugs which are being fixed.* +This PR added documentation for a new Power Automate trigger and two actions for SP connector. Following are the details of the trigger and actions. + +**1. Trigger: When a form is submitted** + +Triggers a flow when a form in SharePoint is submitted. + +Customers can use this trigger to start a Power Automate flow when a supported form in SharePoint receives a response. Supported form types include list forms, file upload forms, and document generation forms. This enables automation of downstream processes such as approvals, notifications, routing, or document workflows based on submitted responses. +The trigger provides submission-level details, including the form ID, responder information, submission time, and responses to form questions. For forms that support file uploads or document generation, the trigger also includes metadata about uploaded or generated documents, where applicable. + +**Impact:** +Enables automated workflows to start instantly when a form is submitted across list, file upload, and document generation experiences. +Reduces manual effort by eliminating the need to monitor and trigger follow‑up actions on submissions. +Supports common scenarios such as approvals, notifications, and task routing based on form responses. +Provides a single, consistent trigger across different form experiences, simplifying flow creation. +Lays the foundation for end‑to‑end automation scenarios, including document generation and downstream integrations. + +**2. Action: Get form metadata** +Gets info about the form. Customers can use this action to obtain the metadata and schema definition of a selected form before executing downstream automation logic in a flow. The returned metadata includes information such as the form identifier, title, link, form type, defined output format, and the questions used to collect responses. This action can be used in automation scenarios where the structure of the form must be evaluated dynamically at runtime before performing additional operations such as validation, transformation, or routing of collected data. + +**Impact:** +Agents that are driven by flows can dynamically read form structure and map responses without manual configuration. +Reduces fragility in automation by avoiding dependency on fixed field IDs. +Enables more scalable scenarios such as integrating form responses with other systems, routing, or orchestration. + +**3. Action: Generate a document from a form** +Creates a document using a document generation template associated with a document generation form in SharePoint. Use this action to generate documents by mapping template fields to corresponding content from supported data sources such as SharePoint lists, Excel, or dynamic values provided within a flow. +This allows customers to automate document creation scenarios using published document generation forms as part of business processes. The generated output includes file metadata such as the Name, link, location, and generation status of the created document. This action is supported only for document generation (DocGen) forms. +**Impact: ** +Automates document creation workflows end-to-end within Power Automate. +Eliminates manual steps required to generate documents from templates. +Enables integration with upstream data sources such as lists, Excel, or dynamic inputs. +Supports scalable document generation scenarios across business processes (e.g., HR onboarding, approvals, contract generation). ## Submission guidelines @@ -27,4 +53,4 @@ > - Review all build checks and address the automated errors, warnings, and suggestions. > - *NOTE: The live site is based on the `live` branch. Site owners periodically refresh `live` branch from the `main` branch so merged PRs won't immediately appear on the live site. Please be patient to see your changes appear on the live site.* > -> **DELETE THIS SECTION BEFORE SUBMITTING** + From 42b6410f97646274dcd035e31d92eea7b4837d83 Mon Sep 17 00:00:00 2001 From: Vamshi Sagar <224952223+vamshi-pm@users.noreply.github.com> Date: Mon, 4 May 2026 13:20:31 +0530 Subject: [PATCH 4/5] Update ms.date to May 4, 2026 --- .../introduction-to-sharepoint-business-process-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/business-apps/introduction-to-sharepoint-business-process-integration.md b/docs/business-apps/introduction-to-sharepoint-business-process-integration.md index 576208048d..f318914733 100644 --- a/docs/business-apps/introduction-to-sharepoint-business-process-integration.md +++ b/docs/business-apps/introduction-to-sharepoint-business-process-integration.md @@ -1,7 +1,7 @@ --- title: Business apps and business process automation description: Business apps and business process automation. -ms.date: 06/28/2022 +ms.date: 05/04/2026 ms.service: sharepoint-online ms.localizationpriority: high --- From 4a9ec5865cfb34216e2195cfcaa4f6bcaa3c3f9d Mon Sep 17 00:00:00 2001 From: Vamshi Sagar <224952223+vamshi-pm@users.noreply.github.com> Date: Tue, 5 May 2026 11:01:22 +0530 Subject: [PATCH 5/5] reverted pull request template edits Updated the pull request template to improve clarity and guidance for contributors. --- .github/PULL_REQUEST_TEMPLATE.md | 42 ++++++-------------------------- 1 file changed, 8 insertions(+), 34 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 4e63199c44..99aeec9af7 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,7 +1,10 @@ ## Category - [ ] Content fix -- [x] New article +- [ ] New article +- [x] Example checked item (*delete this line*) + +> **DELETE THIS LINE BEFORE SUBMITTING** | *For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the `PREVIEW` tab at the top right to preview the rendering before submitting your issue.* ## Related issues @@ -9,40 +12,11 @@ - partially #issuenumber - mentioned in #issuenumber +> **DELETE THIS LINE BEFORE SUBMITTING** | *If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.* + ## What's in this Pull Request? -This PR added documentation for a new Power Automate trigger and two actions for SP connector. Following are the details of the trigger and actions. - -**1. Trigger: When a form is submitted** - -Triggers a flow when a form in SharePoint is submitted. - -Customers can use this trigger to start a Power Automate flow when a supported form in SharePoint receives a response. Supported form types include list forms, file upload forms, and document generation forms. This enables automation of downstream processes such as approvals, notifications, routing, or document workflows based on submitted responses. -The trigger provides submission-level details, including the form ID, responder information, submission time, and responses to form questions. For forms that support file uploads or document generation, the trigger also includes metadata about uploaded or generated documents, where applicable. - -**Impact:** -Enables automated workflows to start instantly when a form is submitted across list, file upload, and document generation experiences. -Reduces manual effort by eliminating the need to monitor and trigger follow‑up actions on submissions. -Supports common scenarios such as approvals, notifications, and task routing based on form responses. -Provides a single, consistent trigger across different form experiences, simplifying flow creation. -Lays the foundation for end‑to‑end automation scenarios, including document generation and downstream integrations. - -**2. Action: Get form metadata** -Gets info about the form. Customers can use this action to obtain the metadata and schema definition of a selected form before executing downstream automation logic in a flow. The returned metadata includes information such as the form identifier, title, link, form type, defined output format, and the questions used to collect responses. This action can be used in automation scenarios where the structure of the form must be evaluated dynamically at runtime before performing additional operations such as validation, transformation, or routing of collected data. - -**Impact:** -Agents that are driven by flows can dynamically read form structure and map responses without manual configuration. -Reduces fragility in automation by avoiding dependency on fixed field IDs. -Enables more scalable scenarios such as integrating form responses with other systems, routing, or orchestration. - -**3. Action: Generate a document from a form** -Creates a document using a document generation template associated with a document generation form in SharePoint. Use this action to generate documents by mapping template fields to corresponding content from supported data sources such as SharePoint lists, Excel, or dynamic values provided within a flow. -This allows customers to automate document creation scenarios using published document generation forms as part of business processes. The generated output includes file metadata such as the Name, link, location, and generation status of the created document. This action is supported only for document generation (DocGen) forms. -**Impact: ** -Automates document creation workflows end-to-end within Power Automate. -Eliminates manual steps required to generate documents from templates. -Enables integration with upstream data sources such as lists, Excel, or dynamic inputs. -Supports scalable document generation scenarios across business processes (e.g., HR onboarding, approvals, contract generation). +> **DELETE THIS LINE BEFORE SUBMITTING** | *Please describe the changes in this PR. Sample description or details around bugs which are being fixed.* ## Submission guidelines @@ -53,4 +27,4 @@ Supports scalable document generation scenarios across business processes (e.g., > - Review all build checks and address the automated errors, warnings, and suggestions. > - *NOTE: The live site is based on the `live` branch. Site owners periodically refresh `live` branch from the `main` branch so merged PRs won't immediately appear on the live site. Please be patient to see your changes appear on the live site.* > - +> **DELETE THIS SECTION BEFORE SUBMITTING**