Submission checklist

ISV client submission checklist

Before submitting your ISV application, review and include the following:

• Required URLs, including Terms of Service URL and Help URL.
• Your installation URL using the Genesys Cloud Clients SDK, including language and environment variables.
• Required metered operational details, including Terms of Service URL and Help URL.

ISV client demonstration checklist

The AppFoundry team reviews the following items for ISV approval during the approval meeting:

• Ensure application loading in the Genesys Cloud Apps menu.
• Ensure that SSO is functioning properly while setting up the application for Genesys Cloud users.
• Ensure that the ISV application URL has the environment and language variables.
• Ensure that the ISV application updates the static definition URL to the customer-specific URL.
• Remove visible Genesys or AppFoundry logos.
• Ensure that the breadcrumbs in the upper left side corner are updated.
• Ensure that the application checks the Genesys Cloud ISV application product.
• Ensure validation of the following monetization mechanisms:
  • Usage applications: Validate users with proper permission or license while accessing the ISV application.
  • Metered applications: Validate metered usage reporting.

ISV client post-submission checklist

The AppFoundry team provides the following items to the ISV application AppFoundry partners:

• Genesys parts.
• Genesys parts live in the Genesys Parts Catalog.
• API Key for the Genesys Cloud Usage APIs. For more information, see the premium AppFoundry partner usage.
• ISV application ID.
• Genesys Cloud product or permission and/or license.
• Pre or post-installation instructions for offering a free trial on AppFoundry.

Genesys Cloud embeddable framework submission checklist

The checklist for Genesys Cloud embeddable framework submission is as follows:

• Develop and test the application locally.
• Develop and test the application using a private deployment (optional).
• Demonstrate the solution and get it approved by the AppFoundry Team.
• Complete AppFoundry listing. 
• Submit Pre or post-installation instructions for offering a free trial on AppFoundry.

Application review process

After completing the checklist, submit your framework.js file to appfoundry@genesys.com. You can either include a link to the accessible source code repository or rename the extension to .txt and attach the file in the email.

Your application review fails due to the following:

• Outside libraries in the framework.js file.
• Direct API calls or credentials in the framework.js file.
• Unscoped (that is, “*”) Windows post messages.
• Submissions that are visually indistinguishable from existing Genesys-provided integrations, including SFDC, Zendesk, and Chrome or Firefox extensions.
• Manipulation of the PEF DOM.

Mejores prácticas

A few best practices to be followed are as follows:

• Keep the framework.js file as lightweight as possible. It is intended as a simple communication layer between the Embeddable Framework Client and your code running in the host application.
• Ensure that all business logic, including screen pop execution, call log writing, and business process automation, is contained in your code running in the host application.
• Ensure that all business logic is not placed in the framework.js file.

These best practices provide you with more control over the code deployment in the host application and keep up with API changes and new feature additions while remaining backward compatible with the deployed framework.js file.

Despliegue

Deployments are done at any time after the file is submitted for review. You must account for the deployment in your host application code, aided by keeping your framework file as lightweight as possible. 

After the application’s initial review, update the redirect URLs in your OAuth client. For more information about deployment, see Deployment.