Application registration in the Developer console
Glossary Item Box
New applications can be registered in the Developer Console on any development stage. Go to the [Applications] section and click [Add application]. After the registration is complete, your application will be added to the list in the [Applications] section.
Fig. 1. List of applications in the Developer console
The application edit page displays a header with the name of the application and its status. Status – current stage of the application life cycle. An application can have one of the following statuses:
- In development – initial status of any application. It means that the product has not been released yet and is not available to the marketplace users.
- Verification – the product has been submitted for publishing and is currently being reviewed by bpm’online marketplace support. One of the stages in the verification process involves checking the product for compatibility. All compatibilities specified for the product by its developer must be fully implemented and tested.
- Clarification required – the product has been reviewed by the bpm’online marketplace support. Several changes must be made to the product based on the review results to match the general requirements to marketplace applications.
- Published – the product has been verified and is now available in the bpm’online marketplace showcase.
 |
NOTE The application status is displayed after a new product has been registered. The “Clarification required” and “Published” statuses are set by the bpm’online marketplace support. |
Application edit page contains several tabs with general properties of the application. Any changes made to the application properties page are available only for the developer and are not visible to the bpm’online marketplace users until published.
Introduction
The [General information] tab (Fig. 2) contains fields with general properties of your bpm’online marketplace application.
Fig. 2. The [General information] tab
The tab contains the following properties of your application:
Product name – official name of the product on the marketplace. For more information on properly naming products for publishing them on the marketplace, please see regulations on releasing partner solutions. This is a required property.
Product category – type of the product. There are two types of products – vertical solution and application.
Vertical solution - a custom configuration, developed on the bpm'online platform. Solutions fulfill the need of a specific industry and have separate business value. A vertical solution consists of the base product used as a development platform and an Add-on developed by the partner to form the unique value of the vertical solution. More information about vertical solutions can be found in the regulations on releasing partner solutions.
|
ATTENTION Vertical solutions can be developed and published exclusively by organizations that have the Bpm’online Partner status. |
Application– a solution that extends functions of bpm’online base products and creates additional business value for the customer. Applications for bpm'online can be developed and published by any organization or individual, including organizations that do not have bpm’online Partner status.
The applications fall into two subcategories:
- Connector – an application that connects bpm'online with external services and third-party applications.
- Add-on – an application that supplements bpm'online base product with new modules, configuration settings and system elements.
|
NOTE To be able to use applications, users must have at least one bpm’online license. |
Compatibility – a group of fields with checkboxes for all bpm’online products. Select a checkbox to indicate that the corresponding product is supported by your application. In the [Version compatibility] field, specify the lowest supported bpm’online version. Use the [Compatibility notes] field to specify any additional comments on the product compatibility, such as supported vertical solutions, etc.
Fig. 3. Product compatibility options
Deployment option – deployment options that are available for the product (Fig. 4):
- Cloud – the product can be deployed on bpm’online servers.
- On-site – the product can be deployed on customer’s servers.
Fig. 4. Additional properties
Localization – the list of languages that are available in the product. You can select multiple languages.
Demo link – a link to deployed bpm’online application with installed product.
Details
The [Details] tab contains fields for description of the bpm'online marketplace application (Fig. 5). Also, tab contains fields to add and modify screenshots (Fig. 6).
Fig. 5. Fields for description
Fig. 6. Fields for screenshots
The tab contains the following properties of your application:
Product summary – brief description of the product: Its primary function and the tasks it solves. Cannot exceed 115 characters with spaces.
Product description – extended description of the product.
[Additional resources] – a group of fields that can be used to specify links on external resources or upload files with product description.
Support conditions – terms and conditions of technical support that the developer obliges to provide for their product. The developer obliges to provide technical support within the boundaries of implemented functions by email, phone or any other communication channel.
Logo – product logo displayed in the marketplace showcase. Corporate background image in PNG, GIF, JPG or JPEG format, 262x216 px. Preferably dark. Lower half of the image must contain developer’s logo in white color.
Screenshots – screenshots that illustrate the product and are available on the marketplace product page. PNG, GIF, JPG or JPEG image, The minimum resolution is 1024px in width. and no larger than 20 MB.
Video link – a link to the product online video overview.
Packages and updates
Information about all versions of the packages and updates is displayed on the [Packages and updates] tab (Fig. 7). A version and update status are displayed for each record.
|
ATTENTION A new version of application cannot be added while previous version is not published. |
Fig. 7. [Packages and updates] tab
When adding a new package or modifying properties of the existing one, the package (or update) properties edit page will be displayed (Fig. 8).
Fig. 8. Package properties edit page.
Main fields of the package properties edit page:
Version – version of the application, update or a package.
What’s New – a brief description of the update.
Packages – a list of uploaded package. Packages can be moved through the list or deleted.
Add files – package upload area. Allowed file types: gz, zip, rar. Files must be less than 200 MB.
Price
The [Price] tab (Fig. 9) contains fields with different price options of your bpm’online marketplace application.
Fig. 9. The [Price] tab
The tab contains the following properties of your application:
[Base currency] – defines a base currency used in marketplace (euro). The currency that will be displayed in the marketplace showcase depends on the site domain from which the client has logged in (for example, for bpmonline.com it will be dollar). Conversion to national currencies takes place at the bpm’online commercial rate.
Deployment type – specify the type of product deployment, for which the current price is valid (you can have different prices for on-site and cloud applications). For example: “bpm'online sales enterprise cloud”.
Price – product price in US dollars. If the [Price] field is not filled in, the product can be downloaded free.
Pricing model – price format for the current product deployment type. The following price models are available:
- “/ year” – customers will need to make yearly payments to be able to use the product, regardless of the number of users.
- “one-time” – customers can use the product for unlimited term after making a single payment, regardless of the number of users.
- “/ user” – customers will need to pay once for every user who will be working with the product. The product can be used for unlimited term.
- “/ user/year” – customers will need to pay once for every user who will be working with the product. Customer pays for the subscription for one year and in a year must renew the subscription.
- “on demand” – the customers will need to make an inquiry with the developer to get their quotation.
Comment – developer’s comment on the product pricing, that is visible to the marketplace users.
