Ex15 - addPrefix
This example demonstrates the use of the addPrefix value in Fulfillment Provisioning. This configurable parameter is set in Fulfillment Provisioning Catalog configuration on the Domain and TechProduct object. It is used to decide whether a product name must be added to a merged dataset or not.
At Domain level, addPrefix can have the following values : - "0" (Do not add Prefix) - "1" (Add Prefix) DEFAULT At TechProduct level, addPrefix can have the following values : - "0" (Do not add Prefix) - "1" (Add Prefix) - "2" (Use AddPrefix set at domain level) DEFAULT manualorder0a.xml uses TP (addPrefix=0) and Domain (addPrefix=0) manualorder1a.xml uses TP (addPrefix=1) and Domain (addPrefix=0) manualorder2a.xml uses TP (addPrefix=2) and Domain (addPrefix=0) manualorder0b.xml uses TP (addPrefix=0) and Domain (addPrefix=1) manualorder1b.xml uses TP (addPrefix=1) and Domain (addPrefix=1) manualorder2b.xml uses TP (addPrefix=2) and Domain (addPrefix=1)
This sample shows that only manualorder1a.xml, manualorder1b.xml and manualorder2b.xml have a prefix in merged datasets.
The files from ex00 are first copied to the $NODE/conf directory and then the ex15 files are copied and may overwrite some files from the following directory:
kpsasample/ex15/generic/conf
Copyright © Cloud Software Group, Inc. All rights reserved.