TaroWorks API 1.0 Features and Limitations

Pros

Ability to: 

• Get all Forms, questions & options, Skip Conditions, Form Mappings & Field Mappings and Object Relationship Mapping records from Salesforce.
• Get Forms, questions, Skip Conditions, Form Mappings & Field Mappings, Form Mappings & Field Mappings from Salesforce by sending the Salesforce ID of the Forms.
• Add/upload a new Form, add questions, Skip Condition, Form Mappings & Field Mappings and Object Relationship Mapping in Salesforce in Draft Status.
• Update an existing Form Version, Skip Condition data Form Mappings & Field Mappings and Object Relationship Mapping in a Draft or Updating status.
• Delete a form in draft or updating status
• Delete questions, Skip Conditions, Form & Field Mappings and Object Relationship Mappings available in Salesforce.

Cons

1. Cannot delete a Form referenced by a task.
2. Cannot delete a Form in Published status.
3. You cannot make any changes to a Form in published state - Editing a published form through the API will not be possible. Users will therefore have to login to Salesforce, navigate to the published form and click on edit in order to make changes to any Form. The external system user can then navigate back to the API and run a GET request for the specific Form to get latest Form version information, merge the changes and then proceed to send the upsert request successfully since the new Form version will be in updating status.
4. Cannot edit a Form with a new version available in Salesforce - External system users need to refetch the data by GET method so that they can get the latest version/change log number and merge their desired changes into it. After merging the changes users can then make the upsert request and proceed to send the upsert request successfully
5. Maximum of 200 Forms can be inserted/ updated in a single PUT request while a maximum of 500 Forms can be fetched through a single GET request.
6. Cannot edit questions details for a Form with a new Version available in Salesforce - External system users need to refetch the data by GET method so that they can get the latest version/change log number and merge their desired changes into it. After merging the changes users can then make the upsert request.
7. Maximum of 45 questions can be inserted/ updated in a single PUT request while a maximum of 150 questions can be fetched through a single GET request.
8. Cannot edit Skip Condition data for a Form with a new version available in Salesforce - External system users need to refetch the data by GET method so that they can get the latest version/change log number and merge their desired changes into it. After merging the changes users can then make the upsert request.
9. Maximum of 400 skip conditions can be inserted/updated in a single PUT request while a maximum of 500 skip conditions can be fetched through a single GET request.
10. Cannot edit Form Mappings and Field Mappings for a Form with a new Version available in salesforce - External system users need to refetch the data by GET method so that they can get the latest version/change log number and merge their desired changes into it. After merging the changes users can then make the upsert request.
11. Maximum of 130 Form mappings can be inserted/updated in a single PUT request while a maximum of 240 Form mappings can be fetched through a single GET request.
12. Cannot update Object Relationship Mapping to a Form in a Published status.
13. Cannot edit Object Relationship Mapping for a Form with a new version available in SF - External system users need to refetch the data by GET method so that they can get the latest version/change log number and merge their desired changes into it. After merging the changes users can then make the upsert request.
14. Maximum of 300 Object Relationship Mappings can be inserted/updated in a single PUT request while a maximum of 500 Object Relationship Mappings can be fetched through a single GET request.