All type rules have the options below for controlling in which types of sites that they should be effective, i.e. where they should run:
Setting name |
Description |
|---|---|
Effective on administration site |
If checked the rule will run on the administration site, i.e. on the site that is used for testing purposes. |
Effective on production site |
If checked the rule will run on the production site, i.e. on the site that is used for creating quotes and orders. |
Effectivity of rules is typically used when modeling new options that have not yet been released for a product and can for example be used in the scenarios below.
Hide or disable new values of a lookup parameter in the production site
This is done by adding a disallowed combination rule with only one lookup parameter in the rule and with the new values selected as disallowed. The rule shall only be effective in the production site.
Hide new parameters in the production site
New parameters that should not yet be visible when making quotes and orders can be hidden using a single sub parameter rule that has no triggering parameters. The rule shall only be effective in the administration site.
If the introduction of new parameters includes the need of modeling when the new parameters should be hidden or visible, it's a better strategy to put the new parameters on a tab that is only visible in the administration site by using the expression function InAdminSite() as Inclusion expression for the tab.
Remarks
It's good practice to mark these kind of rules using a particular rule category like "Temporary" for keeping track of rules that shall be removed once the changes are released.
