Add-on Konfiguration (Provider Backend)


The dashboard displays the important sales data for each company visually. These are:

  • Cumulative sales across all add-ons
  • Add-ons online
  • Add-ons offline
  • Top 5 Add-ons/number of pieces
  • Top 5 Add-ons/Sales
  • Top 5 Purchasing countries
  • Top 5 Buyers



In the Add-on list, the user gets an overview of all the add-ons of the companies where he has the accessor editor right. The add-ons are sorted by companies, if a user supports several companies. It is possible to filter inactive add-ons from the list. A new add-on can be created using the “Create new Add-on” button. If he is a user accessor for several companies, he can decide for which company this is created when creating an add-on. A later move of an add-on is currently not supported! The prerequisite for creating an add-on is a Shortsign at the provider.



Under this heading, the user can specify the important data of an add-on:

  • Name
  • Technical name
    • The technical name is used for the folder structure of the add-on, which makes it independent of the name and folder structure (subproject).
    • The technical name consists of the provider abbreviation (Shortsign) and an additional one.
    • The addition is unique to each provider and may consist only of alphanumeric characters and “_”. This is for reasons of compatibility with WINCC OA.
  • Category (selection from a list)
  • Software (WINCC OA)
  • Description
  • Active (as long as this switch is not active, we do not see the add-on in the store)
    • The following preconditions are required to activate the add-on
      • At least 1 version that has run positively through the quality gate and has the status “released”
      • At least 1 price information
      • At least 1 image with the status “is visible”



In the version area, the user can manage the various stands of his add-on. The area is divided into two parts. On the left, the user sees the versions and right, depending on the selection, the details of a version. The version contains the following detailed information:

  • Name of the version
  • Description of the version
  • ZIP file version
    • The name of the zip file is not relevant at this point
    • The contents of the zip file must be present as described in the “Add-on Creation guide” and is also checked by the QG
  • Type (Details in the chapter add-on versioning)
    • Major
    • Minor
    • Patch
  • WINCC OA version
  • Operating system
  • Release date
    • As soon as possible
      • The version is released as soon as the quality gate has been successfully passed and the quality score is greater than 0.
    • Defined date
      • Here you can define a date on which the version will be released
      • Requirement that the version be released is a positive quality gate
    • Manual
      • Here you can, after a positive quality gate pass, unlock the version be

A table with the quality gate status is displayed under the version information. Details of the quality gate can be read in the Chapter QUALIYT gate.



Here the user can define the price models for the add-on. These are:

  • One time payment
  • Subscription
  • Pay Per Use
  • For each price model, the user can store the following information:

  • Price

    • Price for a license taking into account the pricing model
  • Upgrade/year or period
    • Price for the annual upgrade
  • Upgrade once
    • Price for a one-time upgrade
    • This is not displayed in the add-on detail, but we later dealt with the order

Subscription currently you can only enter “annual” as a period. This selection will be extended later. Pay Per use here you can either from the Std. Select units or enter your own unit as the license entry “UnitCount” is counted down.



Here you can add one or more pictures which will be displayed later in the add-on detail. The top image is also displayed as a “cover image” in the store. You can also switch individual images to in-/visible.



This area is designed to extend an add-on to include services and features. The general point here is that the provider can sell additional licenses in addition to the license. In doing so, SloopTools distinguishes between services and features.


Services are meant to be service or time-oriented. There is nothing special noted in the license, however, these data are important clearing items. Here, SloopTools differs from standard services (e.g. maintenance) or support.


The difference to the services lies in the fact that here a feature bit is placed in the license and the provider later in the software can check this and thus unlock with existing bit functionality.


results matching ""

    No results matching ""