1+ * [ Custom Function Reference] ( #custom-function-reference )
2+ * [ Global custom\_ func Available to All Extensions and Versions of Schema Handlers] ( #global-custom_func-available-to-all-extensions-and-versions-of-schema-handlers )
3+ * [ coalesce] ( #coalesce )
4+ * [ concat] ( #concat )
5+ * [ dateTimeLayoutToRFC3339] ( #datetimelayouttorfc3339 )
6+ * [ dateTimeToEpoch] ( #datetimetoepoch )
7+ * [ dateTimeToRFC3339] ( #datetimetorfc3339 )
8+ * [ epochToDateTimeRFC3339] ( #epochtodatetimerfc3339 )
9+ * [ lower] ( #lower )
10+ * [ now] ( #now )
11+ * [ upper] ( #upper )
12+ * [ uuidv3] ( #uuidv3 )
13+ * [ omni\. 2\. 1 Schema Handler Specific custom\_ func] ( #omni21-schema-handler-specific-custom_func )
14+ * [ copy] ( #copy )
15+ * [ javascript] ( #javascript )
16+ * [ javascript\_ with\_ context] ( #javascript_with_context )
17+
118# Custom Function Reference
219
320## Global ` custom_func ` Available to All Extensions and Versions of Schema Handlers
@@ -22,6 +39,7 @@ string (with only whitespaces) is not considered as empty.
2239```
2340If IDR node ` tracking_number_h002_cn ` value is ` "" ` and ` tracking_number_h001 ` value is ` "ABC" ` ,
2441then the result field ` tracking_number ` value is ` "ABC" ` .
42+
2543---
2644
2745> ### concat
@@ -44,6 +62,7 @@ returned.
4462```
4563If IDR node ` event_date ` value is ` "12/31/2020" ` and ` event_time ` value is ` "12:34:56" ` ,
4664then the result field ` event_date_time ` value is ` "12/31/2020T12:34:56" ` .
65+
4766---
4867
4968> ### dateTimeLayoutToRFC3339
@@ -83,6 +102,7 @@ or the parsed input datetime will be converted into the `toTZ`.
83102If you're not sure, please check
84103[ this sample] ( ../extensions/omniv21/samples/xml/1_datetime_parse_and_format.schema.json ) to find out
85104more subtleties about date time parsing and conversion.
105+
86106---
87107
88108> ### dateTimeToEpoch
@@ -136,6 +156,7 @@ instead tries to parse the input datetime string intelligently.
136156If you're not sure, please check
137157[ this sample] ( ../extensions/omniv21/samples/xml/1_datetime_parse_and_format.schema.json ) to find out
138158more subtleties about date time parsing and conversion.
159+
139160---
140161
141162> ### epochToDateTimeRFC3339
@@ -165,6 +186,7 @@ Param `unit` has two valid values: `"SECOND"` or `"MILLISECOND"`.
165186There is an optional param at the end, ` tz ` : if not specified, the output will be in UTC (` Z ` )
166187time zone; if specified, it must be of a standard IANA time zone string, such as
167188` "America/Los_Angeles" ` .
189+
168190---
169191
170192> ### lower
@@ -276,6 +298,7 @@ book prices.
276298
277299For more information about ` javascript ` , check this
278300[ in-depth explanation] ( ./use_of_custom_funcs.md#javascript-and-javascript_with_context ) .
301+
279302---
280303
281304> ### javascript_with_context
@@ -298,4 +321,5 @@ the current IDR node.
298321
299322For more information about ` javascript_with_context ` , check this
300323[ in-depth explanation] ( ./use_of_custom_funcs.md#javascript-and-javascript_with_context ) .
324+
301325---
0 commit comments