Targets Occurrences of 'ctiva' in Project Found Occurrences (335 usages found) Unclassified (306 usages found) product-docs-local (306 usages found) modules/ROOT (1 usage found) nav.adoc (1 usage found) 138 **** xref:Administration/Security/Activation-security/Activation-keys.adoc[] modules/ROOT/attachments (2 usages found) changes-in-magnolia-6-ui.csv (2 usages found) 317 info.magnolia.ui.framework.action.ActivationActionDefinition,info.magnolia.ui.contentapp.action.JcrCommandActionDefinition (jcrCommandAction),,," 327 info.magnolia.ui.framework.action.DeactivationActionDefinition,info.magnolia.ui.framework.action.ActivationActionDefinition (-),"ActivationActionTest modules/ROOT/pages (1 usage found) Glossary.adoc (1 usage found) 13 == Activation modules/ROOT/pages/Administration (1 usage found) Monitoring.adoc (1 usage found) 214 To test the new configuration, activate some content and view the logged modules/ROOT/pages/Administration/Architecture (10 usages found) Configuration-management.adoc (3 usages found) 360 _default is ``${magnolia.home}/WEB-INF/config/default/magnolia-activation-keypair.properties``_ 362 Location of private and public activation keys used for xref:/Administration/Security/Publishing-security.adoc[publishing]. 513 Activate xref:Administration/Language/Language-configuration.adoc[UTF-8 Node-types.adoc (5 usages found) 181 |`mgnl:activatable` 182 |`mgnl:lastActivated (DATE)` 184 `mgnl:lastActivatedBy (STRING)` 186 `mgnl:activationStatus (STRING)` 188 `mgnl:lastActivatedVersion (STRING)` Publishing-overview.adoc (2 usages found) 10 is a refactored version of the former _activation_. The original Activation module has been broken into multiple submodules, see the xref:Modules 57 in `/server/activation`, see xref:/Administration/Security/Publishing-security.adoc[Publishing security] for more on this. modules/ROOT/pages/Administration/Importing-and-exporting-data (2 usages found) Importing-and-exporting-JCR-data-for-bootstrapping.adoc (2 usages found) 207 * `mgnl:activationStatus`, `mgnl:created`, `mgnl:createdBy`, 208 `mgnl:lastActivated`, `mgnl:lastActivatedBy`, `mgnl:lastModified`, modules/ROOT/pages/Administration/Instances (4 usages found) Content-staging.adoc (2 usages found) 28 . Copy the `magnolia-activation-keypair.properties` file from the author 31 xref:/Administration/Security/Publishing-security.adoc[activation keys]. This Receivers.adoc (2 usages found) 26 Before Magnolia 5.6, the system process was called _activation._ 45 * Publication log `/webapps/magnoliaAuthor/logs/magnolia-activation.log` modules/ROOT/pages/Administration/Language (1 usage found) Language-configuration.adoc (1 usage found) 260 # Activate UTF-8 support to pages magnolia.utf8.enabled=true modules/ROOT/pages/Administration/Security (22 usages found) Default-permissions.adoc (14 usages found) 123 |App |Activation 124 |`/modules/activation/apps/activation/permissions/roles` 204 |Action |Assets |Activate 205 |`/modules/dam-app/apps/assets/subApps/browser/actions/activate/availability/access/roles` 207 |Action |Pages |Activate 208 |`/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles` 229 |Action |Assets |Activate 230 |`/modules/dam-app/apps/assets/subApps/browser/actions/activate/availability/access/roles` 232 |Action |Pages |Activate 233 |`/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles` 271 |Action |Pages |Activate 272 |`/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles` 297 |Action |Pages |Activate 298 |`/modules/pages/apps/pages/subApps/browser/actions/activate/availability/access/roles` Default-roles-groups-and-users.adoc (1 usage found) 29 you should not activate that role. Publishing-security.adoc (4 usages found) 22 # Location of the file containing both the private and the public keys used to verify authenticity of activation requests 23 # This file is generated if not present magnolia.author.key.location=${magnolia.home}/WEB-INF/config/default/magnolia-activation-keypair.properties 37 . Paste the key to *Configuration >* `/server/activation/publicKey`. 39 case with the initial key. You cannot activate the `publicKey` node to the public instance as at this point because a mismatch exists between the Security-best-practices.adoc (1 usage found) 12 * Create a custom user with superuser role and deactivate the Users.adoc (2 usages found) 53 deactivate the superuser account. 74 you should not activate that role. modules/ROOT/pages/Administration/Security/Activation-security (20 usages found) Activation-keys.adoc (20 usages found) 1 = Activation keys 3 This page describes the function of activation keys in Magnolia, what 7 == Understanding activation keys and their functions 12 _Activation_ is used here as a technical term for xref:/Authoring/Publishing.adoc[publishing] content from 14 === `magnolia-activation-keypair.properties` 17 `magnolia-activation-keypair.properties` in the filesystem. The path to 26 `magnolia-activation-keypair.properties` file. 31 `/server/activation@publicKey`. 67 Manager module] uses the public activation key to `hash` plain text 106 `magnolia-activation-keypair.properties` file. In addition, the system 117 * Option I: Copy the `/server/activation@publicKey` property, stored in 120 * Option II: Delete the `/server/activation@publicKey` property in the 134 `/server/activation` node in the `config` workspace: 160 curl -X DELETE https://public1.example.com/.rest/properties/v1/config/server/activation/publicKey \ 165 curl -X DELETE http://localhost:8080/magnoliaPublic/.rest/properties/v1/config/server/activation/publicKey \ 174 `/server/activation` path. 177 `/.rest/properties/v1/config/server/activation` path. 196 ** `//.rest/properties/v1/config/server/activation` 197 ** `//.rest/nodes/v1/config/server/activation` 204 module] and if you had to regenerate the activation key pair, proceed modules/ROOT/pages/Administration/Troubleshooting (5 usages found) Instances-are-not-in-sync.adoc (1 usage found) 8 Activation refused due to request arriving too late or time not synced between author and public instance Publishing-errors.adoc (4 usages found) 35 an error `Handshake information for activation was incorrect` is 39 magnoliaPublic] Message: Handshake information for activation was incorrect. Someone attempted to impersonate author instance. Incoming request was from 127 40 magnoliaPublic] Message: Handshake information for activation was incorrect. Someone attempted to impersonate author instance. Incoming request was from 127 189 mgnlSystem, please verify that page was activated correctly to this public instance. modules/ROOT/pages/Apps (10 usages found) Developing-a-custom-content-editor-app.adoc (2 usages found) 147 class: info.magnolia.ui.framework.action.ActivationActionDefinition 148 command: activate Enabling-versioning-in-content-apps.adoc (8 usages found) 21 `activate/deactivate` link:#_command_chains[command chains] in the 22 `versions` catalog instead of the `activate/deactivate` commands in the 29 . Change the `activate` and `deactivate` action definitions. + 30 In the `/actions/activate` and `/deactivate` nodes add a `catalog` 32 version command configured in the `activation` module in 33 `modules/activation/commands/versioned/activate` and `/deactivate`. 56 . In the *Categories* app, create a few versions by activating and 57 deactivating an item and then execute the *Show versions* action to open modules/ROOT/pages/Apps/App-configuration (5 usages found) Action-bar-definition.adoc (3 usages found) 45 - name: activationActions 47 - name: activate 48 - name: deactivate Action-definition.adoc (2 usages found) 276 activate: 596 activate: modules/ROOT/pages/Apps/List-of-apps (2 usages found) Resource-Files-app.adoc (2 usages found) 37 ** Not activated 39 ** Activated modules/ROOT/pages/Authoring (4 usages found) Publishing.adoc (4 usages found) 22 because it can take a while to activate lots of content. 23 * *Unpublish*: Unpublishes (deactivates) the node from the public 34 (activation) to a future date and include approval steps. The editor who 56 load (many editors activating large amounts of content at the same modules/ROOT/pages/Connector-Packs/Commerce-Connector-Pack/E-commerce-REST-endpoints (1 usage found) Product-endpoint-API.adoc (1 usage found) 1269 features a large digital face and button-activated alarm and stopwatch. The soft-touch resin band promises no-pinch comfort, while the water-resistant modules/ROOT/pages/Developing (21 usages found) Commands.adoc (20 usages found) 51 commands with the same name. For example, the `activation` module has 53 in the *Configuration* app > `/modules/activation/commands`. 58 commands. You might want two `activate` commands – one for pages and 61 you would distinguish the two activate commands by calling one with 62 `workflow-activate` and the other with `default-activate`. 95 definition for the `activate` action in the Pages app. You can find it 97 `/modules/pages/apps/pages/subApps/browser/actions/activate`. See 107 activate a press release on a certain day, take a weekly backup of 114 For example, the `activate` command expects to receive a `repository` 126 * `active`: Set value to `true` to activate the job. 162 /modules/publishing-core/commands/default/activate 163 /modules/publishing-core/commands/default/deactivate 171 /modules/publishing-core/commands/versioned/activate 172 /modules/publishing-core/commands/versioned/deactivate 174 /modules/rest-services/rest-endpoints/commands/enabledCommands/activate 175 /modules/rest-services/rest-endpoints/commands/enabledCommands/activate/access 176 /modules/rest-services/rest-endpoints/commands/enabledCommands/activate/access/roles 216 command = cm.getCommand('activate') 233 . Paste the example activation commands from above into the *Source* 243 `sendMail` command when a page is activated. This way you can send an Integration-points.adoc (1 usage found) 25 any JCR workspace. You can also execute commands to activate, export and modules/ROOT/pages/Developing/API (2 usages found) JCR-API.adoc (2 usages found) 126 NodeTypes.Activatable.getActivationStatus(node); 127 NodeTypes.Activatable.update(node, "username", isActivated); modules/ROOT/pages/Developing/API/REST-API (20 usages found) Commands-endpoint-API.adoc (4 usages found) 83 Publish (activate) the page `/travel/hello`. 87 curl http://localhost:8080/magnoliaAuthor/.rest/commands/v2/website/activate \ 104 Publish (activate) the page `/travel/hello` on a future date. 108 curl http://localhost:8080/magnoliaAuthor/.rest/commands/v2/website/activate \ Nodes-endpoint-API.adoc (6 usages found) 121 "name": "mgnl:lastActivatedBy", 137 "name": "mgnl:lastActivated", 193 "name": "mgnl:activationStatus", 256 mgnl:lastActivatedBy 272 mgnl:lastActivated 328 mgnl:activationStatus SPA-template-annotations-endpoint.adoc (10 usages found) 44 label=\"Component with two columns\" activationStatus=\"0\"", 45 "/angular-minimal/about/header/0": "cms:component content=\"website:/angular-minimal/about/header/0\" label=\"Navigation\" activationStatus=\"0\"", 46 description=\"Adds headline, text and image.\" activationStatus=\"0\"", 48 false\" showNewComponentArea=\"false\" activationStatus=\"0\"", 49 "true\" showNewComponentArea=\"true\" activationStatus=\"0\"", 50 description=\"Adds headline, text and image.\" activationStatus=\"0\"", 51 "true\" showNewComponentArea=\"true\" activationStatus=\"0\"", 52 false\" showNewComponentArea=\"false\" activationStatus=\"0\"", 53 "true\" showNewComponentArea=\"true\" activationStatus=\"0\"", 54 "true\" showNewComponentArea=\"true\" activationStatus=\"0\"" modules/ROOT/pages/Developing/API/REST-API/Delivery-endpoint-API (1 usage found) Delivery-endpoint-API-v2.adoc (1 usage found) 940 You can specify the properties using a full property name, as seen on line 4 below, or using a wildcard character (line 5, to request for example `mgnl:lastActivatedBy`, `mgnl:createdBy` and so on): modules/ROOT/pages/Developing/Content-Types-tutorial (1 usage found) Part-II-Complex-content-types-and-security-set-up.adoc (1 usage found) 616 environment, you should create users with specific roles and deactivate modules/ROOT/pages/Features (4 usages found) Integration.adoc (1 usage found) 131 publications, flush the cache, synchronize content, activate workflows, Personalization.adoc (2 usages found) 386 itemTypes` property of the `personalizationActivation` command in the `personalization-core` module: 393 personalizationActivation: Workflow.adoc (1 usage found) 43 published to public instances immediately when activation is launched. Removing the Workflow module disables all workflows, not only the content approval modules/ROOT/pages/Features/Search (1 usage found) Jackrabbit-search.adoc (1 usage found) 36 from public instance indexes. Any content that has not been activated to modules/ROOT/pages/Getting-started-with-Magnolia/Demo (2 usages found) Travel-demo-for-editors.adoc (2 usages found) 39 * Click Main bar to activate the component bars. 53 * Click Main bar to activate the component bars. modules/ROOT/pages/Magnolia-Cloud/Managing-environments-using-the-Magnolia-cockpit (3 usages found) Monitoring-and-logging.adoc (3 usages found) 36 visualisation of certain preconfigured metrics. which are activated by 38 activate metrics for the integration and UAT environments. Some examples 139 Preconfigured logs are activated by default for your *live, UAT and modules/ROOT/pages/Modules (1 usage found) Module-definition-items.adoc (1 usage found) 121 * Changes can be published (activated) to other instances. modules/ROOT/pages/Modules/List-of-modules (21 usages found) Campaign-Publisher-module.adoc (3 usages found) 33 the state of readiness and activation status of each item, preview 259 `/modules/tours/apps/tours/subapps/browser/actionbar/sections/item/groups/activationActions`. 302 activation status indicator and *Preview* action are disabled. Content-Dependencies-module.adoc (1 usage found) 33 need to be activated together. Groovy-module.adoc (1 usage found) 171 |*[.kbd]#SHIFT#* + *[.kbd]#ENTER#* |Activate multi-line mode in the Observation-module.adoc (7 usages found) 132 be supplied to activate the feature. 160 be supplied to activate the feature. 182 * `activateAddedPages`: Uses `ActivationCommand` to automatically 183 activate new pages. 287 == Example: Activating assets automatically 296 is also required as a parameter by the `ActivationCommand`. 298 *Example*: Automatically activate new assets added in the Periscope-module.adoc (2 usages found) 33 search all content apps or extended by activating search in external 199 specified. Full-text search is activated within the workspace defined. Publishing-module.adoc (3 usages found) 117 * `publish` (`activate`) 118 * `unpublish` (`deactivate`) 149 catalog, the command tree contains also the `activate` and `deactivate` commands (not shown below), which extend the `publish` and `unpublish` commands Scheduler-module.adoc (3 usages found) 40 * Activate or deactivate a promotional web page on a specific date. 55 *Example*: `demo` job that activates the `/news` page hourly. 81 the `activate` command expects to receive a repository name and a Synchronization-module.adoc (1 usage found) 128 (extends `BaseActivationCommand`) registered in modules/ROOT/pages/Modules/List-of-modules/Cache-modules (1 usage found) Cache-core.adoc (1 usage found) 192 This configuration observes changes (activation, import, edit) in a modules/ROOT/pages/Modules/List-of-modules/Personalization-module/Creating-custom-traits-without-Java/Creating-a-custom-cookie-trait-without-Java (1 usage found) Configuring-a-custom-cookie-trait.adoc (1 usage found) 69 To activate the switchable field, in the dialog click *Pick trait > modules/ROOT/pages/Modules/List-of-modules/Solr-module (11 usages found) Indexing-and-crawling-a-website-with-Solr.adoc (11 usages found) 242 |`activationOnly` 246 activation. No scheduler job will be registered for this crawler. 251 |`delayAfterActivation` 255 activation is done. Default value is 5s. 314 List of JCR items. If any of this items is activated crawler will be 426 ==== Crawling triggered by publishing (activation) 428 From version 3.0, crawlers can be also connected with the publishing (activation) process 429 by adding `info.magnolia.module.indexer.crawler.commands.CrawlerIndexerActivationCommand` 430 into command chain with activation command. By default, this is done for 438 * catalog: default, command: personalizationActivation - configured under `/modules/personalization-integration/commands/default/personalizationActivation` 440 If you are using a custom publishing (activation) command and you wish to connect it modules/ROOT/pages/Modules/List-of-modules/Workflow-module (72 usages found) Enabling-workflow-in-content-apps-with-YAML.adoc (50 usages found) 19 override the action configuration for the activation actions. 29 activate: # publish 31 catalog: workflow # Calls workflow-activate command 32 command: activate # from the workflow module. 50 # end activate: ####################################################################### 52 activateRecursive: # publish recursive 54 catalog: workflow # Calls workflow-activate command 55 command: activate # from the workflow module. 60 formTypes: *types # Reference the types configuration from activate. 62 asynchronous: true # Bulk activations will be done asynchronously as to not block the interface. 74 # end activateRecursive: ############################################################## 76 deactivate: # unpublish 78 catalog: workflow # Calls workflow-deactivate command 79 command: deactivate # from the workflow module. 84 formTypes: *types # Reference the types configuration from activate. 89 # end deactivate: ##################################################################### 91 activateDeleted: # publish deletion 93 catalog: workflow # Calls workflow-activate command 94 command: activate # from the workflow module. 110 # end activateDeleted: ################################################################# 122 activation actions are placed in the actionbar. Some configuration has 123 been removed to bring focus to activation. 151 # Configure activation actions for deletedAsset section 152 activationActions: 154 - name: activateDeleted # publish deletion 155 - name: deactivate # unpublish 172 # Configure activation actions for deletedFolder section 173 activationActions: 175 - name: activateDeleted # publish deletion 176 - name: deactivate # unpublish 190 # Configure activation actions for asset section 191 activationActions: 193 - name: activate # publish 194 - name: deactivate # unpublish 210 # Configure activation actions for folder section 211 activationActions: 213 - name: activate # publish 214 - name: activateRecursive # publish recursive 215 - name: deactivate # unpublish 225 # Configure activation actions for multiple section 226 activationActions: 228 - name: activate # publish 229 - name: deactivate # unpublish 244 The workflow module provides two commands for publication (i.e. activate 245 and deactivate). They are located in configuration here: 246 `/modules/workflow/commands/workflow`. The activate and deactivate 248 these chains will call the versioning command before activating (or 249 deactivating). Versioning may or not be needed. 255 the Pages app works OOTB. You can schedule activation for a later date 257 for deactivation. Enabling-workflow-in-content-apps.adoc (8 usages found) 15 launches the `activate` command inside the `versioned` catalog which is 16 part of the Activation module. The action creates a new version of the 17 published item and and activates it to the public instance but does not 45 The command name is the same, `activate`, but the commands reside in 47 `activate` command from the `versioned` catalog in the Activation 48 module. The other `activate` command is in the `workflow` catalog in the 96 . Remove all properties from our activate action inside the assets app. 101 `activate` action you already did. Override properties to change the Magnolia-four-eye-workflow.adoc (3 usages found) 49 === Content Activation 52 then time to activate that content. 54 image:content-activation.png[image,role="zoom"] Workflow-processes.adoc (11 usages found) 73 `/workflows/activate.yaml` 77 id: com.example.workflow.CustomActivation 78 name: activate 79 resourcePath: CustomActivation.bpmn 133 image:activate-workflow-command.png[image,role="zoom"] 135 The `activate` command chain inside the `workflow` catalog consists of 136 two commands: `version` and `activate`. When you launch this chain the 137 content is first versioned and then activated. The `activate` command 138 launches the activate workflow. 206 publication. By default this is the `activate` command from the default 210 uses the `personalizationActivation` command. The command is modules/ROOT/pages/Releases/Cloud-changelog/Magnolia-Cloud-updates-2017 (2 usages found) Magnolia-Cloud-update---December-2017.adoc (1 usage found) 84 SSL (Secure Sockets Layer) is now activated for the cockpit and your Magnolia-Cloud-update---March-2017.adoc (1 usage found) 56 `/server/activation/subscribers` node). modules/ROOT/pages/Support/Magnolia-5-UI-documentation/Content-apps-5-UI/App-configuration-5-UI (18 usages found) Action-definition-5-UI.adoc (17 usages found) 164 `activate` command publishes content from the author instance to public 180 *Example*: `activate` action definition in 188 activate: 189 command: activate 192 class: info.magnolia.ui.framework.action.ActivationActionDefinition 216 that has the same name as an existing command such as `activate`. 405 |`info.magnolia.ui.framework.action.[info.magnolia.ui.framework.action.ActivationActionDefinition](!javadoc)` 406 |Activates an item. By default, performs a non-recursive activation. 409 |`info.magnolia.ui.framework.action.[info.magnolia.ui.framework.action.DeactivationActionDefinition](!javadoc)` 410 |Deactivates an item. 677 |Returns `true` if all ancestors of the item are activated. 680 |Returns `true` if a node’s `ActivationStatus` is not 681 `ACTIVATION_STATUS_NOT_ACTIVATED`. 698 *Example*: `activate` action supporting multiple items: 703 activate: 705 class: info.magnolia.ui.framework.action.ActivationActionDefinition 706 command: activate Column-definition-5-UI.adoc (1 usage found) 57 displays the activation status of an item. modules/ROOT/pages/Templating/Template-scripts/Templating-functions (13 usages found) cmsfn.adoc (3 usages found) 1348 |LAST_ACTIVATED |`mgnl:lastActivated` 1349 |LAST_ACTIVATED_BY |`mgnl:lastActivatedBy` 1350 |ACTIVATION_STATUS |`mgnl:activationStatus` jsonfn.adoc (10 usages found) 710 "mgnl:lastActivatedBy" : "superuser", 717 "mgnl:lastActivated" : 1488435020565, 718 "mgnl:activationStatus" : true, 774 "mgnl:lastActivated" : 1488435020565, 775 "mgnl:activationStatus" : true, 778 "mgnl:lastActivatedBy" : "superuser", 1114 "mgnl:lastActivated" : 1488452079969, 1115 "mgnl:lastActivatedBy" : "superuser" 1119 "mgnl_lastActivated" : 1488452079969, 1120 "mgnl_lastActivatedBy" : "superuser" modules/ROOT/partials/i (8 usages found) _REST-delivery-endpoint-v1-filter-examples.adoc (3 usages found) 26 "mgnl:lastActivatedBy": "superuser", 28 "mgnl:lastActivated": "2018-03-09T13:47:50.329+01:00", 33 "mgnl:activationStatus": "true", _REST-delivery-endpoint-v2-filter-examples.adoc (3 usages found) 49 "mgnl:lastActivatedBy": "superuser", 51 "mgnl:lastActivated": "2019-09-25T08:49:35.482+02:00", 56 "mgnl:activationStatus": "true", _What-is-a-command.adoc (1 usage found) 5 Magnolia uses commands to activate content, send email, flush the cache, _What-is-REST.adoc (1 usage found) 8 xref:/Developing/Commands.adoc[commands] to activate, export and import modules/ROOT/partials/i/_Deprecation-policy (4 usages found) _Deprecations-list.adoc (4 usages found) 210 == Activation module and Transactional Activation module (November 15, 2017) 215 Since Magnolia 5.6, the Activation module and Transactional Activation 221 Publishing is a refactored version of activation. The driving decision 223 reason was to remove deprecated code. The core activation concepts modules/ROOT/partials/i/_Deprecation-policy/_Deprecation-policy (4 usages found) _Deprecations-list.adoc (4 usages found) 232 == Activation module and Transactional Activation module (November 15, 2017) 238 Since Magnolia 5.6, the Activation module and Transactional Activation 245 Publishing is a refactored version of activation. The driving decision 247 reason was to remove deprecated code. The core activation concepts modules/ROOT/partials/snippets/developing/rest (2 usages found) r_rest-default-permissions.adoc (2 usages found) 21 | |Activate 22 |`/modules/rest-services/rest-endpoints/commands/enabledCommands/activate/access/roles` modules/ROOT/partials/snippets/modules (2 usages found) s_ldapConnectorModule-UserManager-Properties.adoc (2 usages found) 111 * `info.magnolia.jaas.sp.ldap.connection.password.ActivationKeyBasedPasswordDecoder` + 112 This implementation uses the same set of keys as activation. To gain an Usage in comments (2 usages found) product-docs-local (2 usages found) modules/ROOT/pages/Administration/Security (2 usages found) Users.adoc (2 usages found) 68 // tag::anonymous-role-do-not-activate[] 76 // end::anonymous-role-do-not-activate[] Usage in string constants (27 usages found) product-docs-local (27 usages found) modules/ROOT/attachments (3 usages found) config.server.filters.dumpHeaders.xml (3 usages found) 18 27 30 modules/ROOT/pages/Modules/List-of-modules/Personalization-module/Creating-custom-traits-without-Java/Creating-a-custom-cookie-trait-without-Java (24 usages found) config.modules.personalization-traits.traits.cookies.ruleField.fields.visits.xml (21 usages found) 18 27 30 52 61 64 86 95 98 124 133 136 162 171 174 200 209 212 238 247 250 config.modules.personalization-traits.traits.cookies.ruleField.options.visits.xml (3 usages found) 15 24 27