Installation and Configuration Guide

Change Summary

Overview

TechnoMile’s Contracts Suite solution helps Government Contractors manage the entire Contract Lifecycle initiating from pre-award to post-award through a user-friendly setup and administration tasks. The Contracts Suite solution is built on a highly flexible and scalable Microsoft Dynamics platform where users can easily configure and manage Contract and Subcontract processes.

Our Contract Lifecycle Management (CLM) product, part of the Contracts Suite solution, delivers a robust set of functionalities with role-based access controls to Contracts, Modifications, Closeouts, Task Orders, Subcontract Agreements (NDAs, SoWs, and TAs), CDRLs, CLINs, Sub CLINs, Approval Workflows, FAR/DFAR Clauses, Small Business Subcontracting, Delivery Orders, Document Repository, and Subcontracts.

This guide will take you through the installation and configuration steps for the Contracts Suite app.

Audience

• Microsoft Dynamics Administrators

• IT Support

Prerequisites

Please contact TechnoMile Support or email support@technomile.com for the following information prior to starting your installation:

• TechnoMile Contracts Suite installation package version 2025.1 or higher

• Power Automate Config (.csv file)

• Document Templates (.zip file)

• Product Configuration Data (.csv file)

• Email Templates (.csv file)

• Contract Closeout Configuration Template (.csv file)

Installation

It is recommended to install the Contracts Suite app in a Sandbox environment for testing, prior to its installation in your Production environment.

Please contact TechnoMile Support or email support@technomile.com for a separate Contracts Suite installation package for your Sandbox/Test environment.

Import TechnoMile Contracts Suite Solution

IMPORTANT

Check all Power Automate Flows to ensure that they are turned ON. If a Power Automate Flow is not ON, select Edit for the flow, create its connections, and turn it ON.

1. Login to your Microsoft Dynamics instance.

2. Open App Launcher and click Power Apps. 

3. Go to Solutions and click Import. 

4. Click Browse. 

5. Select the TechnoMile GRC Suite installation package that you had received from TechnoMile, which is saved on your system and click Next. 

6. Click Import.
   A message displays Solution “TechnoMile GRC Suite” imported successfully and the Solutions page displays the installed TechnoMile GRC Suite package. 

Configuration

Import Power Automate Configuration Data

This step is performed to import the current instance URLs of all your Power Automate Flows that are used to trigger these flows from various Web Resources.

1. Open App Launcher and click Power Apps.

2. Click Environment and select an Environment of your choice. 

3. Go to Solutions, search for, and click TechnoMile GRC Suite. 

4. Click All and select Cloud flow. 

5. Open the PowerAutomateConfig.csv file that you had received from TechnoMile, which is saved on your system.

6. Copy and paste a Flow Name from the Excel file into the search bar against Cloud flow in the Solutions page.  

7. Click Sequential Approval Flow in search results. Power Automate window opens.

8. Click Edit.

9. Expand When a HTTP request is received and click the Copy Url icon. 

10. Open the PowerAutomateConfig.csv file again and paste the URL against Sequential Approval Flow under the Flow URL column as highlighted in the image below and save the file.

11. Similarly, perform the same steps as shown above for all the other remaining flows present in the file. 

12. Click the gear icon and select Advanced Settings. 

13. Open the Settings sitemap and click Data Management. 

14. Click Imports. 

15. Click IMPORT DATA. 

16. Click Choose File. 

17. Select the edited PowerAutomateConfig.csv file that you had received from TechnoMile, which is saved on your system and click Next.

18. Review the upload summary and click Next to continue. 

19. Click Next again. 

20. Click the drop-down menu under the Microsoft Dynamics 365 Record Types column, select Power Automate Config, and click Next. 

21. Click Next again. 

22. Click Next again.

23. Click Submit. 

24. Click Finish.
    PowerAutomateConfig.csv file is imported and Power Automate Config records display in your Microsoft Dynamics instance.
    

Import Document Templates

This step is performed to import all the Base Document Templates that are supported in the Contracts Suite app, which can later be customized, as per your requirements.

Edit Code in extracted Document Template file

1. Right-click the zipped folder that you had received from TechnoMile and extract its file(s) onto your system.
    

2. Click Yes on the confirmation message.
   Word file is converted into a zipped folder. 

3. Right-click the recently zipped folder and extract its file(s) onto your system. XML files along with other folders are extracted.

4. Right-click the item1.xml file and open it in an application such as Notepad/Notepad++. 

5. Copy its Object Type Code that is available in the first line against DocumentTemplate. 

6. Paste the Code as Old value into an application such as Notepad.
   

7. Go to a new tab using the following URL:
   api/data/v9.1/EntityDefinitions?$select=LogicalName,PrimaryNameAttribute,ObjectTypeCode

