#Review Deployment

In the following scenarios, a comparison page highlighting discrepancies between the tenant’s current configurations and the applied baseline will be generated, and the status of the tenant will display Review deployment.

• When a baseline is applied to a tenant and Elements completes the configuration comparison process.

• When the baseline of a tenant is changed, triggering a new configuration comparison process, and the process is complete.

For a tenant with this status, you need to review configurations, make updates as needed, and initiate the deployment process to deploy the finalized configurations to the tenant.

To open the comparisons page, on the Tenants page, locate the tenant, and click the Review deployment status link.

To export a report, click the More actions button in the upper-right corner and click Export. You can navigate to Process center to view the progress and then download the report.

In the summary section, you can find the following information:

• Tenant name and customer’s organization name

• Baseline name, baseline version, and baseline color

  If multiple baselines are applied to the tenant, they will be listed in the ranking order for clarity.

• Last deployed time and the View change log link

  The View change log link allows you to track tenant modifications over time. For detailed instructions, refer to View Change Logs.

  In the comparisons section, configuration comparisons are grouped into tabs. For quick access, you can search for a specific configuration by entering the configuration name in the Search text box and pressing Enter on your keyboard. If you want to focus on configurations from a specific baseline, click Filter, select the desired baseline, and click Apply changes.

Switch among these tabs to review and manage the configurations. Once the current configurations meet your requirements, you can click Deploy in the lower-right corner of the page to initiate the deployment process to deploy the finalized configurations to the tenant. For detailed instructions, refer to Execute Deployment. Note that only the selected configurations will be deployed to the tenant.

#Map Similarity Driven Instances

If the Matching theory method of the tenant is set to Similarity-based matching, when you access the comparison page, a Map similarity-driven instances window pops up, displaying tenant and baseline instances (referring to the baseline that has been applied to the tenant but not yet deployed) that cannot be matched by name, with a system-generated similarity score displayed to identify potential matches. This allows you to manually review and map these similarity-driven instances for further comparison.

The Similarity-based matching window keeps popping up until all instances are mapped or the matching theory method is changed back to Name-based matching. You can click Skip if you want to skip this step for this time.

The Last sync time field shows the time when data was synced. If you want to recalculate similarity, click Recalculate similarity, and then a process will start.

For efficient management, you can adjust the similarity floor. Only tenant and baseline instances with a similarity score above this threshold will appear below.

For each pair, the tenant instance appears on the left, while baseline instances are listed on the right in a drop-down list, sorted by highest similarity score at the top. You can select different baseline instances to view their similarity score. To check the detailed differences between the tenant and baseline instances, click the Compare button to open the Compare window. If a tenant instance can be mapped to a baseline instance, click the Map button. Once mapped, a Mapped tag will appear next to the tenant instance name, and the baseline instance will be available in other pairs.

To remove a mapping between a tenant instance and a baseline instance, click the Unmap button next to the pair.

After saving, click Confirm in the pop-up confirmation window. The comparison page will be regenerated where all mapped instances will be displayed in the Conflicts tab, while unmapped instances will be listed under the Unique to baseline and Unique to tenant tabs.

#Conflicts with Baseline

This tab displays the configurations that are configured differently (same instance name and mismatched property values) in the tenant and the baseline. You can expand or collapse all configurations under this tab by clicking Expand all or Collapse all.

Next to each instance name, you may find the following additional information:

• A system-generated similarity score. The score is always displayed, independent of the tenant's matching method (name-based or similarity-based).

• If a placeholder is used in an instance, a Placeholder referenced tag will appear next to the instance name. When a reference is added to the value, hovering over the tag will display a pop-up showing the related references.

#Accept Deviation

If you want to accept deviation of an instance, click Accept deviation next to the instance. Configure a duration either permanently or due by a custom date, enter a comment, and click Save to save the changes. An Accepted instance tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection.

To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the instance.

#Mark as Tenant-specific Setting

If you want to mark an instance as tenant-specific setting, click Mark as tenant-specific setting next to the instance. Enter a comment and click Save. A Tenant-specific setting tag will appear next to it. Once an instance is marked as tenant-specific setting, it will still be included in the configuration deployment. However, drift detection will now use this custom value as the new standard for detecting deviations.

To unmark an instance as tenant-specific setting, click Unmark, enter a comment, and click Save to save the changes. The Tenant-specific setting tag will disappear. Once an instance is unmarked as tenant-specific setting, it will still be monitored based on the baseline standard in drift detection.

#Edit an Instance

To view and manage the properties of an instance, click Edit next to the instance. The Edit window pops up, displaying properties in pairs (tenant vs. baseline).

