NAPA_Xpress

[NXP-682] - Update Sales Order JIA cHANGES
[NXP-682] - Update Sales Order JIA cHANGES
  • More
  • NXP-21
  • submitted for moderator approval
[NXP-681] - JIA Changes for Create PO , Update PO (NXP-388) and Update SO (NXP-683) to TAMS. Also NXP...
[NXP-681] - JIA Changes for Create PO , Update PO (NXP-388) and Update SO (NXP-683) to TAMS. Also NXP...
  • More
  • NXP-20
  • submitted for moderator approval
[NXP-681] - JIA Changes for Create PO , Update PO (NXP-388) and Update SO (NXP-683) to TAMS. Also NXP...
[NXP-681] - JIA Changes for Create PO , Update PO (NXP-388) and Update SO (NXP-683) to TAMS. Also NXP...
  • More
  • NXP-18
  • submitted for moderator approval
[NXP-674], [NXP-675] JIA changes stories committed.
[NXP-674], [NXP-675] JIA changes stories committed.
  • More
  • NXP-17
  • submitted for moderator approval
[NXP-666], [NXP-674], [NXP-675] JIA changes stories committed.
[NXP-666], [NXP-674], [NXP-675] JIA changes stories committed.
  • More
  • NXP-16
  • submitted for moderator approval
  • More
  • NXP-14
  • finished reviewing
Please see, if both of these "if" conditions are making sense here

Please see, if both of these "if" conditions are making sense here

  • More
  • NXP-13
  • finished reviewing
Please add string constants as applicable. (e.g. PART_NUMBER)

Please add string constants as applicable. (e.g. PART_NUMBER)

What is the guarantee of getting these elements (0), (1), (2), if they are as per JIA, please ignore my comment and add a line of comment in the code to explain the same. If not this is a potential...

What is the guarantee of getting these elements (0), (1), (2), if they are as per JIA, please ignore my comment and add a line of comment in the code to explain the same. If not this is a potential NPE place.

There is so much of business logic happening inside the following for loop, which does not use the iterated element "consignmentEntryModel". Please see and revisit, if the value assignments require...

There is so much of business logic happening inside the following for loop, which does not use the iterated element "consignmentEntryModel". Please see and revisit, if the value assignments required to be with-in for loop (e.g. pickedData = listEventIdentifierPickWsDTO.get(2).getFields().getField().get(0).getValue()

for (ConsignmentEntryModel consignmentEntryModel : setConsignmentEntryModel)

  • More
  • NXP-15
  • finished reviewing
Please remove commented code, always can get it from history

Please remove commented code, always can get it from history

Please use individual braces to segregate, if needed use multiple if statements

Please use individual braces to segregate, if needed use multiple if statements

  • More
  • NXP-12
  • finished reviewing
Kindly revisit the logic of looping through elements, too much of if else statements

Kindly revisit the logic of looping through elements, too much of if else statements

  • More
  • NXP-10
  • finished reviewing
Use a string constant at class level

Use a string constant at class level

Please revisit if a dummy method can be introduced to calculate the date from a date returned by mock IC service

Please revisit if a dummy method can be introduced to calculate the date from a date returned by mock IC service

  • More
  • NXP-8
  • finished reviewing
This line will always return null. Kindly revisit the intended logic. Provide required comments

This line will always return null. Kindly revisit the intended logic. Provide required comments

Avoid DTO, use a data bean. Try segregating the DTO from front-end logic

Avoid DTO, use a data bean. Try segregating the DTO from front-end logic

Please change from getModelService().saveAll(); getModelService().save(customerInfo); getModelService().save(cartModel); to getModelService().saveAll(customerInfo, cartModel);

Please change from

getModelService().saveAll();
getModelService().save(customerInfo);
getModelService().save(cartModel);

to

getModelService().saveAll(customerInfo, cartModel);