8. Add your source instance URL as a prefix to the above URL. 

9. Search for negotiation and copy its Object Type Code. 

10. Paste the Code as New value into Notepad. 

Edit Code in extracted XML file(s)

1. Copy and paste the old Object Type Code into the search bar of the extracted Generate Negotiation Memo folder.

   NOTE

   There are two XML files and in some scenarios, there may be up to three XML files that contain the Code.

   

2. To edit an XML file, open it in an application such as Notepad/Notepad++.

3. Find the Old value and replace it with the New value and save the file.

4. Similarly, perform the same steps as shown above for all the other remaining files that contain the Code.  

5. Go back to the extracted Negotiation Memo folder, select all its available files as shown in the image below, and right-click.

6. Select Send to and then select Compressed Folder to compress all the files into a zipped folder.
   All the files are compressed/zipped. A confirmation message displays.

7. Click Yes. Zipped folder is converted into a Word file. 

8. Similarly, perform the same steps as shown above for all the other remaining Document Template files as listed below:

   • BOE Document.docx

   • BOE Document_Complex.docx

   • ContractBrief.docx

   • Contract-LOF.docx

   • LOF-CLINS.docx

   • NDA.docx

   • PIA.docx

   • Proposal Summary.docx

   • ProposalDoc.docx

   • Self Evaluation Form.docx

   • SoW.docx

   • Subcontract Letter of Commitment.docx

   • Subcontract Offer letter.docx

   • Subcontractor Reps and Certs.docx

   • SubK Mod.docx

   • SubK.docx

   • TA.docx

   • TINACertification.docx 

Upload a Document Template file

1. Go back to Advanced Settings.

2. Re-open the Settings sitemap and click Templates. 

3. Click Document Templates. 

4. Click Upload Template.

5. Click Browse.

6. Select the Negotiation Memo.docx Word file that is saved on your system.

7. Click Upload.

   NOTE

   You can edit the Name of this file, if required.

   Negotiation Memo.docx Word file is uploaded.

8. Similarly, perform the same steps as shown above to upload all the other remaining Document Template files.

Import Product Configuration Data

1. Re-open the Settings sitemap and click Data Management.

2. Click Imports.

3. Click IMPORT DATA.

4. Click Choose File.

5. Select the Product Configuration Data.csv file that you had received from TechnoMile, which is saved on your system.

6. Click Next. 

7. Click Next again.

8. Click Next again.

9. Click the drop-down menu under the Microsoft Dynamics 365 Record Types column, select Product Configuration, and click Next. 

10. Click Next again.

11. Click Next again.

12. Click Next again.

13. Click Submit.

14. Click Finish.
    The Product Configuration Data.csv file is imported and the Product Configuration records display in your Microsoft Dynamics instance. 

Create Email Templates

1. Go to Email Templates and click New. 

2. Go to the Guide & Instructions tab and scroll down the entire tab to view and follow all the steps listed on this tab under various topics to create your own custom Email Template. 

Import Email Templates Data

1. Re-open the Settings sitemap and click Data Management.

2. Click Imports.

3. Click IMPORT DATA.

4. Click Choose File.

5. Select the Email Templates.csv file that you had received from TechnoMile, which is saved on your system.

6. Click Next. 

7. Click Next again.

8. Click Next again.

9. Click the drop-down menu under the Microsoft Dynamics 365 Record Types column, select Email Templates, and click Next. 

10. Click Next again.

11. Click Next again.

12. Click Submit.

13. Click Finish.
    The Email Templates.csv file is imported and the Email Templates display in your Microsoft Dynamics instance. 

Import Contract Closeout Task Configuration Data

Once imported, these Tasks are created automatically when a Closeout record is generated. These Tasks can act as a Master Task for all of Closeouts.

1. Re-open the Settings sitemap and click Data Management.

2. Click Imports.

3. Click IMPORT DATA.

4. Click Choose File.

5. Select the Contract Closeout Configuration Template.csv file that you had received from TechnoMile, which is saved on your system.

6. Click Next. 

7. Click Next again.

8. Click Next again.

9. Click Next again.

10. Click the drop-down menu under the Microsoft Dynamics 365 Record Types column, select Task Configuration, and click Next. 

11. Click Next again.

12. Click Next again.

13. Click Next again.

14. Click Submit.

15. Click Finish.
    Contract Closeout Configuration Template.csv file is imported and the Contract Closeout Task Configuration records display in your Microsoft Dynamics instance.
     

Configure Multi-Currency Settings

Important Prerequisite: For this feature to work, ensure that data is imported into the Exchange History table for the required Exchange Dates, so that the table can then be used to update latest Exchange Rates for different Currencies in the system.

