UG information about parameters

[zzhikai]

Nowhere in the UG was it clearly mentioned that phone number has the conditions as stated in the error message below. Though a small matter.
You can include a parameter summary table at the top of the features section to allow the readers to know the constraints of each parameter better instead of only finding out when using the product.(eg. PHONE_NUMBER : "message stated in error message below")
This will also aid long term users, where they can just check the summary table at a glance while using to ensure their commands are correct.

[soc-se-bot]

Team's Response

Specifying all the constraints in the UserGuide would be very technical and might be overbearing to users. Too much technical information in the UserGuide might turn off users and confuse them instead. The constraints imposed is to protect users from erroneous input, and not meant to limit them. Hence, we feel that it is not necessary to include it in the UserGuide.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: [replace this with your explanation]

---