Merge branch 'microsoft:dev' into dev

Author: troystaylor

.github/CODEOWNERS

@@ -54,4 +54,6 @@
 /certified-connectors/emfluencemp/ @ryandeba
 /certified-connectors/envoy/ @aasimniz95
 /certified-connectors/exghts/ @exghts
-/certified-connectors/gofileroom/ @calvinleong
+/certified-connectors/gofileroom/ @calvinleong
+/certified-connectors/DocuSign/ @sriharip-docusign
+/certified-connectors/DocuSignDemo/ @sriharip-docusign

.github/pull_request_template.md

@@ -4,8 +4,7 @@
 
 If this is your first time submitting to GitHub and you need some help, please sign up for this [session](https://forms.office.com/pages/responsepage.aspx?id=KtIy2vgLW0SOgZbwvQuRaXDXyCl9DkBHq4A2OG7uLpdUMTFJWFFGVUxBNUFZQjZWRUdaOE5BMFkwNS4u). 
 
-Please note that we are experiencing a significant delay due to a high volume of connector submissions. It may take 1-2 weeks for us to provide comments for your connector.
-
+- [ ] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation. 
 - [ ] I attest that the connector works and I verified by deploying and testing all the operations. 
 - [ ] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
 - [ ] I attest that I have added response schemas to my actions, unless the response schema is dynamic. 

certified-connectors/Actsoft/README.md

@@ -1,16 +1,17 @@
-# Actsoft Mobile Workforce Plus
-Mobile Workforce Plus allows you to create and capture digital form information, capture employee timekeeping information, and manage work orders with a dispatching system.
+# Actsoft TeamWherx
+TeamWherx allows you to create and capture digital form information, capture employee timekeeping information, and manage work orders with a dispatching system.
 
-This connector uses the [Mobile Workforce Plus APIs]( https://developer.wfmplatform.com/) to make it easy to interact with information captured using the application.  You can utilize various triggers or actions in the connector to easily extract data from Mobile Workforce Plus and integrate with other applications.
+This connector uses the [TeamWherx APIs]( https://developer.wfmplatform.com/) to make it easy to interact with information captured using the application.  You can utilize various triggers or actions in the connector to easily extract data from TeamWherx and integrate with other applications.
 
+# Publisher
+Actsoft, Inc
 # Prerequisites
 In order to use this connector, you will need the following:
 
-- An active Mobile Workforce Plus Account
-- Mobile Workforce Plus API Key
+- An active TeamWherx Account
+- TeamWherx API Key
 - Microsoft Power Apps or Power Automate plan
 
-
 # Supported Operations
 
 ## Triggers
@@ -70,23 +71,36 @@ In order to use this connector, you will need the following:
 - Activate a user
 - Deactivate a user
 - Update a user
+- Update a partial user
 - Get a single user
 - Get a list of users 
 
 ### Vehicles
 - Create a vehicle
 - Activate a vehicle
 - Update a vehicle
+- Update partial vehicle information
 - Deactivate a vehicle
 - Delete a vehicle
 - Get a single vehicle
 - Get a list of vehicles
 
 
 ## Obtaining Credentials
-Developer API portal credentials are managed in the Mobile Workforce Plus web application. Please contact the application administrator for access.
+Developer API portal credentials are managed in the TeamWherx web application. Please contact the application administrator for access.
+
+After credentials are created, the developer portal can be accessed at: [TeamWherx APIs](https://developer.wfmplatform.com/)
 
-After credentials are created, the developer portal can be accessed at: [Mobile Workforce Plus APIs](https://developer.wfmplatform.com/)
+## Known Issues and Limitations
+- Audio file binary uploads (POST) for all endpoints are limited to MP4 only.
+- Dates for all endpoints that require date-time information must be specified according to RFC3339 guidelines, as in the following example: 2021-09-22T02:36:56.52Z. It is not necessary to specify the exact seconds in the timestamp; 00 is acceptable.
 
+## Deployment Instructions
+- N/A
 
+## Throttling Limits
+| Name	| Calls	| Renewal Period |
+| ----- | ------ | ------- |
+API calls per connection | 100 | 15 seconds 
+Frequency of trigger polls | 1 | 48 seconds