1. Go back to Advanced Settings.

2. Click the funnel icon to access Advanced Find. 

3. In the Look for: field, select Currencies, and click Results. 

4. Click New. 
    

5. Select Currency Code, enter Currency - Name, Precision, and Symbol, then enter Currency Conversion, and click Save and Close. Currency is created. 

Access Team Templates

This step is performed to create an Access Team Template that can be used for maintaining the Proposal Team on Proposal records.

1. Re-open the Settings sitemap and click Security. 

2. Select Access Team Templates and click New. 

3. Create a new Team Template.

   1. Enter a Team Template Name.
      Note: Fields marked by red asterisk (*) sign are mandatory.

   2. Select Entity as Proposal.

   3. Select Access Rights as Append, Append To, Read, and Write.

   4. Click Save & Close. 

Configure Proposal Form Settings

With this step, you can view the Access Team on the Form of Proposal records as the Proposal Team.

1. Go to http://make.powerapps.com/

2. Go to Solutions and click TechnoMile GRC Suite. 

3. Click All and select Table. 

4. Search for and click Proposal.

5. Go to the Forms tab and click Information that has Form type as Main. 

6. Click Switch to classic. 

7. Form: Proposal opens, scroll down to the Proposal Team tab and double-click the Users section. 

8. Select Team Template as Proposal Team Template and click OK. 

9. Click Save and then click Publish. 

Add Users to Proposal Access Team

This step is performed to configure the workflow - Add User to the Proposal Access Team to use the newly created Access Team.

1. Go back to TechnoMile GRC Suite by performing the same steps as shown in the Configure Proposal Form Settings section.

2. Click All and select Process. 

3. Search for and click Add User to the Proposal Access team.

4. Click Set Properties against a User that you want to add to the Proposal Access Team. A popup window opens.

5. Click the lookup icon and select Proposal Team Template. 

6. Click Save and Close.

7. Similarly, perform the same steps as shown above to add other Users.
   Other Users are added to the Proposal Access Team. 

8. Click the Save icon and then click Activate. Process Activate Confirmation message displays.

9. Click Activate. Process is activated.

Remove Users from Proposal Access Team

This step is performed to configure the workflow - Remove users from proposal access team to use the newly created Access Team.

1. Go back to TechnoMile GRC Suite by performing the same steps as shown in the Configure Proposal Form Settings section.

2. Click All and select Process.

3. Search for and click Remove users from proposal access team.

4. Click Set Properties against a User that you want to remove from the Proposal Access Team. A popup window opens.

5. Click the lookup icon and select Proposal Team Template. 

6. Click Save and Close.

7. Similarly, perform the same steps as shown above to remove other Users.

   Other Users are removed from the Proposal Access Team.
   

8. Click the Save icon and then click Activate. Process Activate Confirmation message displays.

9. Click Activate.  Process is activated.

Configure Global Search Settings

This step is performed to include entities into the Global Search feature of the Contracts Suite app.

1. Go back to Advanced Settings.

2. Re-open the Settings sitemap and click Administration.

3. Click System Settings.

4. Go to the General tab.

5. Scroll down to Set up Search and click Select… 

6. Select and move an entity from Available Entities to Selected Entities using the Add button and click OK.

   NOTE

   You can also remove an entity from Selected Entities using the Remove button.

   IMPORTANT

   To refine your search, ensure that you select all those entities for which you want to display filtered search results.

   

   Entity is added.

   Global Search Settings are configured and the selected entities display in the list of Global Search Filters.
   

Configure SharePoint Settings for Document Storage

This step is to be performed for enabling SharePoint Document Storage for selected entities.

1. Go back to Advanced Settings.

2. Re-open the Settings sitemap and click Document Management.

3. Click Configure Server-Based SharePoint Integration.

4. Choose Online and click Next. 

5. Enter your SharePoint Site URL that you wish to use for server-based configuration and click Next. Validation Succeeded message displays.

6. Click Finish. SharePoint Settings are configured.

7. Click Document Management Settings. 

8. Select the entities for which you want to enable SharePoint Document Storage.

9. Enter your SharePoint Site URL and click Next. 

10. Click Next again. 

11. Click OK to confirm. Selected entities display with Status as Succeeded.

12. Click Finish. Document Management Settings are configured.

13. Open App Launcher and click SharePoint. 

14. Copy and paste the same SharePoint Site URL to open it in a new tab and click Site contents.

    Note that the folders for the selected entities can be seen under SharePoint Site contents.
    

15. Go back to Solutions in Power Apps by performing the same steps as shown in the Import Power Automate Config section.

16. Click Default Solution. 

17. Click All and select Cloud flow.
     

18. Click the Agreement - Send Email on Checked In/Out link.
    Power Automate window opens.

