Recent changes to Script Syntax

Script Syntax modified by Giles Lewis

Giles Lewis — Tue, 24 Sep 2013 16:25:00 -0000

--- v18
+++ v19
@@ -32,6 +32,7 @@

 In addition, a minus or/or plus clause can be appended to a datetime. The syntax is as follows:

+    :::text
      [ minus  { days | hours | minutes | seconds } ]
                [ plus   { days | hours | minutes | seconds } ] 

@@ -51,6 +52,7 @@

 ### Syntax

+    :::text
     load  [ into   ] [ use-keys | no-keys ] [ truncate ]
         [ insert-only | update-insert | compare-timestamps ]
         [ [ created | updated ] from   [ to   ] ] 
@@ -122,6 +124,7 @@

 ### Syntax

+    :::text
     refresh  [ into  ] 
         since  
         [ where "{"  "}" ] 
@@ -130,10 +133,12 @@

 Note that this refresh command:

+    :::text
     refresh change_request since today

 performs exactly the same function as this load command:

+    :::text
     load change_request updated from today to now

 ## refresh every
@@ -144,6 +149,7 @@

 ### Syntax

+    :::text
     refresh  [ into  ] 
         [ since  ] 
         every  { seconds | minutes | hours } 
@@ -189,6 +195,7 @@

 ### Syntax

+    :::text
     prune  [ into  ] since 

 ### Examples
@@ -201,12 +208,14 @@

 ### Syntax

+    :::text
     prune  [ into  ] 
         [ since   ]
         every  { seconds | minutes | hours } 

 ### Examples

+    :::text
     prune change_task into upcoming_change_task every 60 minutes

 ## sql
@@ -215,6 +224,7 @@

 ### Syntax

+    :::text
     sql "{"  "}" 

 ### Examples

Script Syntax modified by Giles Lewis

Giles Lewis — Thu, 08 Aug 2013 14:06:24 -0000

--- v17
+++ v18
@@ -159,7 +159,7 @@

 ### since

-Used to specify a starting date/time for the initial query. The datetime may specified using the format yyyy-mm-dd hh:mm:ss or using the keyword today or now.   All dates must be specified in GMT. The keyword today will be interpreted as midnight GMT.
+Used to specify a starting date/time for the initial query. The datetime may specified using the format yyyy-mm-dd hh:mm:ss or using the keyword today or now. If not specified then the default is now.  All dates must be specified in GMT. The keyword today will be interpreted as midnight GMT.

 ### where

Script Syntax modified by Giles Lewis

Giles Lewis — Mon, 20 May 2013 15:45:26 -0000

--- v16
+++ v17
@@ -15,8 +15,8 @@
 | Syntax | Description |
 |--------|-------------|
 | <tablename> | Angled brackets indicate a name or value should be substituted. |
-| [ seconds | minutes | hours ] | Square brackets indicate an optional choice.  One or none of the keyworks may be specified. |
-| { output | append } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
+| [ created | updated ] | Square brackets indicate an optional choice.  One or none of the keyworks may be specified. |
+| { seconds | minutes | hours } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
 | "{" <clause> "}" | Quoted curly brackets indicate that the clause is to be specified between curly brackets. |

Script Syntax modified by Giles Lewis

Giles Lewis — Mon, 20 May 2013 15:39:59 -0000

--- v15
+++ v16
@@ -10,8 +10,7 @@

 ### Syntax Notation

-The following notation is used on this wiki page for the syntax specifications below.
-
+The following notation is used on this page for the syntax specifications below.

 | Syntax | Description |
 |--------|-------------|

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:48:14 -0000

--- v14
+++ v15
@@ -16,7 +16,7 @@
 | Syntax | Description |
 |--------|-------------|
 | <tablename> | Angled brackets indicate a name or value should be substituted. |
-| [ created | updated ] | Square brackets indicate an optional choice.  Either or neither of the keyworks may be specified. |
+| [ seconds | minutes | hours ] | Square brackets indicate an optional choice.  One or none of the keyworks may be specified. |
 | { output | append } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
 | "{" <clause> "}" | Quoted curly brackets indicate that the clause is to be specified between curly brackets. |

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:45:17 -0000

--- v13
+++ v14
@@ -190,7 +190,7 @@

 ### Syntax

-    prune  [ into  ] since  
+    prune  [ into  ] since 

 ### Examples

@@ -203,8 +203,8 @@
 ### Syntax

     prune  [ into  ] 
-        [ since  ]
-        every  { seconds | minutes | hours } 
+        [ since   ]
+        every  { seconds | minutes | hours } 

 ### Examples

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:43:38 -0000

--- v12
+++ v13
@@ -16,8 +16,8 @@
 | Syntax | Description |
 |--------|-------------|
 | <tablename> | Angled brackets indicate a name or value should be substituted. |
