Triggering Reaction - Revision history

Jpritcha at 17:49, 16 July 2010

2010-07-16T17:49:27Z

Gityerfix at 19:03, 26 July 2008

2008-07-26T19:03:15Z

Gityerfix at 05:26, 26 July 2008

2008-07-26T05:26:36Z

Gityerfix at 21:59, 25 July 2008

2008-07-25T21:59:08Z

Gityerfix at 21:56, 25 July 2008

2008-07-25T21:56:20Z

Gityerfix at 14:05, 18 July 2008

2008-07-18T14:05:53Z

Gityerfix at 17:16, 30 June 2008

2008-06-30T17:16:32Z

Gityerfix at 17:06, 30 June 2008

2008-06-30T17:06:06Z

Gityerfix: New page: This article details basic functionality of
--Article provided by Nero Le Velu. Lets assume we have already added a site-defined trigger to cal...

2008-06-30T16:33:05Z

New page: This article details basic functionality of --Article provided by Nero Le Velu. Lets assume we have already added a site-defined trigger to cal...

New page

This article details basic functionality of
 
--Article provided by [[User:Nero Le Velu|Nero Le Velu]].

Lets assume we have already added a site-defined trigger to call zMyScript and pass the Assignee value.

'''Example:'''<source lang="javascript">POST_VALIDATE zMyScript(assignee) 111 FILTER(EVENT("UPDATE"));</source>Lets focus only on the zMyScript(assignee) portion.

Three items of information regarding the assignee are passed from the trigger to the script. 
<nowiki>[1]</nowiki> is the original state value before editing began. 
<nowiki>[2]</nowiki> is the last known value when the trigger was initiated. 
<nowiki>[3]</nowiki> is the new value that is expected to be saved. 

We can then query item <nowiki>[1]</nowiki>, <nowiki>[2]</nowiki>, or <nowiki>[3]</nowiki> in our script as needed.

'''Example:'''
<source lang="javascript">cr::zMyScript(...){
if( is_null( argv[3]){
set_error( 1);
set_return_data( "Assignee need to be filled.");
};
};</source>

----
<div align='center'>To make corrections or additions to this article, select the ''edit'' tab above. 
To discuss or ask questions about this article, select the ''discussion'' tab above.</div>

@@ Line 1: / Line 1: @@
 __NOTOC__
-<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+{{Global Header}}
-To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>
+{{Global Announcement}}
 == Overview ==

@@ Line 5: / Line 5: @@
 == Overview ==
 This article shows how items passed through a trigger can be queried from the script.
 == Details ==
 Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.
 '''Example:'''<source lang="javascript">POST_VALIDATE zMyScript(assignee) 111 FILTER(EVENT("UPDATE"));</source>Lets focus only on the zMyScript(assignee) portion.
@@ Line 19: / Line 17: @@
 We can then query item <nowiki>[1]</nowiki>, <nowiki>[2]</nowiki>, or <nowiki>[3]</nowiki> in our script as needed.
 '''Example:'''

← Older revision		Revision as of 21:59, 25 July 2008
Line 7:		Line 7:


−	== ~~Description~~ ==	+	== Details ==
	Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.		Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.

@@ Line 1: / Line 1: @@
 This article shows how items passed through a trigger can be queried from the script.
 Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.
 '''Example:'''<source lang="javascript">POST_VALIDATE zMyScript(assignee) 111 FILTER(EVENT("UPDATE"));</source>Lets focus only on the zMyScript(assignee) portion.
 Three items of information regarding the assignee are passed from the trigger to the script.<br>
@@ Line 12: / Line 17: @@
 <nowiki>[2]</nowiki> is the last known value when the trigger was initiated.<br>
 <nowiki>[3]</nowiki> is the new value that is expected to be saved.<br>
 We can then query item <nowiki>[1]</nowiki>, <nowiki>[2]</nowiki>, or <nowiki>[3]</nowiki> in our script as needed.
@@ Line 24: / Line 28: @@
      };
    };</source>

@@ Line 1: / Line 1: @@
 This article shows how items passed through a trigger can be queried from the script.
 <br>
 Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.
@@ Line 29: / Line 27: @@
 ----
-<div align='center'><font color="red">To make corrections or additions to this article, select the ''edit'' tab above.<br>
+<div align='center'><font color="green">To make corrections or additions to this article, select the ''edit'' tab above.<br>
 To discuss or ask questions about this article, select the ''discussion'' tab above.</font></div>

@@ Line 22: / Line 22: @@
    if( is_null( argv[3]){
      set_error( 1);
-     set_return_data( "Assignee need to be filled.");
+     set_return_data( "Assignee needs to be filled.");
      };
    };</source>

← Older revision		Revision as of 17:16, 30 June 2008
Line 4:		Line 4:


−	Lets assume we have already added a ~~site~~-~~defined trigger~~ to call zMyScript and pass the Assignee value.	+	Lets assume we have already added a [[Site-Defined Trigger]] to call zMyScript and pass the Assignee value.