Although the Autotask user interface supports rich text formatting such as bold, italic, underline, and inline images, the Autotask API supports no rich text. All Autotask API calls use plaintext. Here are some key points to understand regarding text formatting and the Autotask API:
- Plaintext Only: The Autotask API does not support any form of rich text formatting. This includes common text styles like bold, italic, and underline, as well as inline images.
- Formatted Text Stripping: If an existing entity in Autotask contains rich text, all formatting will be stripped if the object is modified using the API. This means any bold, italic, underlined text, or images will revert to plain text.
- Implications for MSPintegrations: Since MSPintegrations communicates with Autotask via the API, all workflows and data managed through MSPintegrations are also limited to plaintext. This means that any text formatting applied in Autotask's user interface will be lost if the entity is updated through MSPintegrations.
Practical Considerations
Given these limitations, here are a few practical considerations for managing text in Autotask via MSPintegrations:
- Consistent Text Formatting: Plan for all text interactions to be in plaintext. This ensures that there are no surprises when formatting is stripped away.
- Data Integrity: Be aware that modifying any entity with rich text in Autotask using the API will result in the loss of formatting. Make sure this is communicated to all users who might be affected by these changes.
- Workflow Adjustments: Adjust any workflows or processes that rely on text formatting. Since MSPintegrations workflows are limited to plaintext, consider how this affects your documentation, communication, and data storage practices.
Understanding these constraints helps ensure that your use of the Autotask API and MSPintegrations remains effective and predictable, avoiding issues related to the loss of text formatting.