19. Click Edit. 

20. Expand When an ITEM or a file is modified in the flow.

21. Copy and paste the SharePoint Site Address that you had added in the Configure SharePoint Settings for Document Storage section.

22. Select List or Library Name and click Save. 

Configure DocuSign Settings

This step is performed to configure a DocuSign account that will then enable the E-Signature functionality in the Contracts Suite app.

1. Go to DocuSign using the following URL: https://admindemo.docusign.com/

2. Enter your Email Address and click CONTINUE.

3. Enter your Password and click LOG IN.

4. Go to the Settings tab.

5. In the INTEGRATIONS section, click Apps and Keys. 

6. Click the Copy to clipboard icon against User ID. 

7. Paste the copied User ID as User ID into an application such as Notepad.

8. Similarly, copy the API Account ID and Base URI as Account ID and Base URL into Notepad. 

9. Click ADD APP AND INTEGRATION KEY. 

10. Enter App Name and click CREATE APP. 

11. Click the Copy to clipboard icon against Integration Key. 

12. Paste the copied Integration Key as Integration Key into Notepad. 

13. Click Generate RSA. 

14. Click the Copy to Clipboard icon against Private Key. 

15. Paste the copied Private Key as Private Key into Notepad. 

16. In the DocuSign RSA Keypair window, click Close.

17. Click Add URI. 

18. Enter a dummy URL such as https://dummy.com under Redirect URI and click SAVE.
    App is created. 

Request Application Consent

1. Replace , , and  in the following URL with Integration Key pasted into Notepad and Redirect URI used in step 16 of the Configure DocuSign Settings section.

   /oauth/auth?response_type=code&scope=signature%20impersonation&client_id=&state=a39fh23hnf23&redirect_uri=

   EXAMPLE: Upon replacing Base URL, Integration Key, and Redirect URI as per this Guide, you will get the following URL:

   https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=91a7ace4-8601-4bb8-80b3-70c6a509b256&state=a39fh23hnf23&redirect_uri=https://dummy.com

   NOTE

   The Base URL for Developer account is https://account-d.docusign.com and Base URL for Production account is https://account.docusign.com

2. Go to the updated URL created with your Integration Key and Redirect URI from your browser (where you are logged into your DocuSign account) and click ACCEPT. 

DocuSign Product Configuration

1. Go back to your Microsoft Dynamics instance.

2. Go back to the Product Configurations window from Advanced Find and click DocuSign.

3. Copy the JSON Value. 

4. Paste the JSON Value into Notepad.

5. Update Base URL, User ID, Account Id, Integration Key, and Private Key values within the double quotation marks with the corresponding values pasted into Notepad in step 13 of the Configure DocuSign Settings section.

   IMPORTANT

   The value of Audience must be account-d.docusign.com for a Developer account and account.docusign.com for a Production account.

   NOTE

   While updating Base URL value, you need to retain the text - /restapi/.

   

6. Copy and paste the updated JSON Value from Notepad back into the JSON Value field and click Save. 

DocuSign Connect Settings

This step is to be performed to set up a call back as Power Automate (DocuSign Connect) in DocuSign account so as to receive back status updates in Microsoft Dynamics.

1. Go to the Power Automate Configs window from Advanced Find and click DocuSign Connect. 

2. Copy the Flow URL and paste it as Flow URL into Notepad.  

3. Go back to your DocuSign account as shown in step 1 of the Configure DocuSign Settings section.

4. In the INTEGRATIONS section, select Connect.

5. Click ADD CONFIGURATION and select Custom. 

6. Enter a Name.

7. Copy and paste the Flow URL into the URL to Publish field. 

8. Select the Documents and Recipients checkboxes under Include Data. 

9. Select all the following checkboxes under Envelope Events in the Trigger Events section:

   • Envelope Sent

   • Envelope Delivered

   • Envelope Signed/Completed

   • Envelope Declined

   • Envelope Voided

10. Select all the following checkboxes under Recipient Events in the Trigger Events section:

    • Recipient Sent

    • Recipient Delivery Failed

    • Recipient Delivered

    • Recipient Signed/Completed

    • Recipient Declined

    • Recipient Authentication Failure

11. Click Add. Custom Configuration Settings are completed.

Configure Document Compare Settings

Create SharePoint App

1. Replace  in the following URL and go to the updated URL from your browser:
   .sharepoint.com/_layouts/15/appregnew.aspx"https://.sharepoint.com/_layouts/15/appregnew.aspx

2. Click Generate against Client Id and Client Secret, enter appropriate values in the Title, App Domain, and Redirect URI fields, and click Create.
   Note that the Redirect URI field value can be any dummy URI since it has no functional use.   App is created.

3. Copy Client Id and Client Secret and paste them as Client Id and Client Secret into an application such as Notepad. 

4. Replace  in the following URL and go to the updated URL from your browser:
   .sharepoint.com/_layouts/15/appinv.aspx"https://.sharepoint.com/_layouts/15/appinv.aspx

5. Enter the value of Client Id (copied in Notepad in the previous step) as App Id and click Lookup.
   Title, App Domain, and Redirect URI fields are auto-populated. 

6. Click Create.

7. Click Trust It. 

8. Replace  in the following URL and go to the updated URL from your browser:
   .sharepoint.com/_layouts/15/appprincipals.aspx"https://.sharepoint.com/_layouts/15/appprincipals.aspx

9. Copy the value after the @ sign next to the newly created App (as highlighted in the image below) and paste it as Tenant ID into Notepad. 

SharePoint Product Configuration

1. Go to the Product Configurations window from Advanced Find and click SharePoint.

2. Copy and paste the JSON Value into Notepad.

3. Update Client Id, Client Secret, and Tenant ID values within the double quotation marks with the corresponding values copied in Notepad in step 9 of the Create SharePoint App section. 

4. Copy and paste the updated JSON Value from Notepad back into the JSON Value field and click Save. 

Configure Draftable Settings

1. Go to the Draftable URL provided to you by TechnoMile and click Log In. 

2. Log in using the credentials provided to you by TechnoMile.

3. Click the vertical ellipses icon and select Account. 

4. Click API Credentials.

5. Copy Base URL, Account ID Live, and Auth Token Live and paste them as Base URL, Account ID, and Auth Token into an application such as Notepad. 

Draftable Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Draftable.

2. Copy and paste the JSON Value into an application such as Notepad.

3. Update Base URL, Account ID, and Auth Token values within the double quotation marks with the corresponding values copied in Notepad in step 5 of the Configure Draftable Settings section. 

4. Copy and paste the updated JSON Value from Notepad back into the JSON Value field and click Save. 

Clause Library API Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Clause Library API.

2. Edit the JSON Value field by updating the username, password, and base_url values within the double quotation marks as per the corresponding values provided to you by TechnoMile.

3. Click Save. 

Clause Library Refresh Job Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Clause Library Refresh Job.

2. Edit the JSON Value field by updating the clause type, last updated date, and Admin values within the double quotation marks as per your requirements.

   You can also enter a list of comma-separated values for clause type, if required. You can enter the email address of an Admin who will receive the emails once the Clauses are updated.

3. Click Save. 

4. Run the Clause Library batch for the first time.

5. Get the date from the customer for which they would like to see the Clauses, update it in the Clause Library Refresh Job, and run the Master Mass Update Flow.

   1. Go to make.powerapps.com

   2. Go to Solutions and click TechnoMile GRC Suite.

   3. Click Cloud flows, search for, and click Master Mass Update Flow.

   4. Click Run. Run flow window opens.

   5. Click Run flow to proceed. 

   6. Process runs and a success message displays.
      Clause Library Refresh Job is added to the Active Clause Library Refresh Jobs list.
      

      Configure Key Clauses

      1. Go to Clauses and select Yes for a Clause in the Is Key Clause column.
         

      2. Click the Save icon.
         
         Clause is marked as Key.

      3. Go to the Key Clauses list view to view the recently modified Clause in this list.
         

Agreement Mod General Attributes Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Agreement Mod General Attributes.

2. Edit the Value field by updating it with logical names of all mandatory fields that are to be populated from a parent Agreement record into Agreement Mod records.

   IMPORTANT

   Ensure that you include logical names of all mandatory fields in the Value field such as Agreement Manager.

   

3. Click Save. 

TM OCR API Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click TMOCRAPI.

2. Edit the JSON Value field by updating the Username, Password, ClientId, ClientSecret, TokenURL, BaseURL, ObligationsURL, and FormTypes values within the double quotation marks as per the corresponding values provided to you by TechnoMile. Ensure that you modify the values within the quotations. The final result should have the following syntax: 

3. Click Save. 

Configure OAuth in Success Callback in OCR

In Power Automate, you can configure the OAuth in Success Callback. You must provide the following information to TechnoMile to configure the OAuth Authentication in the Success Callback of OCR Process (OCR Response on Success).

1. Follow the steps below to generate these IDs.

2. Ensure that you replace the Scope URL with the Microsoft Dynamics URL of your current instance . 

Azure Active Directory Application User Configuration

Please send the Client ID and Client Secret values generated for the new Azure AD user to TechnoMile, so that we can authorize this user for the eBuy Scraper Web Service.

1. Go to http://portal.azure.com/

2. In the Global Search field, search for and click App registrations. 

3. Click New registration. 

