...
| Info |
|---|
Note: SortOrder is supported on some of the imports listed below and they will have the element included in the example where supported. The list is also here: |
Culture
Language
Country
TicketCategory
TicketContactMethod
TicketPriority
TicketGroup
TicketStatus
State
County
City
The element to add into the xml would be this: SortOrder="1" or any number. 0 being default, and 1,2,3, and so on being the orders where the lowest number floats to the top of the dropdown list in EngageIP
...
Name | Name defining contact type | Billing Contact, Admin Contact, Technical Contact |
Owner | Name of the Owner the country belongs to | this will be based on previous import |
BillingContact | Defines whether this contacttype will be used for billing | True or False |
EmailContact | Defines whether this contacttype will be used for emailing system emails | True or False |
ServiceContact | Defines whether this contacttype will be used for service contact requests | True or False |
Required | Defines whether this contact is required to be completed when adding customer accounts | True or False |
...
User Extended Attributes
| Code Block |
|---|
<?xml version="1.0"?>
<UserExtendedAttributes>
<ProfileQuestion DataType="/DataType=Text" Name="UserExtQuestion" Question="UserExtQuestion" Required="False" UniqueAnswer="False" IncludeInInvoiceXML="False" ShowOnViewFilter="False" ReferenceName="pqUserExt1" />
<UserExtendedAttribute Owner="/Owner=Logisense Corporation" ProfileQuestion="@pqUserExt1" />
</UserExtendedAttributes> |
ContactPointType Imports
Owner’s Contact Points related to the Contact Type. These are the contact points available to Contact Types and MUST be well defined.
...
Steps to import translation xml files into EngageIP
locate the language ID from the language table
delete * from translations where languageID = X
use DB migrator to import the xml.
For generic translation xml files be sure to find and replace the owner with the correct owner for import.
...