Application publishing requirements

Basic requirements to the published applications

1. Product summary – a brief and user-friendly description of your application. The summary should cover the product’s main functionality and the tasks that the product solves. Cannot exceed 115 characters with spaces.

2. Detailed product description – full description of your product capabilities and advantages.

3. Screenshots – at least 1 screenshot that illustrates the product’s functions. The minimum resolution is 1024px in width.

4. Compatibility – Creatio products and versions, that your product is compatible with.

5. Price – specification of the pricing model for your product.

6. Packages – packages with implemented functions that are specified in the product description An application can be a single Creatio package (*.GZ file) or an archive (*.ZIP file) with several packages.

7. Application logo – a corporate background image in PNG, GIF, JPG or JPEG format, 262x216 px. It is not recommended to use white color for the company logo. Dark tones are preferred. Lower half of the image must contain developer’s logo in white color.

8. Developer logo – a PNG, GIF, JPG or JPEG image, 200px in width, preferably with white background.

Marketplace application requirements:

1. Operability – the product must work exactly as claimed in the description.

2. Deployment – the application must be loaded in the Developer worspace on the Marketplace, in the [Installed applications] section. An application can be a Creatio package (*.GZ file) or an archive (*.ZIP file) with several packages. Before uploading your application, make sure that:

• A single file is uploaded.
• The uploaded file (package or ZIP) contains all functions required for proper operation of your application on supported Creatio configurations. I.e., additional setup of “base” or prerequisite packages is not required.
• Creatio package names remain unchanged and are the same as they were when packages were downloaded from the production environment.
• If a ZIP archive is downloaded, it cannot contain any folders. All *.GZ filed in the ZIP archive must be located in the archive’s root catalog.

3. Compatibility – the product must be compatible with Creatio products and versions specified as compatible during registration. Complete the following sequence for all applications:

• Deploy a free 14-day trial Creatio application (available here: https://www.creatio.com/trial/creatio).
• Install the application from a zip archive. The setup procedure for Marketplace applications is covered in the “Installing Marketplace applications from a zip archive” article.
• After installing the application, log in to your Creatio trial. If errors were encountered during the setup, or you are unable to log in to Creatio after installing the application, it will not pass verification and cannot be published on Creatio marketplaece.

4. Licensing – unless distributed for free, Marketplace applications must have one of the available licensing models (see “Marketplace application licensing”).

5. Performance – the product must not cause a performance decrease of the base Creatio product it was designed for.

6. Description – product description must not contain lexical, syntactic and semantic errors.

7. Data confidentiality – the Marketplace application must not obtain access to data to and transfer data illegally from the Creatio application where it is installed. Any data transfer that occurs after installation (in case of integration with third-party solutions) must be explicitly mentioned in the description and occur only after user authorization.

8. Support – the developer undertakes to provide technical support to the users within the implemented functionality by email, phone or any other communication channel. Support conditions must be explicitly stated in the corresponding section of the product properties page.

9. Updates – when releasing Marketplace application updates, the developer shall include all bug fixes and modifications in the description.