Date: Fri, 29 Mar 2024 08:46:56 +0100 (CET) Message-ID: <1880040610.111564.1711698416080@srvdoc.doc.ipesoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_111563_370305226.1711698416080" ------=_Part_111563_370305226.1711698416080 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Data archiving is defined by the configuration of an object Historica= l value. Object describes the source of archived values and archiving m= ethod. Object of Historical value type allows to archive:
Object of Historical value t= ype can be:
!!! WARNING !!!
When saving the configuration of the object of Historical value typ=
e (by means of the processes D2000 CNF), D2000 system is checking whethe=
r the object has not been changed within the meaning of the classification =
mentioned above. If the object has been already changed, the system display=
s a warning message that contains both the previous and current object stat=
uses. If the operator saves the object configuration in spite of this fact,=
some of the D2000 system parts will get into inconsistent status.
Ex=
ample: The object H.Archiv has been changed from structured hist=
orical value to simple one then all ESL scripts, containing e.g. the item <=
i>H.Archiv [6]^Item, are obviously incorrect. Such situation als=
o occurs everywhere the items of structured historical values are used in c=
onfiguration.
Defining the same data source for more Historical values allows t= o a multiple archiving of the same data with the definition of various arch= iving criteria. For example: a short-term archiving that very precisely sto= res all value changes and a long-term archiving that stores only significan= t changes.
The process D2000 Archiv= a> provides value archiving of object of D2000 system into SQL database.
Related pages: