@dangl/avacloud-client-node 1.10.0 → 1.15.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/LICENSE.md +1 -1
- package/api.d.ts +215 -20
- package/api.js +293 -24
- package/api.js.map +1 -1
- package/api.ts +437 -27
- package/package.json +1 -1
package/.swagger-codegen/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
2.4.
|
|
1
|
+
2.4.24
|
package/LICENSE.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
### Licence
|
|
2
2
|
|
|
3
|
-
#### Copyright (c)
|
|
3
|
+
#### Copyright (c) 2021 Dangl IT GmbH, [https://www.dangl-it.com](https://www.dangl-it.com)
|
|
4
4
|
|
|
5
5
|
This software shall only be used for non-commercial evaluation purposes.
|
|
6
6
|
Please contact Dangl**IT** for a commercial licence.
|
package/api.d.ts
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
/**
|
|
2
|
-
* AVACloud API 1.
|
|
2
|
+
* AVACloud API 1.23.3
|
|
3
3
|
* AVACloud API specification
|
|
4
4
|
*
|
|
5
|
-
* OpenAPI spec version: 1.
|
|
5
|
+
* OpenAPI spec version: 1.23.3
|
|
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;
|
|
@@ -560,6 +568,14 @@ export declare class GrossPriceComponentDto {
|
|
|
560
568
|
* The total gross price for all components of a given tax rate.
|
|
561
569
|
*/
|
|
562
570
|
'totalGross': number;
|
|
571
|
+
/**
|
|
572
|
+
* The total gross price for all components of a given tax rate, after applied deductions.
|
|
573
|
+
*/
|
|
574
|
+
'totalGrossDeducted': number;
|
|
575
|
+
/**
|
|
576
|
+
* The total tax amount for all components of a given tax rate, after applied deductions.
|
|
577
|
+
*/
|
|
578
|
+
'totalTaxDeducted': number;
|
|
563
579
|
static discriminator: string | undefined;
|
|
564
580
|
static attributeTypeMap: Array<{
|
|
565
581
|
name: string;
|
|
@@ -640,6 +656,18 @@ export declare class ItemNumberSchemaDto {
|
|
|
640
656
|
* The collection of tiers for this ItemNumberSchema.
|
|
641
657
|
*/
|
|
642
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;
|
|
667
|
+
/**
|
|
668
|
+
* This is just a string property that can optionally be used to store additional data for this ItemNumberSchema, e.g. an identification or a type. It does not have any influence over how item numbers are generated, and is not supported in most exchange formats. However, it is used to store ÖNorm service specification structure types.
|
|
669
|
+
*/
|
|
670
|
+
'identifier'?: string;
|
|
643
671
|
static discriminator: string | undefined;
|
|
644
672
|
static attributeTypeMap: Array<{
|
|
645
673
|
name: string;
|
|
@@ -672,6 +700,14 @@ export declare class ItemNumberSchemaTierDto {
|
|
|
672
700
|
* Indicates if this tier represents a lot. See the documentation for more information about lots.
|
|
673
701
|
*/
|
|
674
702
|
'isLot': boolean;
|
|
703
|
+
/**
|
|
704
|
+
* 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'
|
|
705
|
+
*/
|
|
706
|
+
'increment': number;
|
|
707
|
+
/**
|
|
708
|
+
* This is an optional name for the given tier
|
|
709
|
+
*/
|
|
710
|
+
'tierName'?: string;
|
|
675
711
|
static discriminator: string | undefined;
|
|
676
712
|
static attributeTypeMap: Array<{
|
|
677
713
|
name: string;
|
|
@@ -744,6 +780,10 @@ export declare class LabourPriceComponentDto {
|
|
|
744
780
|
* The total, calculated time of this component. Will return the result rounded to three decimal places.
|
|
745
781
|
*/
|
|
746
782
|
'totalTime': number;
|
|
783
|
+
/**
|
|
784
|
+
* 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.
|
|
785
|
+
*/
|
|
786
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
747
787
|
static discriminator: string | undefined;
|
|
748
788
|
static attributeTypeMap: Array<{
|
|
749
789
|
name: string;
|
|
@@ -806,6 +846,78 @@ export declare class NoteTextDto extends IElementDto {
|
|
|
806
846
|
*/
|
|
807
847
|
'standardizedDescription'?: StandardizedDescriptionDto;
|
|
808
848
|
'elementType'?: string;
|
|
849
|
+
/**
|
|
850
|
+
* 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.
|
|
851
|
+
*/
|
|
852
|
+
'descriptionId'?: string;
|
|
853
|
+
static discriminator: string | undefined;
|
|
854
|
+
static attributeTypeMap: Array<{
|
|
855
|
+
name: string;
|
|
856
|
+
baseName: string;
|
|
857
|
+
type: string;
|
|
858
|
+
}>;
|
|
859
|
+
static getAttributeTypeMap(): {
|
|
860
|
+
name: string;
|
|
861
|
+
baseName: string;
|
|
862
|
+
type: string;
|
|
863
|
+
}[];
|
|
864
|
+
}
|
|
865
|
+
/**
|
|
866
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
867
|
+
*/
|
|
868
|
+
export declare class OenormOriginCodeDto {
|
|
869
|
+
static discriminator: string | undefined;
|
|
870
|
+
static attributeTypeMap: Array<{
|
|
871
|
+
name: string;
|
|
872
|
+
baseName: string;
|
|
873
|
+
type: string;
|
|
874
|
+
}>;
|
|
875
|
+
static getAttributeTypeMap(): {
|
|
876
|
+
name: string;
|
|
877
|
+
baseName: string;
|
|
878
|
+
type: string;
|
|
879
|
+
}[];
|
|
880
|
+
}
|
|
881
|
+
/**
|
|
882
|
+
* 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.
|
|
883
|
+
*/
|
|
884
|
+
export declare class OenormPositionPropertiesDto {
|
|
885
|
+
/**
|
|
886
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
887
|
+
*/
|
|
888
|
+
'originCode': OenormOriginCodeDto;
|
|
889
|
+
/**
|
|
890
|
+
* This marks if the opening texts within this element are considered free text. It corresponds to 'vorbemerkungskennzeichen' in ÖNorm.
|
|
891
|
+
*/
|
|
892
|
+
'openingTextIsFreeText': boolean;
|
|
893
|
+
/**
|
|
894
|
+
* This indicates if the ÖNorm 'wesentliche position' mark is set
|
|
895
|
+
*/
|
|
896
|
+
'isMainPosition': boolean;
|
|
897
|
+
static discriminator: string | undefined;
|
|
898
|
+
static attributeTypeMap: Array<{
|
|
899
|
+
name: string;
|
|
900
|
+
baseName: string;
|
|
901
|
+
type: string;
|
|
902
|
+
}>;
|
|
903
|
+
static getAttributeTypeMap(): {
|
|
904
|
+
name: string;
|
|
905
|
+
baseName: string;
|
|
906
|
+
type: string;
|
|
907
|
+
}[];
|
|
908
|
+
}
|
|
909
|
+
/**
|
|
910
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used.
|
|
911
|
+
*/
|
|
912
|
+
export declare class OenormPropertiesDto {
|
|
913
|
+
/**
|
|
914
|
+
* This indicates where the content of this element originates, if set. It corresponds to 'herkunftskennzeichen' in ÖNorm
|
|
915
|
+
*/
|
|
916
|
+
'originCode': OenormOriginCodeDto;
|
|
917
|
+
/**
|
|
918
|
+
* This marks if the opening texts within this element are considered free text. It corresponds to 'vorbemerkungskennzeichen' in ÖNorm.
|
|
919
|
+
*/
|
|
920
|
+
'openingTextIsFreeText': boolean;
|
|
809
921
|
static discriminator: string | undefined;
|
|
810
922
|
static attributeTypeMap: Array<{
|
|
811
923
|
name: string;
|
|
@@ -1012,7 +1124,7 @@ export declare class PositionDto extends IElementDto {
|
|
|
1012
1124
|
*/
|
|
1013
1125
|
'totalPriceGrossDeducted': number;
|
|
1014
1126
|
/**
|
|
1015
|
-
* Net price after applied deductions.
|
|
1127
|
+
* Net price after applied deductions. Please be aware that this is the total price, from TotalPrice, not the unit price of the position.
|
|
1016
1128
|
*/
|
|
1017
1129
|
'deductedPrice': number;
|
|
1018
1130
|
/**
|
|
@@ -1057,10 +1169,18 @@ export declare class PositionDto extends IElementDto {
|
|
|
1057
1169
|
*/
|
|
1058
1170
|
'commerceProperties'?: CommercePropertiesDto;
|
|
1059
1171
|
/**
|
|
1060
|
-
* 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.
|
|
1172
|
+
* 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.
|
|
1061
1173
|
*/
|
|
1062
1174
|
'alternativeTo'?: string;
|
|
1063
1175
|
/**
|
|
1176
|
+
* 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.
|
|
1177
|
+
*/
|
|
1178
|
+
'alternativeIdentifier'?: number;
|
|
1179
|
+
/**
|
|
1180
|
+
* 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.
|
|
1181
|
+
*/
|
|
1182
|
+
'alternativeGroupIdentifier'?: number;
|
|
1183
|
+
/**
|
|
1064
1184
|
* 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.
|
|
1065
1185
|
*/
|
|
1066
1186
|
'isLumpSum': boolean;
|
|
@@ -1089,6 +1209,18 @@ export declare class PositionDto extends IElementDto {
|
|
|
1089
1209
|
* 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.
|
|
1090
1210
|
*/
|
|
1091
1211
|
'executionDescriptionReference'?: string;
|
|
1212
|
+
/**
|
|
1213
|
+
* 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.
|
|
1214
|
+
*/
|
|
1215
|
+
'notOffered': boolean;
|
|
1216
|
+
/**
|
|
1217
|
+
* 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.
|
|
1218
|
+
*/
|
|
1219
|
+
'oenormPositionProperties'?: OenormPositionPropertiesDto;
|
|
1220
|
+
/**
|
|
1221
|
+
* 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.
|
|
1222
|
+
*/
|
|
1223
|
+
'descriptionId'?: string;
|
|
1092
1224
|
static discriminator: string | undefined;
|
|
1093
1225
|
static attributeTypeMap: Array<{
|
|
1094
1226
|
name: string;
|
|
@@ -1133,6 +1265,26 @@ export declare class PriceComponentDto {
|
|
|
1133
1265
|
* The single Calculation elements this price component is composed of.
|
|
1134
1266
|
*/
|
|
1135
1267
|
'values'?: Array<CalculationDto>;
|
|
1268
|
+
/**
|
|
1269
|
+
* 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.
|
|
1270
|
+
*/
|
|
1271
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
1272
|
+
static discriminator: string | undefined;
|
|
1273
|
+
static attributeTypeMap: Array<{
|
|
1274
|
+
name: string;
|
|
1275
|
+
baseName: string;
|
|
1276
|
+
type: string;
|
|
1277
|
+
}>;
|
|
1278
|
+
static getAttributeTypeMap(): {
|
|
1279
|
+
name: string;
|
|
1280
|
+
baseName: string;
|
|
1281
|
+
type: string;
|
|
1282
|
+
}[];
|
|
1283
|
+
}
|
|
1284
|
+
/**
|
|
1285
|
+
* This enumeration models types of price components for better classification.
|
|
1286
|
+
*/
|
|
1287
|
+
export declare class PriceComponentTypeDto {
|
|
1136
1288
|
static discriminator: string | undefined;
|
|
1137
1289
|
static attributeTypeMap: Array<{
|
|
1138
1290
|
name: string;
|
|
@@ -1346,6 +1498,12 @@ export declare class ProjectInformationDto {
|
|
|
1346
1498
|
*/
|
|
1347
1499
|
'priceComponents'?: Array<string>;
|
|
1348
1500
|
/**
|
|
1501
|
+
* This dictionary specifies actual types used for the PriceComponents. For example, a single price component might have the name 'Material' as a string, ans this dictionary would then have a key 'Material' and a value of Materials. You can not add keys here that are not also present in the PriceComponents property, and removing price components will also remove them from this dictionary here.
|
|
1502
|
+
*/
|
|
1503
|
+
'priceComponentTypes'?: {
|
|
1504
|
+
[key: string]: PriceComponentTypeDto;
|
|
1505
|
+
};
|
|
1506
|
+
/**
|
|
1349
1507
|
* This bool indicates if this project allows the bidder to add bidder comments. Bidder comments are a way to attach clarifying information when submitting an offer.
|
|
1350
1508
|
*/
|
|
1351
1509
|
'bidderCommentAllowed': boolean;
|
|
@@ -1607,10 +1765,14 @@ export declare class ServiceSpecificationDto {
|
|
|
1607
1765
|
*/
|
|
1608
1766
|
'exchangePhase': ExchangePhaseDto;
|
|
1609
1767
|
/**
|
|
1610
|
-
* This indicates where the service specification originates, i.e. from an exchange file format or self created.
|
|
1768
|
+
* This indicates where the service specification originates, i.e. from an exchange file format or self created. If applicable, additional information is present in the OriginDetail property.
|
|
1611
1769
|
*/
|
|
1612
1770
|
'origin': OriginDto;
|
|
1613
1771
|
/**
|
|
1772
|
+
* This property complements the Origin property. Some formats, e.g. GaebXml might have additional information attached, e.g. GAEB XML V3.2 oder GAEB XML V3.1. This string property is used to hold such data. The Dangl.AVA module does not have a list of possible values, since this is defined in the native format assemblies, e.g. Dangl.GAEB or Dangl.Oenorm.
|
|
1773
|
+
*/
|
|
1774
|
+
'originDetail'?: string;
|
|
1775
|
+
/**
|
|
1614
1776
|
* Creation date of this ServiceSpecification.
|
|
1615
1777
|
*/
|
|
1616
1778
|
'creationDate'?: Date;
|
|
@@ -1793,6 +1955,10 @@ export declare class ServiceSpecificationGroupDto extends IElementDto {
|
|
|
1793
1955
|
* Referenced catalogues for this QuantityAssignment.
|
|
1794
1956
|
*/
|
|
1795
1957
|
'catalogueReferences'?: Array<CatalogueReferenceDto>;
|
|
1958
|
+
/**
|
|
1959
|
+
* This class models special properties that only apply to some exchange scenarios where ÖNorm is used.
|
|
1960
|
+
*/
|
|
1961
|
+
'oenormProperties'?: OenormPropertiesDto;
|
|
1796
1962
|
static discriminator: string | undefined;
|
|
1797
1963
|
static attributeTypeMap: Array<{
|
|
1798
1964
|
name: string;
|
|
@@ -1929,6 +2095,14 @@ export declare class SubDescriptionDto {
|
|
|
1929
2095
|
* 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.
|
|
1930
2096
|
*/
|
|
1931
2097
|
'executionDescriptionReference'?: string;
|
|
2098
|
+
/**
|
|
2099
|
+
* 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.
|
|
2100
|
+
*/
|
|
2101
|
+
'projectCatalogues'?: Array<CatalogueDto>;
|
|
2102
|
+
/**
|
|
2103
|
+
* 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.
|
|
2104
|
+
*/
|
|
2105
|
+
'descriptionId'?: string;
|
|
1932
2106
|
static discriminator: string | undefined;
|
|
1933
2107
|
static attributeTypeMap: Array<{
|
|
1934
2108
|
name: string;
|
|
@@ -2027,7 +2201,7 @@ export declare class TradeDiscountDto {
|
|
|
2027
2201
|
*/
|
|
2028
2202
|
export declare class WarrantyDurationDto {
|
|
2029
2203
|
/**
|
|
2030
|
-
* The scalar value of the duration. This value must be equal to or bigger than zero (
|
|
2204
|
+
* The scalar value of the duration. This value must be equal to or bigger than zero (>= 0). Negative values can not be set and will be ignored.
|
|
2031
2205
|
*/
|
|
2032
2206
|
'duration': number;
|
|
2033
2207
|
/**
|
|
@@ -2121,9 +2295,11 @@ export declare class AslvConversionApi {
|
|
|
2121
2295
|
* @param aslvFile The input file
|
|
2122
2296
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2123
2297
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2298
|
+
* @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.
|
|
2299
|
+
* @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.
|
|
2124
2300
|
* @param {*} [options] Override http request options.
|
|
2125
2301
|
*/
|
|
2126
|
-
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', options?: any): Promise<{
|
|
2302
|
+
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<{
|
|
2127
2303
|
response: http.IncomingMessage;
|
|
2128
2304
|
body: Buffer;
|
|
2129
2305
|
}>;
|
|
@@ -2133,9 +2309,10 @@ export declare class AslvConversionApi {
|
|
|
2133
2309
|
* @param aslvFile The input file
|
|
2134
2310
|
* @param destinationOenormType Defaults to Lv2015
|
|
2135
2311
|
* @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
|
|
2312
|
+
* @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.
|
|
2136
2313
|
* @param {*} [options] Override http request options.
|
|
2137
2314
|
*/
|
|
2138
|
-
aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2315
|
+
aslvConversionConvertToOenorm(aslvFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2139
2316
|
response: http.IncomingMessage;
|
|
2140
2317
|
body: Buffer;
|
|
2141
2318
|
}>;
|
|
@@ -2188,9 +2365,11 @@ export declare class AvaConversionApi {
|
|
|
2188
2365
|
* @param avaProject The Dangl.AVA project
|
|
2189
2366
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2190
2367
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2368
|
+
* @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.
|
|
2369
|
+
* @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.
|
|
2191
2370
|
* @param {*} [options] Override http request options.
|
|
2192
2371
|
*/
|
|
2193
|
-
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', options?: any): Promise<{
|
|
2372
|
+
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<{
|
|
2194
2373
|
response: http.IncomingMessage;
|
|
2195
2374
|
body: Buffer;
|
|
2196
2375
|
}>;
|
|
@@ -2200,9 +2379,10 @@ export declare class AvaConversionApi {
|
|
|
2200
2379
|
* @param avaProject The Dangl.AVA project
|
|
2201
2380
|
* @param destinationOenormType Defaults to Lv2015
|
|
2202
2381
|
* @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
|
|
2382
|
+
* @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.
|
|
2203
2383
|
* @param {*} [options] Override http request options.
|
|
2204
2384
|
*/
|
|
2205
|
-
avaConversionConvertToOenorm(avaProject: ProjectDto, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2385
|
+
avaConversionConvertToOenorm(avaProject: ProjectDto, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2206
2386
|
response: http.IncomingMessage;
|
|
2207
2387
|
body: Buffer;
|
|
2208
2388
|
}>;
|
|
@@ -2353,9 +2533,11 @@ export declare class ExcelConversionApi {
|
|
|
2353
2533
|
* @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.
|
|
2354
2534
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2355
2535
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2536
|
+
* @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.
|
|
2537
|
+
* @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.
|
|
2356
2538
|
* @param {*} [options] Override http request options.
|
|
2357
2539
|
*/
|
|
2358
|
-
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', options?: any): Promise<{
|
|
2540
|
+
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<{
|
|
2359
2541
|
response: http.IncomingMessage;
|
|
2360
2542
|
body: Buffer;
|
|
2361
2543
|
}>;
|
|
@@ -2367,9 +2549,10 @@ export declare class ExcelConversionApi {
|
|
|
2367
2549
|
* @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.
|
|
2368
2550
|
* @param destinationOenormType Defaults to Lv2015
|
|
2369
2551
|
* @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
|
|
2552
|
+
* @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.
|
|
2370
2553
|
* @param {*} [options] Override http request options.
|
|
2371
2554
|
*/
|
|
2372
|
-
excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2555
|
+
excelConversionConvertToOenorm(excelFile: FileParameter, readNewElements?: boolean, rebuildItemNumberSchema?: boolean, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2373
2556
|
response: http.IncomingMessage;
|
|
2374
2557
|
body: Buffer;
|
|
2375
2558
|
}>;
|
|
@@ -2422,9 +2605,11 @@ export declare class GaebConversionApi {
|
|
|
2422
2605
|
* @param gaebFile The input file
|
|
2423
2606
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2424
2607
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2608
|
+
* @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.
|
|
2609
|
+
* @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.
|
|
2425
2610
|
* @param {*} [options] Override http request options.
|
|
2426
2611
|
*/
|
|
2427
|
-
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', options?: any): Promise<{
|
|
2612
|
+
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<{
|
|
2428
2613
|
response: http.IncomingMessage;
|
|
2429
2614
|
body: Buffer;
|
|
2430
2615
|
}>;
|
|
@@ -2434,9 +2619,10 @@ export declare class GaebConversionApi {
|
|
|
2434
2619
|
* @param gaebFile The input file
|
|
2435
2620
|
* @param destinationOenormType Defaults to Lv2015
|
|
2436
2621
|
* @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
|
|
2622
|
+
* @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.
|
|
2437
2623
|
* @param {*} [options] Override http request options.
|
|
2438
2624
|
*/
|
|
2439
|
-
gaebConversionConvertToOenorm(gaebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2625
|
+
gaebConversionConvertToOenorm(gaebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2440
2626
|
response: http.IncomingMessage;
|
|
2441
2627
|
body: Buffer;
|
|
2442
2628
|
}>;
|
|
@@ -2489,9 +2675,11 @@ export declare class OenormConversionApi {
|
|
|
2489
2675
|
* @param oenormFile The input file
|
|
2490
2676
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2491
2677
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2678
|
+
* @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.
|
|
2679
|
+
* @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.
|
|
2492
2680
|
* @param {*} [options] Override http request options.
|
|
2493
2681
|
*/
|
|
2494
|
-
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', options?: any): Promise<{
|
|
2682
|
+
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<{
|
|
2495
2683
|
response: http.IncomingMessage;
|
|
2496
2684
|
body: Buffer;
|
|
2497
2685
|
}>;
|
|
@@ -2501,9 +2689,10 @@ export declare class OenormConversionApi {
|
|
|
2501
2689
|
* @param oenormFile The input file
|
|
2502
2690
|
* @param destinationOenormType Defaults to Lv2015
|
|
2503
2691
|
* @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
|
|
2692
|
+
* @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.
|
|
2504
2693
|
* @param {*} [options] Override http request options.
|
|
2505
2694
|
*/
|
|
2506
|
-
oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2695
|
+
oenormConversionConvertToOenorm(oenormFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2507
2696
|
response: http.IncomingMessage;
|
|
2508
2697
|
body: Buffer;
|
|
2509
2698
|
}>;
|
|
@@ -2556,9 +2745,11 @@ export declare class RebConversionApi {
|
|
|
2556
2745
|
* @param rebFile The input file
|
|
2557
2746
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2558
2747
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2748
|
+
* @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.
|
|
2749
|
+
* @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.
|
|
2559
2750
|
* @param {*} [options] Override http request options.
|
|
2560
2751
|
*/
|
|
2561
|
-
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', options?: any): Promise<{
|
|
2752
|
+
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<{
|
|
2562
2753
|
response: http.IncomingMessage;
|
|
2563
2754
|
body: Buffer;
|
|
2564
2755
|
}>;
|
|
@@ -2568,9 +2759,10 @@ export declare class RebConversionApi {
|
|
|
2568
2759
|
* @param rebFile The input file
|
|
2569
2760
|
* @param destinationOenormType Defaults to Lv2015
|
|
2570
2761
|
* @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
|
|
2762
|
+
* @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.
|
|
2571
2763
|
* @param {*} [options] Override http request options.
|
|
2572
2764
|
*/
|
|
2573
|
-
rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2765
|
+
rebConversionConvertToOenorm(rebFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2574
2766
|
response: http.IncomingMessage;
|
|
2575
2767
|
body: Buffer;
|
|
2576
2768
|
}>;
|
|
@@ -2623,9 +2815,11 @@ export declare class SiaConversionApi {
|
|
|
2623
2815
|
* @param siaFile The input file
|
|
2624
2816
|
* @param destinationGaebType Defaults to GAEB XML V3.2
|
|
2625
2817
|
* @param targetExchangePhaseTransform Defaults to none, meaning no transformation will be done
|
|
2818
|
+
* @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.
|
|
2819
|
+
* @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.
|
|
2626
2820
|
* @param {*} [options] Override http request options.
|
|
2627
2821
|
*/
|
|
2628
|
-
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', options?: any): Promise<{
|
|
2822
|
+
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<{
|
|
2629
2823
|
response: http.IncomingMessage;
|
|
2630
2824
|
body: Buffer;
|
|
2631
2825
|
}>;
|
|
@@ -2635,9 +2829,10 @@ export declare class SiaConversionApi {
|
|
|
2635
2829
|
* @param siaFile The input file
|
|
2636
2830
|
* @param destinationOenormType Defaults to Lv2015
|
|
2637
2831
|
* @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
|
|
2832
|
+
* @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.
|
|
2638
2833
|
* @param {*} [options] Override http request options.
|
|
2639
2834
|
*/
|
|
2640
|
-
siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015', tryRepairProjectStructure?: boolean, options?: any): Promise<{
|
|
2835
|
+
siaConversionConvertToOenorm(siaFile: FileParameter, destinationOenormType?: 'Lv2015' | 'Lb2015' | 'B2063' | 'Lv2009' | 'Lb2009' | 'Lv2021' | 'Lb2021', tryRepairProjectStructure?: boolean, skipTryEnforceSchemaCompliantXmlOutput?: boolean, options?: any): Promise<{
|
|
2641
2836
|
response: http.IncomingMessage;
|
|
2642
2837
|
body: Buffer;
|
|
2643
2838
|
}>;
|