Namespace: SuperOffice.WebApi.Data
Assembly: SuperOffice.WebApi.dllCarrier object for TicketCategoryEntity.
This entity describes the meta data for a ticket category, and provides special operations on it.
Get TicketCategoryEntity 123 using the WebApi client:
<pre><code class=“lang-csharp”>var configuration = new WebApiConfiguration(url);
var agent = new ListAgent(configuration);
var ticketCategoryEntity = agent.GetTicketCategoryEntity( 123 );</code></pre>
Udef + Extra fields added to the carrier. Extra fields as defined by changes to database schema + user-defined fields as defined by admin.
Custom fields combines user defined fields and extra fields into one bucket.
The individual <xref href=“SuperOffice.WebApi.Data.TicketCategoryEntity.ExtraFields” data-throw-if-not-resolved=“false”></xref> and UserDefinedFields properties are deprecated in favor of this
combined collection.
The value string is the encoded value: “[I:123]” or “[DT:2019-09-11]”.
public virtual StringDictionary CustomFields { get; set; }
The naming convention of the key string is as follows:
<table><tbody><tr><td class=“term”>Extra field data</td><td class=“description”>
[Extra field name]<p></p>
Example: <pre><code class=“lang-csharp”>‘x_gorp’ = ‘[I:123]’</code></pre>
</td></tr><tr><td class=“term”>User defined field data</td><td class=“description”>
[Prog-id name]<p></p>
Example: <pre><code class=“lang-csharp”>‘SuperOffice:1’ = ‘[I:123]’</code></pre><p></p>
</td></tr></tbody></table>
Id of reply template to merge into messages, whose ticket belongs to this category. Also takes into account ‘Apply to subcategories’ on parent categories. This is a calculated, readonly field.
public virtual int EffectiveReplyTemplateId { get; set; }
Deprecated: Use <xref href=“SuperOffice.WebApi.Data.TicketCategoryEntity.CustomFields” data-throw-if-not-resolved=“false”></xref> instead.
Extra fields added to the carrier. This could be data from Plug-ins, the foreign key system, external applications, etc.
The value string is the encoded value: “[I:123]” or “[DT:2019-09-11]”.
public virtual StringDictionary ExtraFields { get; set; }
The naming convention of the key string is as follows:
<table><tbody><tr><td class=“term”>Plug-in data</td><td class=“description”>
[Plug-in name].[Property name]
Example: DocumentPlugin.DocumentType
</td></tr><tr><td class=“term”>Foreign key data</td><td class=“description”>
The device identity is appended directly to the device name if it exists.
This is not commonly used, but the database opens for this as a possibility to have several devices with the same name,
and hence we would ensure an unique key if this field is used.
Example: Audience.SecretService.DefaultCountry
</td></tr><tr><td class=“term”>User defined table data</td><td class=“description”>
[Table name].[Field name]
Example: Phunneling.AggregatedSales
</td></tr><tr><td class=“term”>Other</td><td class=“description”>
Other data sources must ensure an unique name. If the key already exists we do not add the data to the dictionary.
We also ensure that SuperOffice data are added first, so that existing data doesnt change when more data sources are added (with duplicate data keys).
</td></tr></tbody></table>