-| \[ created \| updated \] | Square brackets indicate an optional choice.  Either or neither of the keyworks may be specified. |
-| { output \| append } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
+| [ created | updated ] | Square brackets indicate an optional choice.  Either or neither of the keyworks may be specified. |
+| { output | append } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
 | "{" <clause> "}" | Quoted curly brackets indicate that the clause is to be specified between curly brackets. |

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:38:08 -0000

--- v11
+++ v12
@@ -7,33 +7,19 @@

     -f 

+
 ### Syntax Notation

 The following notation is used on this wiki page for the syntax specifications below.

-
-
-  
-  
-
-
-  
-  
-
-
-  
-  
-
-
-  
-  
-
-
-  
-  
-
-Syntax Description
<tablename> Angled brackets indicate a name or value should be substituted.
[ created | updated ] Square brackets indicate an optional choice.  Either or neither of the keyworks may be specified.
{ output | append } Curly brackets indicate a andatory choice.  One of the keywords must be specified.
-
"{" <clause> "}" Quoted curly brackets indicate that the clause is to be specified between curly brackets.
+
+| Syntax | Description |
+|--------|-------------|
+| <tablename> | Angled brackets indicate a name or value should be substituted. |
+| \[ created \| updated \] | Square brackets indicate an optional choice.  Either or neither of the keyworks may be specified. |
+| { output \| append } | Curly brackets indicate a mandatory choice.  One of the keywords must be specified. |
+| "{" <clause> "}" | Quoted curly brackets indicate that the clause is to be specified between curly brackets. |
+

 ### DateTime Notation

Syntax	Description
`<tablename>`	Angled brackets indicate a name or value should be substituted.
`[ created \| updated ]`	Square brackets indicate an optional choice. Either or neither of the keyworks may be specified.
`{ output \| append }`	Curly brackets indicate a andatory choice. One of the keywords must be specified. -
`"{" <clause> "}"`	Quoted curly brackets indicate that the clause is to be specified between curly brackets.

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:07:04 -0000

--- v10
+++ v11
@@ -107,28 +107,22 @@

 The following command will load all Linux servers into a SQL table named linux_server. The SQL table will be created if it does not already exist. If it exists and contains data then records from ServiceNow will be inserted and/or updated based on the primary key which is  sys_id.

-~~~~
-load cmdb_ci_linux_server into linux_server
-~~~~
+    load cmdb_ci_linux_server into linux_server

 The following script will load all change_request tickets from the first half of 2012, one month at a time starting with the most recent month.

-~~~~
-load change_request from 2012-06-01 to 2012-07-01
-load change_request from 2012-05-01 to 2012-06-01
-load change_request from 2012-04-01 to 2012-05-01
-load change_request from 2012-03-01 to 2012-04-01
-load change_request from 2012-02-01 to 2012-03-01
-load change_request from 2012-01-01 to 2012-02-01
-~~~~
+    load change_request from 2012-06-01 to 2012-07-01
+    load change_request from 2012-05-01 to 2012-06-01
+    load change_request from 2012-04-01 to 2012-05-01
+    load change_request from 2012-03-01 to 2012-04-01
+    load change_request from 2012-02-01 to 2012-03-01
+    load change_request from 2012-01-01 to 2012-02-01

 The following script will load all records from the tables sys_user, sys_user_group and sys_user_grmember. Existing records in   sys_user and sys_user_group will be updated only if they have changed (based on timestamp). The table sys_user_grmember  will be truncated and reloaded.

-~~~~
-load sys_user compare-timestamps
-load sys_user_group compare-timestamps
-load sys_user_grmember truncate
-~~~~
+    load sys_user compare-timestamps
+    load sys_user_group compare-timestamps
+    load sys_user_grmember truncate

 The following command will load all P1 "Network" incidents  updated in the last seven days through midnight GMT.

@@ -151,15 +145,11 @@

 Note that this refresh command:

-~~~~
-refresh change_request since today
-~~~~
+    refresh change_request since today

 performs exactly the same function as this load command:

-~~~~
-load change_request updated from today to now
-~~~~
+    load change_request updated from today to now

 ## refresh every

@@ -194,23 +184,19 @@

 The following example will load all P1 incidents created or updated since 5:30 PM (GMT) yesterday and then poll the system every 5 minutes for any newly created or updated P1 incidents. The application will continue running until it is killed. 

-~~~~
-load incident from today minus 390 minutes where { priority<2 }
-refresh incident every 5 minutes where { priority<2 }
-~~~~
+    load incident from today minus 390 minutes where { priority<2 }
+    refresh incident every 5 minutes where { priority<2 }

 The following example will load all upcoming change requests and change tasks into the the tables upcoming_change_request and upcoming_change_task respectively and then monitor the system every 10 minutes for any changes. The application will continue running until it is killed. This script will not correctly account for change requests or change tasks which are deleted after it starts running.  For that you need the  prune operation (described below). 

