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
+
1
18
# Custom Function Reference
2
19
3
20
## 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.
22
39
```
23
40
If IDR node ` tracking_number_h002_cn ` value is ` "" ` and ` tracking_number_h001 ` value is ` "ABC" ` ,
24
41
then the result field ` tracking_number ` value is ` "ABC" ` .
42
+
25
43
---
26
44
27
45
> ### concat
@@ -44,6 +62,7 @@ returned.
44
62
```
45
63
If IDR node ` event_date ` value is ` "12/31/2020" ` and ` event_time ` value is ` "12:34:56" ` ,
46
64
then the result field ` event_date_time ` value is ` "12/31/2020T12:34:56" ` .
65
+
47
66
---
48
67
49
68
> ### dateTimeLayoutToRFC3339
@@ -83,6 +102,7 @@ or the parsed input datetime will be converted into the `toTZ`.
83
102
If you're not sure, please check
84
103
[ this sample] ( ../extensions/omniv21/samples/xml/1_datetime_parse_and_format.schema.json ) to find out
85
104
more subtleties about date time parsing and conversion.
105
+
86
106
---
87
107
88
108
> ### dateTimeToEpoch
@@ -136,6 +156,7 @@ instead tries to parse the input datetime string intelligently.
136
156
If you're not sure, please check
137
157
[ this sample] ( ../extensions/omniv21/samples/xml/1_datetime_parse_and_format.schema.json ) to find out
138
158
more subtleties about date time parsing and conversion.
159
+
139
160
---
140
161
141
162
> ### epochToDateTimeRFC3339
@@ -165,6 +186,7 @@ Param `unit` has two valid values: `"SECOND"` or `"MILLISECOND"`.
165
186
There is an optional param at the end, ` tz ` : if not specified, the output will be in UTC (` Z ` )
166
187
time zone; if specified, it must be of a standard IANA time zone string, such as
167
188
` "America/Los_Angeles" ` .
189
+
168
190
---
169
191
170
192
> ### lower
@@ -276,6 +298,7 @@ book prices.
276
298
277
299
For more information about ` javascript ` , check this
278
300
[ in-depth explanation] ( ./use_of_custom_funcs.md#javascript-and-javascript_with_context ) .
301
+
279
302
---
280
303
281
304
> ### javascript_with_context
@@ -298,4 +321,5 @@ the current IDR node.
298
321
299
322
For more information about ` javascript_with_context ` , check this
300
323
[ in-depth explanation] ( ./use_of_custom_funcs.md#javascript-and-javascript_with_context ) .
324
+
301
325
---
0 commit comments