...
| Sv translation | ||||
|---|---|---|---|---|
| ||||
Facilities, all of their child-facilities children and various associated elements can be copied with the help of a few clicks. This function spares everyone time and work who repeatedly needs already existing facilities and their structures, for example for the complete setup of new sites. In this article we'll be talking about important aspects that should be considered whilst copying facilities. For instance possible Possible risks that could arise from an inconsiderate copying of elements. Plus, we discuss the setup of a new site with the help of the function as a best practice example.
1. Wherecacan I find the function to copy facility?The function to copy facilities can be found in the lower left corner, at the bottom of the facility overview. Select the three-dotted-button to open additional options for facilities, which include including the copying. Click on the copy button to open the wizard that will guide you through the task.
2. Important general information about the functionData points should be linked to new external sources after being copied.Data points with external strategies are no longer linked to their external sources after being copied and therefore don't have sources from which they could receive no sources to get their data from. That's why you they should be linked to new sources. It is not possible to choose the original facility or its children as the new parent facility for the copy.Several problems with internal data point references could arise , if it would be possible to choose the original facility or its children as the new parent facility for the copy. That's why this functionality is not available. The facility on top of the hierarchy can not be copied.The facility on top of the hierarchy mostly is mostly the "organisation". It can not be copied due to the fact , that no that it is not possible to choose a the copied facility can choose itself or one of its subordinate facilities as a its new parent facility. The copying of report and regular tasks includes recipients, which could lead to unwanted spam.Every report task could include recipients that who receive the report as an email. Users can also be informed about regular tasks if they those match their issue notification settings. If you copy these elements, recipients might receive unwanted emails. DashboardsDashboard widgets should be adjusted if necessary.It may happen that the functionality of widgets is impaired because affected if the configuration does not fit the new facility anymore.
3. Application example: setup of a new siteThe initial effort for the setup of a new site can be reduced drastically due to the possibility to copy facilities. Already existing facilities, whose hierarchy and general structure resemble the ones that should be set up, can simply be duplicated.
Subordinate facilities should always be copied!It is necessary to include child facilities to duplicate whole hierarchies. Attention: Other chosen elements, like data points, properties or message rules, will also be copied for subordinate facilities. This is practical to maintain internal references of data points but could also cause problems, like unwanted spam triggered by the copying of report or regular tasks that may cause unwanted spam. Data points should be copied, because internal references and custom calculation rules willalsobeduplicatedincluded.Internal references, which belong, for example, to strategies that calculate the sum or average values of child facilities, will be copied. This data points and references won't need any adjustments if you have also duplicated all child facilities and the general structure. Custom calculation rules that have been created in QUDE will also be copied, including the used references to ata data points and properties and wontherefore don't need to be created newly from scratch. However, external references and their data will get lost. But the copies of the respective data points will be copied which should at least reduces reduce the initial creation effort. Message rules should be copied, because internal references and custom calculation rules will also beduplicatedincluded.The copying of message rules, that can be used Message rules should be copied if they are needed at the new site, . This can save a lot of time and work because this includes , thanks to the fact that the copies include all important settingsettings. If you copy more than needed, it's always still easier to delete delete redundant message rules than to create everything again. The copying of adjusted dashboards is useful,if the individual adjustments fit the new facilities.Individual configurations of widgets or newly created facility dashboards could also be useful for copied facilities and should be used copied if that's the case. Having said this, it's mostly better recommended to take use the automatically generated default dashboards. Properties should only be copied, ifthetheir values match the new facilities.Values of properties rarely apply for to multiple facilities. That's why it's mostly unnecessary to copy them. However, in some cases you could benefit from the functionality, like for identically constructed equipment. Report and regular tasks should not be copied to avoid spam for possible recipients!Every report task could include recipients that receive the report as an email. Users can also be informed about regular tasks if they those match their issue notification settings. If you copy these elements, recipients might receive unwanted emails.
|
