Translations:Speicherfenster/24/en - Versionsgeschichte

T.Schnellbach am 16. Februar 2021 um 08:09 Uhr

2021-02-16T08:09:55Z

← Nächstältere Version		Version vom 16. Februar 2021, 10:09 Uhr
Zeile 1:		Zeile 1:
	The selection of type, class and name is mainly informative. The user himself is responsible for entering the data for releases afterwards. The identification of the release is made up of three digits: the first letter is determined by the selected class, the second by the selected type. These are then followed by a unique number in the third position, which is assigned corresponding to the order of the creation of the releases and their classes and types. The release ~~identification~~ determines how the simulation results are stored and how the releases can be utilized for the definition of system states. For this purpose, the release identifier is attached to the respective system element identifier with an underscore, e.g., T100_QA1.		The selection of type, class and name is mainly informative. The user himself is responsible for entering the data for releases afterwards. The identification of the release is made up of three digits: the first letter is determined by the selected class, the second by the selected type. These are then followed by a unique number in the third position, which is assigned corresponding to the order of the creation of the releases and their classes and types. The release identifier determines how the simulation results are stored and how the releases can be utilized for the definition of system states. For this purpose, the release identifier is attached to the respective system element identifier with an underscore, e.g., T100_QA1.

T.Schnellbach am 2. Februar 2021 um 12:27 Uhr

2021-02-02T12:27:49Z

← Nächstältere Version		Version vom 2. Februar 2021, 14:27 Uhr
Zeile 1:		Zeile 1:
	The selection of type, class and ~~the input of the designation~~ is mainly informative. The user himself is responsible for entering the data for ~~delivery~~ afterwards. The identification of the ~~levy~~ is made up of three digits: the first letter is determined by the selected class, the second by the selected type, followed by a unique number in the third position, which is assigned in the order ~~in which~~ the ~~levy~~ of the ~~respective class~~ and ~~type is created~~. The ~~charge~~ identification determines how the simulation results are stored and how the ~~charges~~ can be ~~addressed~~ for the definition of system states. For this purpose, the ~~delivery~~ identifier is ~~appended~~ to the respective system element identifier with underscore, e.g., T100_QA1.		The selection of type, class and name is mainly informative. The user himself is responsible for entering the data for releases afterwards. The identification of the release is made up of three digits: the first letter is determined by the selected class, the second by the selected type. These are then followed by a unique number in the third position, which is assigned corresponding to the order of the creation of the releases and their classes and types. The release identification determines how the simulation results are stored and how the releases can be utilized for the definition of system states. For this purpose, the release identifier is attached to the respective system element identifier with an underscore, e.g., T100_QA1.

Ferrao: Die Seite wurde neu angelegt: „The selection of type, class and the input of the designation is mainly informative. The user himself is responsible for entering the data for delivery afterwa…“

2020-10-30T13:57:40Z

Die Seite wurde neu angelegt: „The selection of type, class and the input of the designation is mainly informative. The user himself is responsible for entering the data for delivery afterwa…“

Neue Seite

The selection of type, class and the input of the designation is mainly informative. The user himself is responsible for entering the data for delivery afterwards. The identification of the levy is made up of three digits: the first letter is determined by the selected class, the second by the selected type, followed by a unique number in the third position, which is assigned in the order in which the levy of the respective class and type is created. The charge identification determines how the simulation results are stored and how the charges can be addressed for the definition of system states. For this purpose, the delivery identifier is appended to the respective system element identifier with underscore, e.g., T100_QA1.