-~~~~
-load    change_request into upcoming_change_request truncate \
-        where { start_date>javascript:gs.daysAgoEnd(0) }
-load    change_task    into upcoming_change_task    truncate \
-        where { request.start_date>javascript:gs.daysAgoEnd(0) }
-refresh change_request into upcoming_change_request every 10 minutes \
-        where { start_date>javascript:gs.daysAgoEnd(0) }
-refresh change_task    into upcoming_change_task    every 10 minutes \
-        where { request.start_date>javascript:gs.daysAgoEnd(0) }
-~~~~
+    load    change_request into upcoming_change_request truncate \
+            where { start_date>javascript:gs.daysAgoEnd(0) }
+    load    change_task    into upcoming_change_task    truncate \
+            where { request.start_date>javascript:gs.daysAgoEnd(0) }
+    refresh change_request into upcoming_change_request every 10 minutes \
+            where { start_date>javascript:gs.daysAgoEnd(0) }
+    refresh change_task    into upcoming_change_task    every 10 minutes \
+            where { request.start_date>javascript:gs.daysAgoEnd(0) }

 ## prune

@@ -222,9 +208,7 @@

 ### Examples

-~~~~
-prune change_task into upcoming_change_task since 2013-01-01
-~~~~
+    prune change_task into upcoming_change_task since 2013-01-01

 ## prune every

@@ -232,15 +216,13 @@

 ### Syntax

-    prune  [ into ] 
-        [ since  ] 
+    prune  [ into  ] 
+        [ since  ]
         every  { seconds | minutes | hours } 

 ### Examples

-~~~~
-prune change_task into upcoming_change_task every 60 minutes
-~~~~
+    prune change_task into upcoming_change_task every 60 minutes

 ## sql

@@ -252,40 +234,38 @@

 ### Examples

-~~~~
-sql { truncate table ritm_variable }
-
-
-sql { merge into ritm_variable t \
-using ( \
-select \
-v.sys_id sc_item_option, \
-ritm.sys_id sc_req_item, \
-ritm.number_, \
-vdef.name var_name, \
-v.value var_value, \
-vdef.reference ref_table, \
-vdef.question_text question_text \
-from  \
-sc_req_item ritm,  \
-sc_cat_item item, \
-sc_item_option_mtom iv,  \
-sc_item_option v, \
-item_option_new vdef \
-where ritm.opened_at >= to_date('2012-07-01','yyyy-mm-dd') \
-and item.sys_id = ritm.cat_item \
-and iv.request_item = ritm.sys_id \
-and v.sys_id = iv.sc_item_option \
-and vdef.sys_id = v.item_option_new \
-) s \
-on (s.sc_item_option = t.sc_item_option) \
-when matched then update \
-set t.var_value = s.var_value \
-when not matched then insert ( \
-t.sc_item_option, t.sc_req_item, t.number_, \
-t.var_name, t.var_value, t.ref_table, t.question_text) \
-values ( \
-s.sc_item_option, s.sc_req_item, s.number_, \
-s.var_name, s.var_value, s.ref_table, s.question_text) } 
-~~~~
-
+    sql { truncate table ritm_variable }
+    
+    
+    sql { merge into ritm_variable t \
+    using ( \
+    select \
+    v.sys_id sc_item_option, \
+    ritm.sys_id sc_req_item, \
+    ritm.number_, \
+    vdef.name var_name, \
+    v.value var_value, \
+    vdef.reference ref_table, \
+    vdef.question_text question_text \
+    from  \
+    sc_req_item ritm,  \
+    sc_cat_item item, \
+    sc_item_option_mtom iv,  \
+    sc_item_option v, \
+    item_option_new vdef \
+    where ritm.opened_at >= to_date('2012-07-01','yyyy-mm-dd') \
+    and item.sys_id = ritm.cat_item \
+    and iv.request_item = ritm.sys_id \
+    and v.sys_id = iv.sc_item_option \
+    and vdef.sys_id = v.item_option_new \
+    ) s \
+    on (s.sc_item_option = t.sc_item_option) \
+    when matched then update \
+    set t.var_value = s.var_value \
+    when not matched then insert ( \
+    t.sc_item_option, t.sc_req_item, t.number_, \
+    t.var_name, t.var_value, t.ref_table, t.question_text) \
+    values ( \
+    s.sc_item_option, s.sc_req_item, s.number_, \
+    s.var_name, s.var_value, s.ref_table, s.question_text) } 
+

Script Syntax modified by Giles Lewis

Giles Lewis — Sun, 19 May 2013 20:03:47 -0000

--- v9
+++ v10
@@ -143,10 +143,9 @@

 ### Syntax

-   refresh   [ into  ] 
-           since  
-           [ where "{"  "}" ] 
-
+    refresh  [ into  ] 
+        since  
+        [ where "{"  "}" ] 

 ### Example