summaryrefslogtreecommitdiffstats
path: root/vid-app-common/src/main/webapp
AgeCommit message (Collapse)AuthorFilesLines
2019-11-05remove comma's properties file with flag ↵Alexey Sandler1-1/+1
FLAG_1911_INSTANTIATION_ORDER_BUTTON_IN_ASYNC_ALACARTE Issue-ID: VID-646 Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com> Change-Id: Idbd37bc2800ca8d38dff7e566654f0677f767a2a
2019-11-04add new flag FLAG_1911_INSTANTIATION_ORDER_BUTTON_IN_ASYNC_ALACARTEAlexey Sandler1-1/+2
Issue-ID: VID-646 Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com> Change-Id: If954d1fb597ecb974b671a05d3f5c5ea5ca9a704
2019-10-25Removed the line break before and after options over UI,Amir Skalka1-3/+1
Added a 'version' field validation over the E2E test. Issue-ID: VID-691 Signed-off-by: Amir Skalka <amir.skalka@intl.att.com> Change-Id: I52205e819a373458c47b8a48239c4bdb309a0bae
2019-10-10fix call AAI get vnf data with right cloudRegion idAlexey Sandler1-2/+2
Issue-ID: VID-596 Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com> Change-Id: I9879657abdc23d91370ed12736d177884963448a
2019-10-10Merge changes from topics "VID-30", "VID-37"Ittay Stern1-1/+1
* changes: Add the "@Override" annotation. Replace "==" with "===".
2019-10-06change management integration with reduce flagSara Weiss1-7/+7
Issue-ID: VID-596 Signed-off-by: Sara Weiss <sara.weiss@intl.att.com> Change-Id: I3b9df53ae4b58b3abe672b3871b75a68fda79fc9 Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
2019-10-02adding orchestration type to service models viewBartosz Gardziejewski5-0/+9
Issue-ID: VID-602 Signed-off-by: Bartosz Gardziejewski <bartosz.gardziejewski@nokia.com> Change-Id: I289b55129cbfe8fbf6dd28f0e8f41715ff4ed107
2019-10-01Replace "==" with "===".anushadasari1-1/+1
The == and != operators do type coercion before comparing values. This is bad because it can mask type errors. For example, it evaluates ' \t\r\n' == 0 as true. It is best to always use the side-effect-less === and !== operators instead. Issue-ID: VID-656 Change-Id: If93fe032fae618bb0bd7112c24a0e4d3acab6337 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-25change management integration with reduce flagSara Weiss2-7/+7
Issue-ID: VID-596 Signed-off-by: Sara Weiss <sara.weiss@intl.att.com> Change-Id: I81155ff877016995ef977358d3bf9fddf75a18ce
2019-09-24Add a semicolon at the end of this statement.anushadasari1-4/+4
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I27deafe5e97d71be4b5b6501f3cda0a19769123b Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-2/+2
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Ibf05db5e76be01c78cfac8196fcf4bb09dfa7709 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-3/+3
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Id3fd3e7baea856e8aab4c5c7c509a6c00bb44ced Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-2/+2
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I45637083e88ac2e1c4cb27519a3116f2f5f792e8 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-11/+11
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I2adee2c4d945cde39d796106fa6540d875b25219 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-2/+2
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line Issue-ID: VID-607 Change-Id: I6798e2fbf4439e5336e1af734aa762449454f04f Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-2/+2
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I74a97be12bc5a110c4afd7f2d3eaf51b0ae707c8 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari2-3/+3
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line Issue-ID: VID-607 Change-Id: I351d26cab21fffe5925dd6bc64691166e5c3ea3d Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24Add a semicolon at the end of this statement.anushadasari1-2/+2
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I1fd965413585256c09e61c2a19b0651800e65eab Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-24change management new filter testsSara Weiss3-15/+31
Issue-ID: VID-596 Change-Id: I591da151bb27a46c217edec552e7c9c670a96aaa Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
2019-09-23add 'cloud region' optional field to change managementSara Weiss4-20/+69
Issue-ID: VID-596 Change-Id: Ieb89980f7e802fe2508950a0e1a23188145fd85e Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
2019-09-23Change-management: provide and use scheduler's fields through ↵Ittay Stern3-21/+60
vm.scheduleWorkflow() In addition, show error message when no Portal-frame. Use the dumped data to revive ChangeManagementTest tests by capturing the error's payload. Issue-ID: VID-397 Change-Id: I978bf537c43b0e3933e82c761c60cd067ab2cf27 Signed-off-by: Ittay Stern <ittay.stern@att.com>
2019-09-19Merge "Disable homing_solution"6.0.0Ittay Stern2-1/+2
2019-09-19Disable homing_solutionwsliwka2-1/+2
Send Homing_solution=none during macro instantiation Add flag 'FLAG_DISABLE_HOMING' (by default set to true) which defines whether homing_solution should be in request to so or not Issue-ID: VID-576 Signed-off-by: wsliwka <wojciech.sliwka@nokia.com> Change-Id: I6151151a0256a5bb4e637acf08ae511f4b265dc2 Signed-off-by: wsliwka <wojciech.sliwka@nokia.com>
2019-09-18add new flag FLAG_1911_INSTANTIATION_ORDER_IN_ASYNC_ALACARTEEylon Malin1-0/+1
Issue-ID: VID-646 Signed-off-by: Eylon Malin <eylon.malin@intl.att.com> Change-Id: I533221a6115c4a2d00ce3ed02eef4d1ad882df3a
2019-09-15change operational-environment-type on operational-environments queryEylon Malin1-1/+1
Issue-ID: VID-637 Signed-off-by: Eylon Malin <eylon.malin@intl.att.com> Change-Id: Ia9340269dd6a4a6616a6fdbfe166eea0731490de
2019-09-12Merge "Reduce vnf data response from A&AI in change management flows"Ittay Stern1-1/+2
2019-09-12Reduce vnf data response from A&AI in change management flowsas221v1-1/+2
Issue-ID: VID-596 Signed-off-by: Amir Skalka <as221v@intl.att.com> Change-Id: I4462ef0c2dbc9880d1a0d204f6552e3842aad821 Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com>
2019-09-12add button to menual search of vnf change the vnf role to free text optionalSara Weiss5-282/+456
Issue-ID: VID-378 Signed-off-by: Sara Weiss <sara.weiss@intl.att.com> Change-Id: I21a4b541f32626823d84f9d0d6fb0392275b7428 Signed-off-by: Sara Weiss <sara.weiss@intl.att.com>
2019-09-12add Feature Flag for cloud-region and nf-role as an optional searchAlexey Sandler1-0/+1
Issue-ID: VID-596 Signed-off-by: Alexey Sandler <alexey.sandler@intl.att.com> Change-Id: I36e5ea4842816dfa8a6734299bf667150600a375
2019-09-10Merge "Semicolon at the end of the Statement and Remove trailing whitespaces ↵Ittay Stern1-4/+2
at the end of this line"
2019-09-10Merge "Semicolon at the end of the Statement and Remove trailing whitespaces ↵Ittay Stern1-3/+2
at the end of this line"
2019-09-10Merge "Semicolon at the end of the Statement and Remove trailing whitespaces ↵Ittay Stern1-10/+8
at the end of this line"
2019-09-10Merge changes from topics "VID-14", "VID-13", "VID-12"Ittay Stern3-22/+22
* changes: Add Semicolon at the end Add Semicolon at the end Add Semicolon ath the end
2019-09-10Semicolon at the end of the Statement and Remove trailing whitespaces at the ↵anushadasari1-10/+8
end of this line In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-606 Change-Id: Ic6daf9162504a2296a7e2cf48f08e60cabe14b21 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-10Semicolon at the end of the Statement and Remove trailing whitespaces at the ↵anushadasari1-4/+2
end of this line In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-606 Change-Id: Ib1484f91b4b47457c4150b536d420ffc1e6902b4 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-10Semicolon at the end of the Statement and Remove trailing whitespaces at the ↵anushadasari1-3/+2
end of this line In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-604 Change-Id: I850ee4d00e2f263105a15a5778c11cfb2e526986 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-10Merge changes from topics "VID-11", "VID-10", "VID-9"Ittay Stern3-5/+5
* changes: Add Semicolon at the end Add Semicolon at the end Add Semicolon at the end
2019-09-10Merge "Semicolon at the end of the Statement and Remove trailing whitespaces ↵Ittay Stern1-6/+4
at the end of this line"
2019-09-10Add flag flag_flash_more_actions_button_in_old_view_editIttay Stern2-2/+2
Renamed from FLAG_FLASH_VIEW_IN_NEW_VIEWEDIT_SCREEN. Added features.properties.md to document the different flags. Change-Id: I819a31851eab8bed54f807f0ffb5082496677d3f Issue-ID: VID-603 Signed-off-by: Ittay Stern <ittay.stern@att.com>
2019-09-09Adding feature: Replace vfmoduleEinat Vinouze3-3/+14
Issue-ID: VID-603 Change-Id: I59068a0979d6fb733e4243c8f78921f396dc9d17 Signed-off-by: Einat Vinouze <einat.vinouze@intl.att.com> Signed-off-by: Amichai Hemli <amichai.hemli@intl.att.com> Signed-off-by: Ittay Stern <ittay.stern@att.com>
2019-09-06Add Semicolon at the endanushadasari1-1/+1
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Ic75affcf10f990fa507eaf738a360df603a700dc Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-06Add Semicolon at the endanushadasari1-20/+20
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I40df40c69bf7de18eeafbf640b4ebe1d0efe6def Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-06Add Semicolon ath the endanushadasari1-1/+1
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I9ca9d0f3c935efe83859b4d623939adce0a38465 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-05Add Semicolon at the endanushadasari1-3/+3
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I53b2e7a540b88b3e04d9169670d1fc6b4a32c6e8 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-05Add Semicolon at the endanushadasari1-1/+1
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Icdfa98d7f67fbf3b21cba97b0013f0181ed34675 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-05Add Semicolon at the endanushadasari1-1/+1
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each lin Issue-ID: VID-607 Change-Id: Ibde377c9a1f4fe473d8f2c0542657888cfbd44c5 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-05Semicolon at the end of the Statement and Remove trailing whitespaces at the ↵anushadasari1-6/+4
end of this line In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-606 Change-Id: If88beef4fa028d01eda5119dfa5bc005d8225e17 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-04Merge changes from topics "VID-8", "VID-7"Ittay Stern2-7/+7
* changes: Add semicolon at the end Add a semicolon at the end of this statement
2019-09-04Add semicolon at the endanushadasari1-4/+4
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Ief3162f9990689251c7268c515107a34b1a03a52 Signed-off-by: anushadasari <danush10@in.ibm.com>
2019-09-04Add a semicolon at the end of this statementanushadasari1-3/+3
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I92d5834ace5659334bdede1dfc2af23cc697f78a Signed-off-by: anushadasari <danush10@in.ibm.com>