Overview | Service | Command |
Modify the phone num and label.
NOTE: UI should insert empty values for oldPhone, phone label in-case the user wants to leave them empty.
Authorization token required | true |
Admin Authorization token required | false |
<ModifyFromNumRequest> ## ModifyFromNumRequest
<storeprincipal [id="{id-of-user-in-the-backing-store}"] [name="{name-of-user-in-the-backing-store}"]
[accountNumber="{account-number}"] /> ## StorePrincipalSpec
<phone oldPhone="{old-phone-number}" phone="{new-phone-number}" id="{phone-id}" label="{phone-label}" /> ## ModifyFromNumSpec
</ModifyFromNumRequest>
The following table describes elements and attributes you can define within a
<ModifyFromNumRequest>
element:
XPath | Required / Optional | Description |
/storeprincipal | Optional (0 or 1) | Store Principal specification |
/storeprincipal@id | Optional (0 or 1) | Type:String ID of user in the backing store |
/storeprincipal@name | Optional (0 or 1) | Type:String Name of user in the backing store |
/storeprincipal@accountNumber | Optional (0 or 1) | Type:String Account Number |
/phone | Optional (0 or 1) | Changes for phone |
/phone@oldPhone | Required (only 1) | Type:String Old phone number |
/phone@phone | Required (only 1) | Type:String New phone number |
/phone@id | Required (only 1) | Type:String Phone ID |
/phone@label | Required (only 1) | Type:String Phone label/name |
<ModifyFromNumResponse> ## ModifyFromNumResponse
<phone> ## PhoneName
<name>{name} (String)</name>
</phone>
</ModifyFromNumResponse>
The following table describes elements and attributes you can define within a
<ModifyFromNumResponse>
element:
XPath | Required / Optional | Description |
/phone | Optional (0 or 1) | Phone |
/phone/name | Optional (0 or 1) | Type:{name} (String) Name |