Documentation Index

Fetch the complete documentation index at: https://docs.zilliant.com/llms.txt

Use this file to discover all available pages before exploring further.

General property and ontology files

Prev Next

Zilliant CPQ uses specific files to store and maintain application system properties and support ontology-based customization of the application.

Access properties and ontology files

  1. From the application left navigation area, select Administration.
  2. From the top navigation bar, select Content Management .
  3. Select conf.
Important

The conf folder is required by the system. Do not delete this folder.

  1. Download the properties file you want to configure.
  2. Use a text editor to make and save changes.
  3. Upload the file.

The conf folder contains the following file types:

  • .properties—General property files for Zilliant CPQ. For example, application.properties.
  • .n3—Mapping files to find the .owl files.
  • .owl—Ontology files located in /conf/ontology folder.
Note

For more information, consult with your Zilliant representative or your implementation team.

Files in the conf folder

  • application.properties—Main properties file. It contains the properties for starting up a Zilliant CPQ tenant.
  • email-content.properties—Provides keys to customize the content of notification emails, such as approval and routing emails.
  • location-mapping.n3 and location-mapping-to-empty.n3—Use to find the exact path to the ontology .owl files.
    • location-mapping.n3—A key mapper to map file’s unique identification (URI) to its location.
    • location-mapping-to-empty.n3—Use when starting a tenant application.
  • schema.owl—Entities definition and their relationship.
    • Contains Classes (Business Types, BT), Data Attributes (Business Data Attribute, BDA) and Relation Attributes (Business Relation Attributes, BRA) definitions.
    • Contains meta attributes (Business Meta Attributes, BMA) that are used together with BDA and BRA.
      Additional ontology concepts can be defined in application-schema-ext.owl to further customize the product based on customer needs. (Examples: legacy BDAs, SPARQLs, custom data points.)