Siebel CRM Siebel Mobile Guide: Disconnected Siebel Innovation Pack 2017, Rev. A E52427-01 |
|
![]() Previous |
![]() Next |
View PDF |
The following topics are included in this section:
Note: Description values specified in this section do not contain the double quotes around the value |
Table 13-3 shows the type conversion mappings for phone.
Table 13-3 Type Conversion Mappings for Phone
Siebel Phone Type LOV | CardDAV Client | Display Label | vCard TEL/VOICE Type |
---|---|---|---|
Home |
iOS |
home |
TEL;type=HOME;type=VOICE |
Android |
Home |
TEL;type=HOME;type=VOICE |
|
Business |
iOS |
work |
TEL;type=WORK;type=VOICE |
Android |
Work |
TEL;type=WORK;type=VOICE |
|
Other |
iOS |
other |
TEL;type=OTHER;type=VOICE |
Android |
Other |
TEL, or if it is a primary at Siebel then: TEL;type=OTHER;type=VOICE;type=pref |
|
Cell |
iOS |
mobile |
TEL;type=CELL;type=VOICE |
Android |
Mobile |
TEL;type=CELL;type=VOICE |
|
Cell with Description = "type=IPHONE" |
iOS |
iPhone |
TEL;type=IPHONE;type=CELL;type=VOICE |
Android |
Custom label as iPhone |
TEL;type=IPHONE;type=CELL;type=VOICE |
|
Main |
iOS |
main |
TEL;type=MAIN |
Android |
Main |
TEL;type=MAIN, supported only for download synchronization. There is no upload synchronization support.The vCard line sent becomes Tel;Type=VOICE;TYPE=PREF, and will be converted to Other type on the server. |
|
Pager 1 |
iOS |
pager |
TEL;type=PAGER |
Android |
Pager |
TEL;type=PAGER |
|
Personal |
iOS and Android |
Custom label as Personal |
<group>.TEL<group>.X-ABLabel:Personal |
Personal with Description = "MyCustLabel"or the Android's bold predefined labels |
iOS and Android |
Custom label as specified in Description Example: MyCustLabel |
<group>.TEL<group>.X-ABLabel: MyCustLabel |
Android |
Predefined labels:
|
|
|
All other LOV values:
The Work custom type has an uppercase W. Do not confuse this with the iOS's default work type (which has a lowercase w) |
iOS and Android |
Custom label as LovValue |
<group>.TEL <group>.X-ABLabel: <LovValue> |
Table 13-4 shows the type conversion mappings for fax. Note the following:
The iOS and Android CardDAV clients do not support the custom label for the TEL/FAX type. You must convert Personal, Campus, and Dormitory types to the other fax type when downloading data (download synchronization) to CardDAV clients.
After the next data upload (client upload synchronization), any Siebel-side Fax entries of type Personal, Campus, or Dormitory will be updated to Other type implicitly.
Table 13-4 Type Conversion Mappings for Fax
Siebel Fax Type LOV | CardDAV Client | Display Label | vCard TEL/FAX Type |
---|---|---|---|
Home |
iOS |
home fax |
TEL;type=HOME;type=FAX |
Android |
Home Fax |
TEL;type=HOME;type=FAX |
|
Business |
iOS |
work fax |
TEL;type=WORK;type=FAX |
Android |
Work Fax |
TEL;type=WORK;type=FAX |
|
Other |
iOS |
other fax |
TEL;type=OTHER;type=FAX |
Android |
Other Fax |
TEL;type=OTHER;type=FAX |
|
All other LOV Values
|
iOS |
other fax |
TEL;type=OTHER;type=FAX |
Android |
Other fax |
TEL;type=OTHER;type=FAX |
Table 13-5 shows the type conversion mappings for email.
Table 13-5 Type Conversion Mappings for Email
Siebel Email Type LOV | CardDAV Client | Display Label | vCard EMAIL Type |
---|---|---|---|
Home |
iOS |
home |
EMAIL;type=INTERNET;type=HOME |
Android |
Home |
EMAIL;type=INTERNET;type=HOME |
|
Business |
iOS |
work |
EMAIL;type=INTERNET;type=WORK |
Android |
Work |
EMAIL;type=INTERNET;type=WORK |
|
Other |
iOS |
other |
<group>.EMAIL;type=INTERNET<group.X-ABLabel:_$!<Other>!$_ |
Android |
Other |
EMAIL;type=INTERNET |
|
Personal |
iOS and Android |
Custom label as Personal |
<group>.EMAIL;type=INTERNET<group>.X-ABLabel:Personal |
Personal with Description "MyCustLabel" |
iOS and Android |
Custom label as specified in Description Example: MyCustLabel |
<group>.EMAIL;type=INTERNET<group>.X-ABLabel: MyCustLabel |
All other LOV Values
|
iOS and Android |
Custom label as LovValue |
<group>.EMAIL;type=INTERNET <group>.X-ABLabel:<LovValue> |
Table 13-6 shows the type conversion mappings for URL.
Table 13-6 Type Conversion Mappings for URL
Siebel URL Type LOV | CardDAV Client | Display Label | vCard URL Type |
---|---|---|---|
Home |
iOS |
home |
URL;type=HOME |
Android |
Home |
URL;type=HOME |
|
Business |
iOS |
work |
URL;type=WORK |
Android |
Work |
URL;type=WORK |
|
Other |
iOS |
other |
<group>.URL<group.X-ABLabel:_$!<Other>!$_ |
Android |
Other |
URL;type=OTHER |
|
Personal |
iOS and Android |
Custom label as Personal |
<group>.URL<group>.X-ABLabel:Personal |
Personal with Description "MyCustLabel" |
iOS and Android |
Custom label as specified in Description Example: MyCustLabel |
<group>.URL<group>.X-ABLabel: MyCustLabel |
All other LOV Values
|
iOS and Android |
Custom label as LovValue |
<group>.URL<group>.X-ABLabel: <LovValue> |
Table 13-7 shows the type conversion mappings for address. Note the following:
Siebel contact Address types (Mailing Address and Business) not in the CardDAV's default types become the custom label automatically after data download synchronization to the CardDAV client.
An empty address type in Siebel becomes other type in the CardDAV client after data download.
The Siebel contact Address does not have an additional field to hold a custom label. As a result, the ADR entry with custom label will become empty (no value) Address type in Siebel. And the custom label defined in the CardDAV client is cleared or lost after data upload synchronization to Siebel Server. Eventually after data download synchronization, all address custom labels become other type in the CardDAV client.
Table 13-7 Type Conversion Mappings for Address
Siebel Address Type LOV | CardDAV Client | Display Label | vCard ADR Type |
---|---|---|---|
Mailing Address |
iOS |
home |
<group>.ADR;type=HOME<group>.X-ABADR:<CountryCode> |
Android |
Home |
ADR;type=HOME |
|
Business |
iOS |
work |
<group>.ADR;type=WORK<group>.X-ABADR:<CountryCode> |
Android |
Work |
ADR;type=WORK |
|
<empty, no type specified> |
iOS |
other |
<group>.ADR;type=OTHER<group>.X-ABADR:<CountryCode> |
Android |
Other |
ADR |
|
All other LOV Values
|
iOS and Android |
Custom label as LovValue |
<group>.ADR<group>.X-ABLabel:LovValueiOS Only: <group>.X-ABADR:<CountryCode> |