When developing custom catalogs you can now limit the use of the catalog to certain Experior “keys” by including a Build.Config file when you build the catalog.
The key numbers listed in the file is then the same users that are allowed to load the catalog when Experior is started.
It is optional, meaning that if you don’t need a Build.config file, then the catalog is complied without this information and then everybody with an Experior license can load the catalog.
This is the code that should be used if a Build.Config needs to be included.
The last key number in the list below, “02**”, means that all license keys starting with “02” are able to load the catalog.
<br /><!--?xml version=”1.0″ >;<br ?--><br /><br />0103<br />0104<br />02**<br /><br /><br />
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |