@dangl/avacloud-client-node 1.13.0 → 1.14.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.swagger-codegen/VERSION +1 -1
- package/api.d.ts +168 -18
- package/api.js +228 -24
- package/api.js.map +1 -1
- package/api.ts +339 -25
- package/package.json +1 -1
package/.swagger-codegen/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
2.4.
|
|
1
|
+
2.4.24
|
package/api.d.ts
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* AVACloud API 1.
|
|
2
|
+
* AVACloud API 1.22.0
|
|
3
3
|
* AVACloud API specification
|
|
4
4
|
*
|
|
5
|
-
* OpenAPI spec version: 1.
|
|
5
|
+
* OpenAPI spec version: 1.22.0
|
|
6
6
|
*
|
|
7
7
|
*
|
|
8
8
|
* NOTE: This class is auto generated by the swagger code generator program.
|
|
@@ -182,6 +182,14 @@ export declare class CalculationDto {
|
|
|
182
182
|
* Will be -1 if the Formula is correct, else it will show the position in the formula where an error was encountered. This is a zero based index.
|
|
183
183
|
*/
|
|
184
184
|
'errorPositionInLine': number;
|
|
185
|
+
/**
|
|
186
|
+
* These are Catalogues that are used within this Calculation. Catalogues are used to describe catalogues, or collections, that can be used to describe elements with commonly known properties. For example, QuantityAssignments use these to categorize themselves. They are propagate to all child elements, e.g. other containers and QuantityAssignments. In the context of a ServiceSpecification, all elements share the same instance of the collection.
|
|
187
|
+
*/
|
|
188
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
189
|
+
/**
|
|
190
|
+
* Referenced catalogues for this Calculation.
|
|
191
|
+
*/
|
|
192
|
+
'catalogueReferences'?: Array<CatalogueReferenceDto>;
|
|
185
193
|
static discriminator: string | undefined;
|
|
186
194
|
static attributeTypeMap: Array<{
|
|
187
195
|
name: string;
|
|
@@ -648,6 +656,14 @@ export declare class ItemNumberSchemaDto {
|
|
|
648
656
|
* The collection of tiers for this ItemNumberSchema.
|
|
649
657
|
*/
|
|
650
658
|
'tiers'?: Array<ItemNumberSchemaTierDto>;
|
|
659
|
+
/**
|
|
660
|
+
* The separator to use for separiting the different levels in an ItemNumber. Defaults to DEFAULT_SEPARATOR, which is a point '.'. Setting this to a space or other whitespaces is discouraged, as this might not work correct in all situations and item numbers could be displayed not as intended. This can not be set to an empty or null string, trying that will default to the DEFAULT_SEPARATOR. If a value is set that has a different length than one '1', the DEFAULT_SEPARATOR will be used instead. You should also not use values for the separator that are also valid for the item numbers themselves, as that might also lead to incorrect results
|
|
661
|
+
*/
|
|
662
|
+
'separator'?: string;
|
|
663
|
+
/**
|
|
664
|
+
* This string is used to fill (left-pad) item numbers. For example, if a tier has a length of '4' but the given item number is '12', with a Filler of '0', then the final item number will be represented as '0'. This must be a single character string, if a value is given where the Length property does not evaluate to '1', the DEFAULT_FILLER '0' is used. A space is fine to use. You should ensure that you use a value different than Separator, as that might produce unexpected results. No attempt is done by the code to recover from such ambiguous configurations
|
|
665
|
+
*/
|
|
666
|
+
'filler'?: string;
|
|
651
667
|
static discriminator: string | undefined;
|
|
652
668
|
static attributeTypeMap: Array<{
|
|
653
669
|
name: string;
|
|
@@ -680,6 +696,14 @@ export declare class ItemNumberSchemaTierDto {
|
|
|
680
696
|
* Indicates if this tier represents a lot. See the documentation for more information about lots.
|
|
681
697
|
*/
|
|
682
698
|
'isLot': boolean;
|
|
699
|
+
/**
|
|
700
|
+
* This value is the increment, or step size, that should be used for new item numbers. It defaults to DEFAULT_INCREMENT, but can be changed to any other positive number greater than zero. Invalid values make this be set to one '1'
|
|
701
|
+
*/
|
|
702
|
+
'increment': number;
|
|
703
|
+
/**
|
|
704
|
+
* This is an optional name for the given tier
|
|
705
|
+
*/
|
|
706
|
+
'tierName'?: string;
|
|
683
707
|
static discriminator: string | undefined;
|
|
684
708
|
static attributeTypeMap: Array<{
|
|
685
709
|
name: string;
|
|
@@ -752,6 +776,10 @@ export declare class LabourPriceComponentDto {
|
|
|
752
776
|
* The total, calculated time of this component. Will return the result rounded to three decimal places.
|
|
753
777
|
*/
|
|
754
778
|
'totalTime': number;
|
|
779
|
+
/**
|
|
780
|
+
* These are Catalogues that are used within this PriceComponent. Catalogues are used to describe catalogues, or collections, that can be used to describe elements with commonly known properties. For example, QuantityAssignments use these to categorize themselves. They are propagate to all child elements, e.g. other containers and QuantityAssignments. In the context of a ServiceSpecification, all elements share the same instance of the collection.
|
|
781
|
+
*/
|
|
782
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
755
783
|
static discriminator: string | undefined;
|
|
756
784
|
static attributeTypeMap: Array<{
|
|
757
785
|
name: string;
|
|
@@ -814,6 +842,78 @@ export declare class NoteTextDto extends IElementDto {
|
|
|
814
842
|
*/
|
|
815
843
|
'standardizedDescription'?: StandardizedDescriptionDto;
|
|
816
844
|
'elementType'?: string;
|
|
845
|
+
/**
|
|
846
|
+
* This is an identifier specific for this description. Some exchange formats, like GAEB XML, use it to identify descriptions. It's different to an elements identifier in that it should only apply to the description component, meaning the text itself.
|
|
847
|
+
*/
|
|
848
|
+
'descriptionId'?: string;
|
|
849
|
+
static discriminator: string | undefined;
|
|
850
|
+
static attributeTypeMap: Array<{
|
|
851
|
+
name: string;
|
|
852
|
+
baseName: string;
|
|
853
|
+
type: string;
|
|
854
|
+
}>;
|
|
855
|
+
static getAttributeTypeMap(): {
|
|
856
|
+
name: string;
|
|
857
|
+
baseName: string;
|
|
858
|
+
type: string;
|
|
859
|
+
}[];
|
|
860
|
+
}
|
|
861
|
+
/**
|
|
862
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
863
|
+
*/
|
|
864
|
+
export declare class OenormOriginCodeDto {
|
|
865
|
+
static discriminator: string | undefined;
|
|
866
|
+
static attributeTypeMap: Array<{
|
|
867
|
+
name: string;
|
|
868
|
+
baseName: string;
|
|
869
|
+
type: string;
|
|
870
|
+
}>;
|
|
871
|
+
static getAttributeTypeMap(): {
|
|
872
|
+
name: string;
|
|
873
|
+
baseName: string;
|
|
874
|
+
type: string;
|
|
875
|
+
}[];
|
|
876
|
+
}
|
|
877
|
+
/**
|
|
878
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used. It is special for Positions and extends the OenormProperties base class.
|
|
879
|
+
*/
|
|
880
|
+
export declare class OenormPositionPropertiesDto {
|
|
881
|
+
/**
|
|
882
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
883
|
+
*/
|
|
884
|
+
'originCode': OenormOriginCodeDto;
|
|
885
|
+
/**
|
|
886
|
+
* This marks if the opening texts within this element are considered free text. It corresponds to 'vorbemerkungskennzeichen' in ÖNorm.
|
|
887
|
+
*/
|
|
888
|
+
'openingTextIsFreeText': boolean;
|
|
889
|
+
/**
|
|
890
|
+
* This indicates if the ÖNorm 'wesentliche position' mark is set
|
|
891
|
+
*/
|
|
892
|
+
'isMainPosition': boolean;
|
|
893
|
+
static discriminator: string | undefined;
|
|
894
|
+
static attributeTypeMap: Array<{
|
|
895
|
+
name: string;
|
|
896
|
+
baseName: string;
|
|
897
|
+
type: string;
|
|
898
|
+
}>;
|
|
899
|
+
static getAttributeTypeMap(): {
|
|
900
|
+
name: string;
|
|
901
|
+
baseName: string;
|
|
902
|
+
type: string;
|
|
903
|
+
}[];
|
|
904
|
+
}
|
|
905
|
+
/**
|
|
906
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used.
|
|
907
|
+
*/
|
|
908
|
+
export declare class OenormPropertiesDto {
|
|
909
|
+
/**
|
|
910
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
911
|
+
*/
|
|
912
|
+
'originCode': OenormOriginCodeDto;
|
|
913
|
+
/**
|
|
914
|
+
* This marks if the opening texts within this element are considered free text. It corresponds to 'vorbemerkungskennzeichen' in ÖNorm.
|
|
915
|
+
*/
|
|
916
|
+
'openingTextIsFreeText': boolean;
|
|
817
917
|
static discriminator: string | undefined;
|
|
818
918
|
static attributeTypeMap: Array<{
|
|
819
919
|
name: string;
|
|
@@ -1020,7 +1120,7 @@ export declare class PositionDto extends IElementDto {
|
|
|
1020
1120
|
*/
|
|
1021
1121
|
'totalPriceGrossDeducted': number;
|
|
1022
1122
|
/**
|
|
1023
|
-
* Net price after applied deductions.
|
|
1123
|
+
* Net price after applied deductions. Please be aware that this is the total price, from TotalPrice, not the unit price of the position.
|
|
1024
1124
|
*/
|
|
1025
1125
|
'deductedPrice': number;
|
|
1026
1126
|
/**
|
|
@@ -1065,10 +1165,18 @@ export declare class PositionDto extends IElementDto {
|
|
|
1065
1165
|
*/
|
|
1066
1166
|
'commerceProperties'?: CommercePropertiesDto;
|
|
1067
1167
|
/**
|
|
1068
|
-
* If this position is an Alternative, then this property should point to the id of the position in this service specification that it can replace.
|
|
1168
|
+
* If this position is an Alternative, then this property should point to the id of the position in this service specification that it can replace. If this is set to a value, you can optionally also specify an identifier via AlternativeIdentifier to specifiy multiple positions that must be used together to be an alternative to a single base position.
|
|
1069
1169
|
*/
|
|
1070
1170
|
'alternativeTo'?: string;
|
|
1071
1171
|
/**
|
|
1172
|
+
* This is an optional property that can be used together with AlternativeTo. If this is set, you can indicate which alternative group a specific position is assigned to. That way, if you specifiy multiple alternative Positions with the same AlternativeIdentifier, you can indicate that to replace a single base Position, multiple alternative Positions should be used. This property is not checked or managed automatically, so it is possible for this property to become invalid, by for example setting this property but not setting a base position via AlternativeTo.
|
|
1173
|
+
*/
|
|
1174
|
+
'alternativeIdentifier'?: number;
|
|
1175
|
+
/**
|
|
1176
|
+
* This is an optional property that can be used together with AlternativeTo and AlternativeGroupIdentifier. If this is set, you can indicate which alternative group a specific position is assigned to. That way, you can specify the id (in integer format) for the alternative group this position belongs to. It's different to AlternativeIdentifier in that the other property describes the id of the group, while this property here describes the group itself. If a position only has set AlternativeGroupIdentifier but not AlternativeIdentifier, then it likely is a base position for a specific group. This was introduced in version v2.9.0 to be able to model both position and group ids for alternative group combinations. This property is not checked or managed automatically, so it is possible for this property to become invalid, by for example setting this property but not setting a base position via AlternativeTo.
|
|
1177
|
+
*/
|
|
1178
|
+
'alternativeGroupIdentifier'?: number;
|
|
1179
|
+
/**
|
|
1072
1180
|
* If this is true, it indicates that the position is intended to be a lump sum, \"Pauschal\" in German. This means the position total price that is being invoiced should not depend on the actual quantity. In practice, partial invoices are still often used for partial services rendered. This property does not affect the price calculation for this position. Typically, the Quantity should be set to 1.0 when this flag is used.
|
|
1073
1181
|
*/
|
|
1074
1182
|
'isLumpSum': boolean;
|
|
@@ -1097,6 +1205,18 @@ export declare class PositionDto extends IElementDto {
|
|
|
1097
1205
|
* This identifier can be used to point to the Id of an ExecutionDescription in the same ServiceSpecification. ExecutionDescriptions act as a way to centrally describe how positions should be executed in practice. Often, the position itself still has text of its own to highlight deviations from that or add more details.
|
|
1098
1206
|
*/
|
|
1099
1207
|
'executionDescriptionReference'?: string;
|
|
1208
|
+
/**
|
|
1209
|
+
* This indicates if a position has not been offered. This is typically only expected to be true when the exchange phase of the parent ServiceSpecification is Offer, and it means that the position has not been offered at all.
|
|
1210
|
+
*/
|
|
1211
|
+
'notOffered': boolean;
|
|
1212
|
+
/**
|
|
1213
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used. It is special for Positions and extends the OenormProperties base class.
|
|
1214
|
+
*/
|
|
1215
|
+
'oenormPositionProperties'?: OenormPositionPropertiesDto;
|
|
1216
|
+
/**
|
|
1217
|
+
* This is an identifier specific for this description. Some exchange formats, like GAEB XML, use it to identify descriptions. It's different to an elements identifier in that it should only apply to the description component, meaning the text itself.
|
|
1218
|
+
*/
|
|
1219
|
+
'descriptionId'?: string;
|
|
1100
1220
|
static discriminator: string | undefined;
|
|
1101
1221
|
static attributeTypeMap: Array<{
|
|
1102
1222
|
name: string;
|
|
@@ -1141,6 +1261,10 @@ export declare class PriceComponentDto {
|
|
|
1141
1261
|
* The single Calculation elements this price component is composed of.
|
|
1142
1262
|
*/
|
|
1143
1263
|
'values'?: Array<CalculationDto>;
|
|
1264
|
+
/**
|
|
1265
|
+
* These are Catalogues that are used within this PriceComponent. Catalogues are used to describe catalogues, or collections, that can be used to describe elements with commonly known properties. For example, QuantityAssignments use these to categorize themselves. They are propagate to all child elements, e.g. other containers and QuantityAssignments. In the context of a ServiceSpecification, all elements share the same instance of the collection.
|
|
1266
|
+
*/
|
|
1267
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
1144
1268
|
static discriminator: string | undefined;
|
|
1145
1269
|
static attributeTypeMap: Array<{
|
|
1146
1270
|
name: string;
|
|
@@ -1827,6 +1951,10 @@ export declare class ServiceSpecificationGroupDto extends IElementDto {
|
|
|
1827
1951
|
* Referenced catalogues for this QuantityAssignment.
|
|
1828
1952
|
*/
|
|
1829
1953
|
'catalogueReferences'?: Array<CatalogueReferenceDto>;
|
|
1954
|
+
/**
|
|
1955
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used.
|
|
1956
|
+
*/
|
|
1957
|
+
'oenormProperties'?: OenormPropertiesDto;
|
|
1830
1958
|
static discriminator: string | undefined;
|
|
1831
1959
|
static attributeTypeMap: Array<{
|
|
1832
1960
|
name: string;
|
|
@@ -1963,6 +2091,14 @@ export declare class SubDescriptionDto {
|
|
|
1963
2091
|
* This identifier can be used to point to the Id of an ExecutionDescription in the same ServiceSpecification. ExecutionDescriptions act as a way to centrally describe how positions (or sub descriptions) should be executed in practice. Often, the position (or sub description) itself still has text of its own to highlight deviations from that or add more details. When working with import and export features, this property is only supported in GAEB 90 data exchange.
|
|
1964
2092
|
*/
|
|
1965
2093
|
'executionDescriptionReference'?: string;
|
|
2094
|
+
/**
|
|
2095
|
+
* These are Catalogues that are used within this Calculation. Catalogues are used to describe catalogues, or collections, that can be used to describe elements with commonly known properties. For example, QuantityAssignments use these to categorize themselves. They are propagate to all child elements, e.g. other containers and QuantityAssignments. In the context of a ServiceSpecification, all elements share the same instance of the collection.
|
|
2096
|
+
*/
|
|
2097
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
2098
|
+
/**
|
|
2099
|
+
* This is an identifier specific for this description. Some exchange formats, like GAEB XML, use it to identify descriptions. It's different to an elements identifier in that it should only apply to the description component, meaning the text itself.
|
|
2100
|
+
*/
|
|
2101
|
+
'descriptionId'?: string;
|
|
1966
2102
|
static discriminator: string | undefined;
|
|
1967
2103
|
static attributeTypeMap: Array<{
|
|
1968
2104
|
name: string;
|
|
@@ -2156,9 +2292,10 @@ export declare class AslvConversionApi {
|
|
|
2156
2292
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2157
2293
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2158
2294
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2295
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2159
2296
|
* @param {*} [options] Override http request options.
|
|
2160
2297
|
*/
|
|
2161
|
-
aslvConversionConvertToGaeb(aslvFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2298
|
+
aslvConversionConvertToGaeb(aslvFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2162
2299
|
response: http.IncomingMessage;
|
|
2163
2300
|
body: Buffer;
|
|
2164
2301
|
}>;
|
|
@@ -2168,9 +2305,10 @@ export declare class AslvConversionApi {
|
|
|
2168
2305
|
* @param aslvFile The input file
|
|
2169
2306
|
* @param destinationOenormType Defaults to Lv2015
|
|
2170
2307
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2308
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2171
2309
|
* @param {*} [options] Override http request options.
|
|
2172
2310
|
*/
|
|
2173
|
-
aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2311
|
+
aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2174
2312
|
response: http.IncomingMessage;
|
|
2175
2313
|
body: Buffer;
|
|
2176
2314
|
}>;
|
|
@@ -2224,9 +2362,10 @@ export declare class AvaConversionApi {
|
|
|
2224
2362
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2225
2363
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2226
2364
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2365
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2227
2366
|
* @param {*} [options] Override http request options.
|
|
2228
2367
|
*/
|
|
2229
|
-
avaConversionConvertToGaeb(avaProject: ProjectDto, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2368
|
+
avaConversionConvertToGaeb(avaProject: ProjectDto, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2230
2369
|
response: http.IncomingMessage;
|
|
2231
2370
|
body: Buffer;
|
|
2232
2371
|
}>;
|
|
@@ -2236,9 +2375,10 @@ export declare class AvaConversionApi {
|
|
|
2236
2375
|
* @param avaProject The Dangl.AVA project
|
|
2237
2376
|
* @param destinationOenormType Defaults to Lv2015
|
|
2238
2377
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2378
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2239
2379
|
* @param {*} [options] Override http request options.
|
|
2240
2380
|
*/
|
|
2241
|
-
avaConversionConvertToOenorm(avaProject: ProjectDto, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2381
|
+
avaConversionConvertToOenorm(avaProject: ProjectDto, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2242
2382
|
response: http.IncomingMessage;
|
|
2243
2383
|
body: Buffer;
|
|
2244
2384
|
}>;
|
|
@@ -2390,9 +2530,10 @@ export declare class ExcelConversionApi {
|
|
|
2390
2530
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2391
2531
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2392
2532
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2533
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2393
2534
|
* @param {*} [options] Override http request options.
|
|
2394
2535
|
*/
|
|
2395
|
-
excelConversionConvertToGaeb(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2536
|
+
excelConversionConvertToGaeb(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2396
2537
|
response: http.IncomingMessage;
|
|
2397
2538
|
body: Buffer;
|
|
2398
2539
|
}>;
|
|
@@ -2404,9 +2545,10 @@ export declare class ExcelConversionApi {
|
|
|
2404
2545
|
* @param rebuildItemNumberSchema When importing new elements from Excel, sometimes the ItemNumberSchema in the file is not in compliance with the GAEB requirements. Enabling this option tries to repair the ItemNumberSchema. Defaults to false.
|
|
2405
2546
|
* @param destinationOenormType Defaults to Lv2015
|
|
2406
2547
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2548
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2407
2549
|
* @param {*} [options] Override http request options.
|
|
2408
2550
|
*/
|
|
2409
|
-
excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2551
|
+
excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2410
2552
|
response: http.IncomingMessage;
|
|
2411
2553
|
body: Buffer;
|
|
2412
2554
|
}>;
|
|
@@ -2460,9 +2602,10 @@ export declare class GaebConversionApi {
|
|
|
2460
2602
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2461
2603
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2462
2604
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2605
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2463
2606
|
* @param {*} [options] Override http request options.
|
|
2464
2607
|
*/
|
|
2465
|
-
gaebConversionConvertToGaeb(gaebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2608
|
+
gaebConversionConvertToGaeb(gaebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2466
2609
|
response: http.IncomingMessage;
|
|
2467
2610
|
body: Buffer;
|
|
2468
2611
|
}>;
|
|
@@ -2472,9 +2615,10 @@ export declare class GaebConversionApi {
|
|
|
2472
2615
|
* @param gaebFile The input file
|
|
2473
2616
|
* @param destinationOenormType Defaults to Lv2015
|
|
2474
2617
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2618
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2475
2619
|
* @param {*} [options] Override http request options.
|
|
2476
2620
|
*/
|
|
2477
|
-
gaebConversionConvertToOenorm(gaebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2621
|
+
gaebConversionConvertToOenorm(gaebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2478
2622
|
response: http.IncomingMessage;
|
|
2479
2623
|
body: Buffer;
|
|
2480
2624
|
}>;
|
|
@@ -2528,9 +2672,10 @@ export declare class OenormConversionApi {
|
|
|
2528
2672
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2529
2673
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2530
2674
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2675
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2531
2676
|
* @param {*} [options] Override http request options.
|
|
2532
2677
|
*/
|
|
2533
|
-
oenormConversionConvertToGaeb(oenormFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2678
|
+
oenormConversionConvertToGaeb(oenormFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2534
2679
|
response: http.IncomingMessage;
|
|
2535
2680
|
body: Buffer;
|
|
2536
2681
|
}>;
|
|
@@ -2540,9 +2685,10 @@ export declare class OenormConversionApi {
|
|
|
2540
2685
|
* @param oenormFile The input file
|
|
2541
2686
|
* @param destinationOenormType Defaults to Lv2015
|
|
2542
2687
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2688
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2543
2689
|
* @param {*} [options] Override http request options.
|
|
2544
2690
|
*/
|
|
2545
|
-
oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2691
|
+
oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2546
2692
|
response: http.IncomingMessage;
|
|
2547
2693
|
body: Buffer;
|
|
2548
2694
|
}>;
|
|
@@ -2596,9 +2742,10 @@ export declare class RebConversionApi {
|
|
|
2596
2742
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2597
2743
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2598
2744
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2745
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2599
2746
|
* @param {*} [options] Override http request options.
|
|
2600
2747
|
*/
|
|
2601
|
-
rebConversionConvertToGaeb(rebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2748
|
+
rebConversionConvertToGaeb(rebFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2602
2749
|
response: http.IncomingMessage;
|
|
2603
2750
|
body: Buffer;
|
|
2604
2751
|
}>;
|
|
@@ -2608,9 +2755,10 @@ export declare class RebConversionApi {
|
|
|
2608
2755
|
* @param rebFile The input file
|
|
2609
2756
|
* @param destinationOenormType Defaults to Lv2015
|
|
2610
2757
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2758
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2611
2759
|
* @param {*} [options] Override http request options.
|
|
2612
2760
|
*/
|
|
2613
|
-
rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2761
|
+
rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2614
2762
|
response: http.IncomingMessage;
|
|
2615
2763
|
body: Buffer;
|
|
2616
2764
|
}>;
|
|
@@ -2664,9 +2812,10 @@ export declare class SiaConversionApi {
|
|
|
2664
2812
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2665
2813
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2666
2814
|
* @param enforceStrictOfferPhaseLongTextOutput Defaults to false. If this is enabled, exported long texts to GAEB XML that use text additions will be strictly schema compliant. If this is not enabled, any text that is marked to contain a text addition is exported in full to ensure that incorrectly used text additions are still preserved in the export.
|
|
2815
|
+
* @param exportQuantityDetermination Defaults to false. If this is enabled, quantities are exported in detail in GAEB XML targets via the 'QtyDeterm' (Quantity Determination, or Quantity Take Off) fields. To control this, you can set custom quantity calculations in the 'QuantityComponents' property of positions. Please see the entry for 'Quantity Determination' in the Dangl.AVA HowTo documentation section. Please be advised that enabling this might export data that was not intended to be exported, like internal quantity calculation details, depending on what data you put in the 'QuantityComponents' property.
|
|
2667
2816
|
* @param {*} [options] Override http request options.
|
|
2668
2817
|
*/
|
|
2669
|
-
siaConversionConvertToGaeb(siaFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, options?: any): Promise<{
|
|
2818
|
+
siaConversionConvertToGaeb(siaFile: FileParameter, destinationGaebType?: 'Gaeb90' | 'Gaeb2000' | 'Gaeb2000Commerce' | 'GaebXml_V3_1' | 'GaebXml_V3_2' | 'GaebXml_V3_2_Commerce' | 'GaebXml_V3_3' | 'GaebXml_V3_3_Commerce', targetExchangePhaseTransform?: 'None' | 'Base' | 'OfferRequest' | 'Offer' | 'Grant' | 'CostEstimate' | 'SideOffer', enforceStrictOfferPhaseLongTextOutput?: boolean, exportQuantityDetermination?: boolean, options?: any): Promise<{
|
|
2670
2819
|
response: http.IncomingMessage;
|
|
2671
2820
|
body: Buffer;
|
|
2672
2821
|
}>;
|
|
@@ -2676,9 +2825,10 @@ export declare class SiaConversionApi {
|
|
|
2676
2825
|
* @param siaFile The input file
|
|
2677
2826
|
* @param destinationOenormType Defaults to Lv2015
|
|
2678
2827
|
* @param tryRepairProjectStructure Defaults to false. If this is enabled, the converter will try to ensure that the project structure can be mapped to Oenorm. It might introduce additional group levels to ensure a compatible target
|
|
2828
|
+
* @param skipTryEnforceSchemaCompliantXmlOutput If this option is enabled, AVACloud will not attempt to force a schema-compliant Xml output for ÖNorm targets that are Xml based. By default, AVACloud will try to add required fields, even if no data is present, with sensible defaults. This behavior can be disabled with this option.
|
|
2679
2829
|
* @param {*} [options] Override http request options.
|
|
2680
2830
|
*/
|
|
2681
|
-
siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2831
|
+
siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2682
2832
|
response: http.IncomingMessage;
|
|
2683
2833
|
body: Buffer;
|
|
2684
2834
|
}>;
|