4. In the Name field, enter TechnomileWebServiceAppUser.

5. In the Supported account types section, choose Accounts in this organizational directory only. 

6. Click Register.

7. Copy the Application ID and Directory ID.
   It may be helpful to paste this information into an application such as Notepad or any other application, as this will be used in later steps. 

8. Go to the API permissions tab and add the required API permissions. 

   • For a common Microsoft dynamics.com instance:

     1. On the API permissions tab, click Add a permission.

     2. Click Dynamics CRM. 

     3. Select the user_impersonation checkbox.

     4. Click Add permissions. 

   • For a GCC HIGH Microsoft dynamics.us instance:

     1. On the API permissions tab, click Add a permission.

     2. On the APIs my organization uses tab, search for Common Data Service.

     3. Select the user_impersonation checkbox. 

     4. Go to the Certificates & secrets tab and click New client secret. 

     5. In the Add a client secret window, enter a Description such as TMWSExpirationKey.

     6. In the Expires section, choose Never. 

     7. Click Add.

     8. Copy the Client Secret.

        IMPORTANT

        This value is ONLY visible upon creation. If you leave the page and come back, the value will NO longer be visible.

        

Wage Determination Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Wage Determination.

2. Edit the JSON Value field by updating the client_id, client_secret, and baseUrl values within the double quotation marks as per the corresponding values provided to you by TechnoMile. Ensure that you modify the values within the quotations. The final result should have the following syntax:  

Convert To Contract Stages Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click Convert To Contract Stages.

2. Edit the JSON Value field by updating the Stages and AllowDuplicates values within the double quotation marks, as per your requirements and click Save.

   NOTE

   If the value assigned to AllowDuplicates is set to true, then multiple Contracts can be created for an Opportunity. Therefore, if you want to restrict a user to create only one Contract per Opportunity, ensure that you set AllowDuplicates to false.

   Create Contract button becomes visible on Opportunities that are in the specified Stage(s). 

CPAR/OCI Approval/Review Product Configurations

Update the JSON Value field for the CPAR Approval/Review configuration record.

1. Go back to the Product Configurations window from Advanced Find and click CPAR Approval/Review.

2. Click the JSON Value field and modify the desired setting to reflect Parallel or Sequential. Ensure that you modify the values within the quotations. The final result should have the following syntax:
   {"Approval":"Sequential", "Review":"Parallel"}By default, both Approval and Review are set to Sequential however, you can modify both or individual values to Parallel.

3. Click Save. 

   NOTE

   The OCI Approval/Review configuration record can have JSON Value as Parallel only.

OCI Team Member Product Configuration

Update the JSON Value field for the OCI Team Member configuration records.

1. Go back to the Product Configurations window from Advanced Find and click OCI Team Member Configuration.

2. Click the JSON Value field and enter the email addresses of the Team Members you want to include by default in OCI, during its creation. You can also enter a list of comma-separated values containing email addresses for adding multiple OCI Team Members as Reviewers, Approvers, and Final Reviewers.

3. Click Save. 

Agreement Agreement Mod General AttributesConfiguration

Update the JSON Value field for the OCI Team Member configuration records.

1. Go back to the Product Configurations window from Advanced Find and click OCI Team Member Configuration.

2. Click the JSON Value field and enter the email addresses of the Team Members you want to include by default in OCI, during its creation. You can also enter a list of comma-separated values containing email addresses for adding multiple OCI Team Members as Reviewers, Approvers, and Final Reviewers.

3. Click Save. 

Configure Product Configuration Form

1. Ensure that you remove the JSON Value field from a Form once all the configurations are completed.

Service Admin Product Configuration

This step is to be performed to set up a Service Admin - User who will act as a sender of all the emails going out from the Contracts Suite app.

1. Go back to the Product Configurations window from Advanced Find and click Service Admin.

2. Select a User in the User field that will be used to send the emails and enter the email address of the Service Admin in the Value field.

3. Click Save. 

IMPORTANT

You must enable the Send As privilege for the Admin to ensure that the emails will be sent. An Exchange license is required, as you must also configure an email box for the Admin.

1. In the Compliance application, click the gear icon and select Personalization Settings.

2. In the Set Personal Options window, go to the Email tab.

3. Select the Allow other Microsoft Dynamics 365 users to send email on your behalf checkbox.

4. Click OK. 

Obligations Default Settings Product Configuration

The configuration must be updated to reflect a user from the current instance who will be the default owner and duration for calculating the default due date for Obligations management.

NOTE

The duration calculation is today+5days.

1. Go back to the Product Configurations window from Advanced Find and click Obligations Default Settings.

2. The JSON Value field must be updated to reflect a user from the current instance and a duration. Ensure that you modify the values within the quotations. The final result should have the following syntax:
   {"User":"CEE98E4F-45B0-EB11-8236-000D3A332511","Duration":"5"}

3. Click Save. 

Amount Field Mapping Product Configuration

This field is used for mapping the amount of OCI, if the CLIN type is empty.

1. Go back to the Product Configurations window from Advanced Find and click Amount Mapping for no clin type selected.

2. The JSON Value field must be updated to reflect a field name from CLIN that you will want to populate for OCI, if the value is null. Ensure that you modify the values within the quotations. The final result should have the following syntax:
   {"ObligatedFieldName":"clm_obligatedcost", "FundedFieldName":"clm_fundedcost"}

3. Click Save. 

Lock Contract Stages Product Configuration

Use this configuration to record the Stages that should lock a Contract to prevent changes or updates.

1. Go back to the Product Configurations window from Advanced Find and click Lock Contract Stages.

2. The JSON Value field must be updated. Ensure that you modify the value within the quotation. You can also enter a list of comma-separated values. The final result should have the following syntax:
   {"Stages":"Administer,Close Out,Archived"}
   EXAMPLE: Locked fields on a Contract that is in the Administer Stage. 

Contract Clone: Contract Entity Fields Product Configuration

1. Go back to the Product Configurations window from Advanced Find and click ContractCloneGeneralFields.

2. The JSON Value field must be updated with logical names of fields to be cloned as shown below.

   {
   "fields":
   [
   {
   "logical_name": "clm_revisionversion"
   },
   ]
   } 

3. Click Save. 

4. Go to a Contract record and clone it.
   Note that the value of the Revision Version field is copied into the cloned Contract record.

   IMPORTANT

   If a field is NOT specified in the above JSON Value field, the value of that field will NOT be copied into the cloned Contract record.

   

Contract Clone: Child Entity Fields Product Configuration

This product configuration allows admins to manage cloning for child entities by specifying which fields to be excluded. All other fields are cloned by default. 

1. Go to the Product Configurations window from Advanced Find and click ContractCloneIgnoreRelatedTableFields.

2. In the JSON Value field, enter the child fields you want to exclude from cloning.

   

3. Click Save.

Historical Clauses Product Configuration

NOTE

This configuration extracts historical Clauses data for all the listed Clause Types into your Clause Library.

1. Go back to the Product Configurations window from Advanced Find and click Historical Clauses.

2. The Value field must be updated with a list of comma-separated values for Clause Types, as shown below.

3. Click Save. 

Generic - Send For Final Review Power Automate Configuration

Update the Flow URL field for the Generic - Send For Final Review Settings.

1. Go back to the Product Configurations window from Advanced Find and click Generic - Send For Final Review.

2. Click the Flow URL field and paste the HTTP POST URL from Cloud flows here.
   To retrieve the Flow URL perform the following steps:

   1. Go back to Default Solution, click Cloud flows, search for, and click Generic - Send For Final Review.
      

   2. Click Edit.
      

   3. Expand When a HTTP request is received and click the Copy Url icon against HTTP POST URL.
      

   4. Click Save. 

Parent and Child Contract Field Copy Configuration

The Parents and Child Contract Field Copy feature automates data synchronization between parent and child contracts. It ensures that specific fields in the child contract are automatically populated or updated based on the corresponding values in the parent contract. This helps eliminate manual data entry and ensures consistency across related contract records.

Configurable Modes

Enabling or Disabling Parent and Child Contract Field Copy

To enable or disable the Parent and Child field copy:

1. Go to the Product Configurations window from Advanced Find and click Parent_Contract_To_Child_Contract_Field_Copy.
   The Parent_Contract_To_Child_Contract_Field_Copy page appears. 

2. To enable the feature, in the Value field, set the "AllowCopy" value to "true". When you set this to true, the system considers both OneTimeCopy and AlwaysCopy configurations.

3. To disable the feature, in the Value field, set the "AllowCopy" value to "false". When you set this to false, the system ignores both OneTimeCopy and AlwaysCopy configurations.

Configuring OneTimeCopy Fields

Use this configuration to define which parent contract fields are copied to the child contract upon creation. The OneTimeCopy option copies the fields only once, when the child contract is initially created.

1. Go to the Product Configurations window from Advanced Find and click Parent_Contract_To_Child_Contract_Field_Copy.
   The Parent_Contract_To_Child_Contract_Field_Copy page appears.

2. In the JSON Value field, under the “OneTimeCopy” value, enter the logical names of the fields you want to copy. 

   NOTE

   Make sure you enter each logical name within double quotes and separate them with commas. Also, when you remove a logical name, also remove the corresponding double quotes and comma.

