Exchange This topic is related to the Avoka Exchange. | Platform Developer | v5.0 & Higher This feature is related to v5.0 and higher.
During the Avoka Exchange Publishing Process you will be required to get your package certified by Avoka before it can be made active on the Avoka Exchange. When you submit your package for certification it will be added to the work queue for the Avoka Exchange team and scheduled for review. This review may take up to 6 weeks and may require one or more scheduled conference calls between the certification team and your project team to discuss aspects of your solution.
The Avoka Exchange team will review your package to ensure that it meets certain standards and minimum requirements in terms of how it is designed and built. We consider many aspects of the solution you've produced, including those listed under Certification Checklist below. We encourage you to become very familiar with this checklist and ensure that you are considering these items from the outset of your project so that delays are minimized when you wish to publish your solution on the Avoka Exchange. If anything is uncertain it is better to seek clarity before submitting for certification than it is to submit a non-compliant solution and receive a certification failure.
When you submit your package for certification it will be added to the work queue for the Avoka Exchange team and scheduled for review. This review may take up to 6 weeks and may require one or more scheduled conference calls between the certification team and your project team to discuss aspects of your solution.
Before submitting your package for certification, ensure you have reviewed the following checklist:
At the completion of the certification review you will receive a report detailing the outcome of the review and feedback relating to the areas highlighted by the review team.
The report will detail the overall outcome of the review (CERTIFIED or UNCERTIFIED) and may contain a number of feedback items classified as either:
Comment - A benign note made by the certification team relating to your solution. Comments to not impact the outcome of the review;
Recommendation - A suggested (but not required) modification to the solution that should be considered by your project team; or
Requirement - A mandatory requirement that must be satisfied by your solution before it is certified. The presence of any such items will result in an UNCERTIFIED outcome.
Any solution that does not get certified on the first submission may be resubmitted once the feedback items have been addressed.