Any property with a conflict will be indicated by a yellow icon preceding the property for easy identification. When a property conflict exists in JSON format, the specific differences will be highlighted, and an icon will appear beside it. Clicking this icon will open a full-screen view, allowing you to easily review the highlighted differences.

If a property cannot be updated, a View only tag will appear next to it. To help streamline the review process, you can click Hide view-only properties to focus only on those modifiable properties.

For easier review, matching properties are hidden by default, helping you focus on conflicts. You can click Show matching properties if you want to display these matching properties, and you can make updates to these matching configurations, if needed.

If you want to accept deviation of properties within an instance, select the properties, and click Accept deviation. Configure duration, enter a comment, and click Save to save the changes. An Accepted property tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the properties.

For each property pair, select the standard to confirm the settings to be deployed. If you choose the baseline as the standard, click Update to save the changes. If you select tenant setting as the standard, you must either mark it as a tenant-specific setting or accept it as a deviation, and then click Save to save your selection.

When a property is marked as tenant-specific settings, a Tenant-specific setting tag will appear next to it. This property will continue to be included in the configuration deployment. However, drift detection will use the tenant’s custom value as the new standard for detecting deviations. To unmark a property as tenant-specific setting, click Unmark, enter a comment, and click Save to save the changes. The Tenant-specific setting tag will disappear, and the property will once again be monitored based on the baseline standard in drift detection.

When a property is accepted, an Accepted instance tag will appear next to it. Although accepted deviations remain part of the configuration deployment, they are excluded from drift detection monitoring. To cancel the acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the property.

#Unique to Baseline

This tab displays the configurations that are exclusive to the baseline. You can expand or collapse all configurations under this tab by clicking Expand all or Collapse all. You can make updates as below.

#Add Configurations to Tenant

To deploy all configurations to the tenant, click Select all. If you want to deploy all configurations within a specific source to the tenant, select the checkbox next to the source. If you want to deploy one or more configurations within a specific source to the tenant, expand the source to find the configurations, and select the checkboxes next to the configurations. If you want to deploy an instance within a specific configuration to the tenant, expand the source to find the configuration, expand the configuration to locate the instance, and select the checkbox next to it.

#Accept Deviation

To accept deviation of an instance, click Accept deviation next to the instance. Configure duration, enter a comment, and click Save to save the changes. An Accepted instance tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection.

To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the instance.

#Edit an Instance

If you want to update the properties of an instance, click Edit next to the instance to open the Edit window. In the Edit window, locate a property, make updates, and click Update to save the changes. If a specific property cannot be updated, a View only tag will appear next to it.

If you want to accept deviation of properties within an instance, select the properties, and click Accept deviation. Configure duration, enter a comment, and click Save to save the changes. An Accepted property tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the properties.

#Unique to Tenant

This tab displays the configurations that are exclusive to the tenant. You can expand or collapse all configurations under this tab by clicking Expand all or Collapse all. You can make updates as below.

#Remove Configurations from Tenant

To remove all configurations from the tenant, click Deselect all. If you want to remove all configurations within a specific source from the tenant, deselect the checkbox next to the source. If you want to remove one or more configurations within a specific source from the tenant, expand the source to find the configurations, and deselect the checkboxes next to the configurations. If you want to remove an instance within a specific configuration from the tenant, expand the source to find the configuration, expand the configuration to locate the instance, and deselect the checkbox next to the it.

#Accept Deviation

If you want to accept deviation of an instance, click Accept deviation next to the instance. Configure duration, enter a comment, and click Save to save the changes. An Accepted instance tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection.

To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the instance.

#Edit an Instance

If you want to update the properties of an instance, click Edit next to the instance to open the Edit window. In the Edit window, locate a property, make updates, and click Update to save the changes.

If a property cannot be updated, a View only tag will appear next to it. To help streamline the review process, you can click Hide view-only properties to focus only on those modifiable properties.

If you want to accept deviation of properties within an instance, select the properties, and click Accept deviation. Configure duration, enter a comment, and click Save to save the changes. An Accepted property tag will appear next to it. Accepted deviations will still be included in configuration deployment. However, they will not be monitored in drift detection. To cancel acceptance, click Cancel acceptance. Enter a comment and click Save to save the changes. Canceling acceptance will re-enable drift detection for the properties.

#Matches with Baseline

This tab displays the configurations that are configured identically (same instance name and property values) in the tenant and the baseline. You can expand or collapse all configurations under this tab by clicking Expand all or Collapse all.

To view details of an instance, click View next to the instance to open the View window. There is no need to make updates.