Show/Hide Toolbars

Therefore Programming Interface 3.0

Therefore API > What's New

What's new in Thereforeâ„¢ 2019

Scroll

 

New feature: Calculated Fields

TheCategoryField support field value calculations. If a field has a Formula, it can't be set directly but its values is set by executing CalculateFields on a TheIndexData object. If a specific field value is calculated, a recursive chain reaction is triggered that calculates all other field values this field has part of its Formula.

The returned TheFieldCalculationResult contains a list of all field values that have been calculated, the calculated value and information about errors. The index data values in the TheIndexData object are updated automatically.

When saving index data, the server will always calculate field values, independent from if the client already calculated all values or not.

 

All fields used in a Formula can be get by TheCategory.GetCalculationTriggerFields for categories and TheCaseDefinition.GetCalculationTriggerFields for case definitions.

 

New feature: Conditional Formatting

Similar to calculated fields, TheCategoryField supports conditional formatting that allows a change of the visual appearance of fields in the index data dialog. For conditional formatting a Condition has to be set as well as some visual properties, the ConditionalFormatting.

By executing EvaluateConditionalFormatting on a TheIndexData object, the ConditionalFormatting properties of all fields according to the Condition are returned.

 

All fields used in a Condition can be get by TheCategory.GetFormattingTriggerFields for categories and TheCaseDefinition.GetFormattingTriggerFields for case definitions.

 

New feature: Field IDs

In the UI of the Solution Designer, the FieldID takes the place of the Column Name. They have to be unique per category or case definition, cannot be changed and does not change when importing into a different system, other than the IndexDataFieldName, which is composed of "TWF" followed by the FieldNo for fields with no ColName. This makes the FieldID replace the IndexDataFieldName in the API.

Other than column names, field IDs apply to every field, even if the field has no column in the related index data table in the database.

 

The FieldID can be used for Formulas of field calculations and Conditions for conditional formatting of fields.

 

 

New Classes

TheConditionalFormatting

TheConditionalFormattingList

TheConditionalFormattingResult

TheConditionalFormattingResultList

TheFieldCalculationResult

TheFieldCalculationResultItem

 

New Properties

TheCategoryField.Condition

TheCategoryField.ConditionalFormatting

TheCategoryField.FieldID

TheCategoryField.Formula

TheCategoryField.ValidDefaultMacros

 

TheDependentFieldsQueryResult.AllRowsReturned

TheServer.CustomerId

TheTask.CaseNo

 

New Methods

TheCaseDefinition.GetFieldByFieldID

TheCaseDefinition.GetCalculationTriggerFields

TheCaseDefinition.GetFormattingTriggerFields

 

TheCategory.GetFieldByFieldID

TheCategory.GetCalculationTriggerFields

TheCategory.GetFormattingTriggerFields

 

TheCategoryField.ChangeDependencyMode

TheCategoryField.GetValidDefaultMacros

TheCategoryField.SetCondition

TheCategoryField.SetFormula

 

TheIndexData.CalculateFields

TheIndexData.EvaluateConditionalFormatting

TheIndexData.GetValueByFieldID

TheIndexData.SetValueByFieldID

 

ThePDFPrinter.SetDefaultPrinter

 

TheServer.ConnectBearerToken

TheServer.GetKeywordsByKeyDic

TheServer.GetTokenForCurrentUser

TheServer.QueryDependentFieldsDirect

TheServer.SetParentFolder

 

TheWFInstance.Load (new overload)

TheWFInstance.LoadWorkflowHistory

 

TheUser.SetPassword

 

© 2022 Therefore Corporation, all rights reserved.