-
The customer or partner signed the contract. See the process for building an integration
-
The integration doesn't violate the Acrolinx license model. (Demo / Questions)
-
Did you hard-code the correct signature? (Demo / Source)
-
Version information is available to help Acrolinx Support. (Demo / Source)
-
Did you use the correct Acrolinx branding? (Demo)
-
The integration seems to be usable. (Demo / Questions)
-
The integration uses the best checking features to satisfy the use case. (Demo / Questions)
-
Did you use the correct authentication method? (Demo / Source)
- How can the customer set or change the sign-in option?
-
You set the correct check type. (Demo / Source / Questions)
-
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)
-
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) -
You provided a recognizable reference. (Demo / Source / Questions)
-
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)
-
No obvious security issues are present. (Demo / Questions)
-
The integration can connect to an Acrolinx instance such as
https://partner-dev.acrolinx.sh/
. (Demo / Questions) -
Did you implement a good scheduling mechanism? (Questions)