i4connected Knowledgebase 5.6

Move Area

Abstract

Check out this article and learn more details about the Move Area panel, available under the Move entity feature.

When moving an Area, the user needs to select as an entity the desired area to be moved, using the Object filters panel. Immediately after selecting an Area, the Move Area panel is populated with the Destination selection section.

Move_area_object_filter.jpg

The Object filter panel

When selecting the destination Area, the Destination Site field is prepopulated by the system. However, in case the user desires to move the Area to another Site, it is not needed to select an Area as well, as long as the Area should be subordinated directly to the destination site.

Destination_Area.jpg

The destination Area field

Tip

Selection of destination Site and /or Area will be organized using the Object filter panel. For more details about the Object filter, please visit the dedicated article:

After all the move entity and destination entities are selected, the user can click either the Apply button, to proceed with the move operation, or the Close button, to dismiss the operation.

Apply.jpg

The selection of moving Area

Warning

The move area operation can be a time and resource consuming action, when dealing with large structures. Besides, this is a system function that should be used by a responsible and qualified user.

The move operation starts in the background by clicking the Apply button. A server notification message is displayed when the Area unit is moved to the destination entity.

MicrosoftTeams-image__5_.png

The server notification message

Warning

Since the Move entity panel itself is not guarded by specific permissions, the users having the "View Sites and Areas" permission enabled, will be able to select as Move entity or Destination entity, all the Areas that he/she can see. However, when the actual move operation is initiated, the system will check if the Move entity or the Destination entities can be managed or not. The Move function will check if the user performing the operation has management rights on the direct parent site of the Area before allowing the change. Also, the move destination Site or Area will be checked for management permissions before allowing the change.

When not enough rights are available, a warning toast message will be displayed on the screen.

MicrosoftTeams-image__4_.jpg

Example of toast message

When moving an Area , the assigned entities are transferred to the new structure, as follows:

  • The area keeps its list of directly assigned users, along with their assigned roles and permissions. To this list, the users inherited from the new higher hierarchical structure(s) are added, and their effective permissions are recalculated;

  • The areas assigned to the moved area will also be transferred to the new hierarchical location, along with their dependencies, and the directly assigned users with their roles and permissions. The sub-areas will also inherit the list of users, assigned to the new hierarchy, from all the structures positioned on a higher hierarchical level;

  • The moved areas and the sub-areas will carry their devices to the new location, along with all their device dependencies:

    • All the directly assigned users of a device will be transferred as dependencies of that device. Similar to the areas, the device will also inherit users assigned on a higher hierarchical level;

    • All the Signals, their assigned users along with Signal measurements;

    • All the assigned Device Response Teams;

    • All External Alarms;

    • All the Alarm script lists;

    • The Device's i4designer Application Mappings, if there is one set to Default;

  • The moved areas will be transferred along with their Measure aggregations, Area response teams, and Entity variables;

  • If a default i4designer application is available for the moved area, this will be transferred, as well.

The Move Area operation is marked by the system as an auditable event. For more details about the Audit Events, please visit the dedicated article: