Skip to content

Latest commit

 

History

History
140 lines (136 loc) · 16.3 KB

minimum-requirements.md

File metadata and controls

140 lines (136 loc) · 16.3 KB

Minimum requirements to pass certification

  1. The customer or partner signed the contract. See the process for building an integration

  2. The integration doesn't violate the Acrolinx license model. (Demo / Questions)

  3. Did you hard-code the correct signature? (Demo / Source)

  4. Version information is available to help Acrolinx Support. (Demo / Source)

    • How to set the version:
  5. Did you use the correct Acrolinx branding? (Demo)

  6. The integration seems to be usable. (Demo / Questions)

  7. The integration uses the best checking features to satisfy the use case. (Demo / Questions)

  8. Did you use the correct authentication method? (Demo / Source)

    • How can the customer set or change the sign-in option?
  9. You set the correct check type. (Demo / Source / Questions)

  10. The Acrolinx URL:

    • Isn't hardcoded
    • Doesn't default to https://partner-dev.acrolinx.sh/.

    Ideally, an admin can configure the Acrolinx URL for all users. (Demo / Source / Questions)

  11. You set the correct format. Ideally, use the auto setting. Acrolinx usually checks everything that is displayed in the UI. Sometimes you have to include additional custom fields. (Demo / Source)

  12. You provided a recognizable reference. (Demo / Source / Questions)

  13. The content is well structured and includes all necessary content. Acrolinx usually checks everything that is displayed in the UI. Sometimes you have to include additional custom fields. (Demo / Source)

  14. No obvious security issues are present. (Demo / Questions)

  15. The integration can connect to an Acrolinx instance such as https://partner-dev.acrolinx.sh/. (Demo / Questions)

  16. Did you implement a good scheduling mechanism? (Questions)

See Also