3. Click Save.
   When a child contract is created, the Competition type field is automatically copied from the parent contract.
   When you create and save a parent contract with a value specified in the Competition Type field.
   When you create a child contract, the value in the Competition Type field is automatically copied from the parent contract. 

Configuring AlwaysCopy Fields

Use this configuration to synchronize selected fields between parent and child contracts. When the parent contract is updated, the changes are automatically reflected in the corresponding fields of the child contract.

1. Go to the Product Configurations window from Advanced Find and click Parent_Contract_To_Child_Contract_Field_Copy.
   The Parent_Contract_To_Child_Contract_Field_Copy page appears.

2. In the JSON Value field, under the “AlwaysCopy” value, enter the logical names of the fields you want to sync continuously. 

   NOTE

   Make sure you enter each logical name within double quotes and separate them with commas. Also, when you remove a logical name, also remove the corresponding double quotes and comma.

3. Click Save.
   Fields listed here update automatically in the child contract when you change them in the parent contract.
   When you update any of the specified field values in the parent contract. The system automatically updates the changes to the child contract. 

Configure Audit History Settings

These steps are performed to enable Audit History for your environment, its entities, and related fields.

1. Go back to Advanced Settings.

2. Click Administration and then click Auditing. 

3. Select the Start Auditing checkbox and click OK.
   Audit History is enabled for your environment.

4. Go back to Default Solution.

5. Expand Tables.
   

6. Click Contract and then click Properties.
   

7. Expand Advanced options.
   

8. Select the Audit changes to its data checkbox and click Save.
   Audit History is enabled for the Contract entity.

9. Expand Contract, click Columns, and then click Status. 

10. Expand Advanced options, select the Enable auditing checkbox, and click Save. Audit History is enabled for the Status field of the Contract entity.

11. To enable or disable Contract Audit History records, click the Funnel icon and select Product Configurations.

12. In the search bar, type and open Is_Contract_Audit_History_Enabled. 

13. On the Product Configuration page, set the Value field to Yes or No.  

    NOTE

    When the Value is set to Yes, Contract Audit History captures the audit data.
    When the Value is set to No, Contract Audit History remains empty while standard Dynamics audit logging continues.

14. Click Save & Close.

Mod Number Product Configuration

When a contract record is created, the initial Mod’s Mod Number field is set to Mod 0 by default. However, administrators can customize this value based on organizational preferences or naming conventions. For example, you may use alternatives such as Base Mod or Base Award.

To customize the default Mod Number field value:

1. Go to the Product Configurations window from Advanced Find and click ModNumberConfig.
   The ModNumberConfig product configuration page appears. 

2. Updated the Value field as required, then click Save. 

Agreement Field Visibility Product Configuration

Field visibility on the Agreement layout changes based on the selected Agreement Type. Specific fields are shown or hidden to ensure that you are able to view only the relevant information for each agreement type. However, administrators can customize this value based on organizational preferences.

To customize the field visibility based on Agreement Type:

1. Go to the Product Configurations window from Advanced Find, and click Agreement_Field_Visibility.
   The Agreement_Field_Visibility product configuration page appears. 

2. Modify the JSON Value field to show or hide the necessary fields, then click Save.

Agreement Archive Days Product Configuration

Agreements are automatically archived a set number of days after their end date. This timeframe (X days after the end date) is configurable by the administrators based on organizational preferences.

To configure the number of days:

1. Go to the Product Configurations window from Advanced Find and click Agreement Archive Days.
   The Agreement Archive Days product configuration page appears. 

2. Set the required number of days in the JSON Value field for archiving, then click Save.

Auto Generate Contract Brief Product Configuration

The Contract Brief auto-generation feature is disabled by default for out-of-the-box contracts users to avoid unintended storage issues. It can only be enabled and configured by administrators who explicitly choose to use it.

To enable auto generation of contract briefs:

1. Go to the Product Configurations window from Advanced Find, and click Generate Contract Brief.
   The Generate Contract Brief product configuration page appears. 

2. Set the Value field to true.

3. Set the required configuration in the JSON Value field:

   1. Customize which types of contract changes trigger auto-generation by setting the Revision Type to:

      • Internal Revision

      • Modification

      Note: If the Revision Type is left blank, the system will auto-generate Contract brief for both Internal Revision and Modification.

      NOTE

      If the Revision Type is left blank, the system will auto-generate Contract brief for both Internal Revision and Modification.

   2. Specify the BPF stage at which the contract brief should be auto-generated. If blank, the contract brief is generated when a contract is locked.

   3. Set Send Email to true to enable email notifications with the auto-generated contract brief attached. The email will be sent to the Contract Administrator.

   4. Enter the email IDs to be copied in the notification sent to the Contract Administrator when a contract brief is auto generated.

4. Click Save.