Skip to content

Commit ccc96e2

Browse files
Merge pull request #28549 from MicrosoftDocs/agreements-field-detection-working
Agreements field detection working
2 parents 578908c + b9438c3 commit ccc96e2

11 files changed

Lines changed: 171 additions & 6 deletions
3.86 KB
Loading
38.9 KB
Loading
975 Bytes
Loading
3.71 KB
Loading
67.5 KB
Loading
19.2 KB
Loading
44.6 KB
Loading

microsoft-365/syntex/solutions/agreements-create-agreement.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: ssathyamoort
7-
ms.date: 05/20/2025
7+
ms.date: 05/27/2025
88
audience: admin
99
ms.topic: how-to
1010
ms.service: microsoft-syntex

microsoft-365/syntex/solutions/agreements-create-template.md

Lines changed: 71 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: ssathyamoort
7-
ms.date: 05/13/2025
7+
ms.date: 05/27/2025
88
audience: admin
99
ms.topic: how-to
1010
ms.service: microsoft-syntex
@@ -25,7 +25,7 @@ Templates serve as a predefined structure that standardizes the creation of docu
2525
Once you create and publish a template, users with access to the template can start [generating agreements](agreements-create-agreement.md) from it. Users are asked to [input values for fields](#add-fields-to-a-template), and send it for approval or eSignature based on the [workflow configured](#configure-a-workflow) with the template.
2626

2727
> [!NOTE]
28-
> You can always edit a published template. However, you need to republish the template for the changes to take effect. Documents will be created based of the last published version of the template.
28+
> You can always edit a published template. However, you need to republish the template for the changes to take effect. Documents are created based of the last published version of the template.
2929
3030
## Create a new template from the Agreements app
3131

@@ -133,6 +133,73 @@ To associate a field to a SharePoint list or library, follow these steps when cr
133133

134134
You can also allow users to manually input values with the **Document authors can type in values manually for this field** option. The values input by the authors are only used to generate the document. They won't be added to the SharePoint list.
135135

136+
## Automatically detect potential fields for templates
137+
138+
Automatic field detection for templates uses AI to help template creators quickly identify and insert relevant fields into their templates. It scans the document, detects key content, and suggests fields for review and insertion—reducing manual effort and saving time. To learn more about the AI used in the automatic field detection feature, see [Responsible AI FAQs for SharePoint Agreements](agreements-responsible-ai.md).
139+
140+
### Detect potential fields
141+
142+
On the **Manage templates** panel, select **Set up fields** > **Detect potential fields**. Agreements AI analyzes your template and suggests relevant fields for your review and insertion.
143+
144+
![A screenshot showing the Manage templates panel with the Detect potential field option highlighted.](../../media/content-understanding/agreements-detect-potential-fields.png)
145+
146+
#### Currently supported fields
147+
148+
The following standard fields from the library are detected.
149+
150+
- First party (Single line of text) – The first party on the agreement.
151+
- Second party (Single line of text) – The second party on the agreement.
152+
- Effective date (Date) – The date on which the agreement comes into effect.
153+
- Expiration date (Date) – The date on which the agreement expires.
154+
155+
#### New field suggestions
156+
157+
The following new fields are detected. These fields aren't part of the field library and will get added once you accept the suggestion and add them to the template.
158+
159+
- Governing law (Single line of text) – State, country, or region’s law that governs the interpretation of the agreement.
160+
- Renewal term (Single line of text) – Renewal term after the initial term of the agreement expires.
161+
- Notice to terminate renewal (Single line of text) – Notice period required to terminate renewal or notice period required to prevent the automatic renewal of the agreement.
162+
163+
![A screenshot showing the Manage templates panel to review the potential detected fields.](../../media/content-understanding/agreements-review-detected-fields.png)
164+
165+
#### Review suggestions
166+
167+
Each suggested field card displays the following information.
168+
169+
- The detected content from the document
170+
- The number of occurrences
171+
- The suggested field to associate with the content
172+
173+
You can navigate through the occurrences of detected content using the **Previous** and **Next** buttons.
174+
175+
To apply a field to all detected occurrences and replace them with a placeholder, select **Insert all**. If you prefer not to apply the suggestion, select **Ignore all**.
176+
177+
![A screenshot showing the Manage templates panel to apply the detected fields.](../../media/content-understanding/agreements-apply-detected-fields.png)
178+
179+
#### Edit new field suggestions
180+
181+
For new field suggestions, you’ll see the **Edit** (![Image of the edit icon.](../../media/content-understanding/agreements-edit-icon.png)) option.
182+
183+
![A screenshot showing the option to edit new suggested fields.](../../media/content-understanding/agreements-edit-suggested-fields.png)
184+
185+
Select it to open the **Edit field** panel, where you can:
186+
187+
- Rename the field
188+
- Change the field type
189+
- Modify other field components
190+
191+
Once done, select **Save** to return to the previous panel, and then select **Insert all** to apply the changes.
192+
193+
![A screenshot showing the Manage templates panel showing the Save button.](../../media/content-understanding/agreements-save-suggested-fields.png)
194+
195+
After reviewing and taking appropriate action (insert or ignore) on all suggestions, you'll be able to see the **Go back** button. Select **Go back** to return to the **Set up fields** panel. From there, you can continue adding any other fields needed for your template.
196+
197+
![A screenshot showing the Go back button to review the potential detected fields.](../../media/content-understanding/agreements-review-fields-go-back.png)
198+
199+
> [!NOTE]
200+
> - You can return to the fields panel at any time by selecting the back button in the upper-left corner of the panel. If you rerun the detection process, any previously ignored suggestions will reappear. This allows you to update the template content and detect fields again as needed.
201+
> - You can't edit the standard field suggestions that are already in the field library. Only new field suggestions are editable.
202+
136203
## Add sections to a template
137204

138205
Sections are reusable blocks of content that can be used across templates. For more information, see [Manage sections](agreements-manage-sections.md).
@@ -264,7 +331,7 @@ To set up a mandatory signature workflow, follow these steps:
264331
2. Place your cursor where you want the signature to appear in the document, then insert the fields for signature, initials, and date.
265332

266333
> [!NOTE]
267-
> You only need to insert the signature field locations in the template. During document generation, authors will have to assign signatory email addresses to the fields and send the PDF version of this document for signing.
334+
> You only need to insert the signature field locations in the template. During document generation, authors have to assign signatory email addresses to the fields and send the PDF version of this document for signing.
268335
269336
3. You can add multiple instances of the same signature field throughout the template and then navigate through each occurrence.
270337

@@ -283,7 +350,7 @@ To set up a mandatory signature workflow, follow these steps:
283350
2. Select **Save**.
284351

285352
> [!NOTE]
286-
> During document generation, authors will be directed to the provider platform to assign the signature fields, add signatory email addresses, and send the PDF version of the document for signing.
353+
> During document generation, authors are directed to the provider platform to assign the signature fields, add signatory email addresses, and send the PDF version of the document for signing.
287354
288355
## Publish the template
289356

microsoft-365/syntex/solutions/agreements-overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ ms.author: chucked
44
author: chuckedmonson
55
manager: jtremper
66
ms.reviewer: ssathyamoort
7-
ms.date: 04/02/2025
7+
ms.date: 05/27/2025
88
audience: admin
99
ms.topic: article
1010
ms.service: microsoft-syntex
@@ -62,6 +62,7 @@ With SharePoint Agreements, you can:
6262
|[Manage attachments](agreements-attachments.md) |Manage supporting documents related to an agreement. |
6363
|[View reports](agreements-reports.md) |Learn about the reports that are available to monitor all agreements, their statuses, and other essential metrics. |
6464
|[Receive approval notifications](agreements-notifications.md) |Learn about approval notifications in the Approvals app and in email. |
65+
|[Responsible AI FAQs](agreements-responsible-ai.md) |Learn more about the AI features in the SharePoint Agreements app. |
6566

6667
> [!NOTE]
6768
> SharePoint Agreements is not yet available for Government Community Cloud (GCC) organizations. However, it is planned and will be available in the future.

0 commit comments

Comments
 (0)