<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.catglobe.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Huynhhuyphong</id>
	<title>Catglobe Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.catglobe.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Huynhhuyphong"/>
	<link rel="alternate" type="text/html" href="https://wiki.catglobe.com/Special:Contributions/Huynhhuyphong"/>
	<updated>2026-05-28T01:47:16Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.catglobe.com/index.php?title=Email_rules&amp;diff=24322</id>
		<title>Email rules</title>
		<link rel="alternate" type="text/html" href="https://wiki.catglobe.com/index.php?title=Email_rules&amp;diff=24322"/>
		<updated>2012-04-12T08:35:14Z</updated>

		<summary type="html">&lt;p&gt;Huynhhuyphong: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;﻿ &lt;br /&gt;
&lt;br /&gt;
=== Email rules ===&lt;br /&gt;
&lt;br /&gt;
Email rules can be accessed from the accounts dialog. Any email rule must belong to a main account. Accounts can although have multiple rules. &lt;br /&gt;
&lt;br /&gt;
[[Image:8086.png|800px|Emailrules581-1]] &lt;br /&gt;
&lt;br /&gt;
Click add to create a new email rule and edit to modify an existing rule. This will open the following dialogue. &lt;br /&gt;
&lt;br /&gt;
[[Image:8087.png|530px|Emailrules581-2]] &lt;br /&gt;
&lt;br /&gt;
Each rule has some criteria which you can define to specify for which e-mails the rule will apply. And it has some actions to define what will happen to the emails for which the criteria applies. If an incoming e-mail meets the criteria of one rule, the action is applied. &lt;br /&gt;
&lt;br /&gt;
The criteria that exists for selecting e-mails for a rule are; To e-mail, From e-mail, Subject, Message and Header contains. It is only for the To E-mail where an exact match is required. For the other rules the inserted string just needs to be part of the tested e-mail. If e.g. Subject for the rule is &amp;quot;Coca&amp;quot; then all e-mails with &amp;quot;Coca-Cola&amp;quot; in subject will also fulfill this criteria. The Header contains field is for advanced users who know how the hidden &amp;quot;codes&amp;quot; in e-mail headers look. An example of a&amp;amp;nbsp; header criteria could be &amp;quot;x-sender: kiima@ozonic.com&amp;quot; or &amp;quot;X-ExchangeSecure-AntiSpam: spam&amp;quot;. This would mean that all headers containing the&amp;amp;nbsp;keys &amp;quot;x-sender&amp;quot; where value looks like&amp;amp;nbsp;%kiima@ozonic.com% and key &amp;quot;X-ExchangeSecure-AntiSpam&amp;quot; where value looks like&amp;amp;nbsp;%spam% will fulfill this rule. To add multiple rules for &amp;quot;header contains&amp;quot; please place each rule in a separate line in the text box. &lt;br /&gt;
&lt;br /&gt;
In the above dialogue example, if an incoming mail is sent to support@vietnam.catglobe.com and in the Subject field includes the string &amp;quot;[Spam]&amp;quot;, then the e-mail will be moved to the Inbox of the ARCHIVE resource. As you can see we can combine a number of different rules based on whom the e-mail is to, whom an e-mail is from, and what key words are found in the subject and message areas. &lt;br /&gt;
&lt;br /&gt;
Distribution rules offer 6 different types of actions (chosen in the Type dropdown). These are explained in turn below&amp;amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Move:&#039;&#039;&#039; When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be moved to. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Copy:&#039;&#039;&#039; If you want to leave a copy in the original resource, but still want a copy another place, you can use this type. When choosing this type, you will be asked to choose a mailfolder (typically inbox) of another resource to which incoming emails caught by this rule should be copied to. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Forward:&#039;&#039;&#039; If you want the incoming email caught by this rule to be forwarded to another email address, then use this rule. The stated email does not need to exist in the Catglobe system. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Reply:&#039;&#039;&#039; When choosing this type, you will be asked to specify the mail template to be used for the reply email. An email reply will then automatically be returned for any incoming email caught by this rule. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Delete:&#039;&#039;&#039; When you choose this type, any email caught will immediately get deleted. Good way to handle spammail. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Execute CGScript:&#039;&#039;&#039; This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot; width=&amp;quot;875&amp;quot; style=&amp;quot;border-collapse:collapse; border:1px solid #010101&amp;quot; class=&amp;quot;tableintopic&amp;quot;&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Index&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Data type&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Value&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_FROM&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The sender&#039;s email address&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_TO_RESOURCE_ID&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;Number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The resource ID of the resource to which the email is delivered&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_TO_ADDRESSES&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The recipients&#039; email addresses, including Cc recipients&#039;.&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_HEADERS&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The headers of the email&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_SUBJECT&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The subject of the email&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;EMAIL_CONTENT&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The content of the email&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example : &#039;&#039;&#039; On the workflow using for adding the journal basing on the email content : &lt;br /&gt;
&lt;br /&gt;
array emailparameter=Workflow_getParameters();  &lt;br /&gt;
&lt;br /&gt;
string fromemail = emailparameter[EMAIL_FROM];&lt;br /&gt;
&lt;br /&gt;
number parentResourceId = emailparameter[EMAIL_TO_RESOURCE_ID];&lt;br /&gt;
&lt;br /&gt;
string toemail = emailparameter[EMAIL_TO_ADDRESSES];&lt;br /&gt;
&lt;br /&gt;
string headeremail = emailparameter[EMAIL_HEADERS];&lt;br /&gt;
&lt;br /&gt;
string headeremail = emailparameter[EMAIL_SUBJECT];&lt;br /&gt;
&lt;br /&gt;
string contentemail = emailparameter[EMAIL_CONTENT];&lt;br /&gt;
&lt;br /&gt;
addJournal(197653,6, &amp;quot;Comment&amp;quot;,convertToString(emailparameter)); &lt;br /&gt;
&lt;br /&gt;
[[Category:Accounts]]&lt;/div&gt;</summary>
		<author><name>Huynhhuyphong</name></author>
	</entry>
	<entry>
		<id>https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24315</id>
		<title>SMS keywords</title>
		<link rel="alternate" type="text/html" href="https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24315"/>
		<updated>2012-04-12T08:09:22Z</updated>

		<summary type="html">&lt;p&gt;Huynhhuyphong: /* SMS keywords */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;﻿ &lt;br /&gt;
&lt;br /&gt;
== SMS keywords ==&lt;br /&gt;
&lt;br /&gt;
SMS keywords can be inserted into outgoing SMS. The SMS Keyword is the Identification text that will be used by people with mobile phones to send SMS back to us. A message might thus be &amp;quot;If you would like to receive a free newsletter pls send an SMS to 555-5555 with the message &amp;quot;KEYWORD&amp;quot;, where the keyword will depend on the provider they return the SMS to. All the KEYWORD merge-field in reality does is insert a keyword depending on the provider it is sent from instead of the KEYWORD tag. So it is a bit like a merge field. Only this mergefield is essential for anyone that wants to send an SMS to us to place first in the message so the provider knows that it is intended for your site as receiver. Besides this purpose, the keyword is also used as an &amp;quot;distribution rule&amp;quot; that identifies what resource&#039;s SMS inbox will receive the SMS. &lt;br /&gt;
&lt;br /&gt;
If you want to set up a keyword in Catglobe you can access the dialogue for this under the drop down menu of the Communicator SMS list. You will be introduced to a dialog like below. &lt;br /&gt;
&lt;br /&gt;
[[Image:8081.png|419px|SMS581-2]] &lt;br /&gt;
&lt;br /&gt;
When a keyword is added for a resource it means that this keyword is the one that will be merged into any mail sent from this resource for this provider. Thus there can only be one keyword per provider for the same resource. The keyword also has another function though. If the Catglobe site receives an SMS, then it will check if it can identify a keyword in it. If it can, then it will make sure that the incoming SMS is placed in the communicator of the resource that has this keyword registered. The keywords therefore also function as a type of distribution rule. &lt;br /&gt;
&lt;br /&gt;
Allthough you are sending an SMS with keywords from a specific resource it does not necessarily mean that this is the place to which you want its return messages sent. You can specify more distribution rules for SMS using this keyword by using the distribution rules feature of SMS. Activate the distribution rules button by highlighting one of your SMS keywords and click on it. You will then see the following dialog. &lt;br /&gt;
&lt;br /&gt;
[[Image:8082.png|450px|SMS581-3]] &lt;br /&gt;
&lt;br /&gt;
You can add multiple rules for the same keyword. Thus you can e.g. both sent a thank you SMS in return to the sender as well as well as move the SMS to a different resource in the system. &lt;br /&gt;
&lt;br /&gt;
Click create to add a rule. &lt;br /&gt;
&lt;br /&gt;
[[Image:8083.png|219px|SMS581-4]] &lt;br /&gt;
&lt;br /&gt;
At the top of the new SMS distribution rule dialog you can choose between 4 types of rules. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Move:&#039;&#039;&#039; Makes it possible for you to move the entire SMS to a different destination folder (typically the inbox) of a different resource. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Copy:&#039;&#039;&#039; Makes it possible for you to make a copy of the SMS on a different destination folder (typically the inbox) of a different resource. The difference to the move type is that this rule will leave not remove the original copy of the SMS. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Delete:&#039;&#039;&#039; Simply deletes the incoming SMS with the specific keyword. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Execute CGScript:&#039;&#039;&#039; This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project. &lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot; width=&amp;quot;875&amp;quot; style=&amp;quot;border-collapse:collapse; border:1px solid #010101&amp;quot; class=&amp;quot;tableintopic&amp;quot;&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Index&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Data type&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Value&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_KEYWORD&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The keyword of the sms&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_TO_RESOURCE_ID&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The resource ID of the resource to which the sms is delivered&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_FROM&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;String&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The sender&#039;s number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_CONTENT&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The content of the sms (including the keyword)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example : &#039;&#039;&#039; On the workflow using for adding the journal basing on the sms content : &lt;br /&gt;
&lt;br /&gt;
array smsparameter=Workflow_getParameters();  &lt;br /&gt;
&lt;br /&gt;
string smskeyword = smsparameter[SMS_KEYWORD];&lt;br /&gt;
&lt;br /&gt;
number parentResourceId = smsparameter[SMS_TO_RESOURCE_ID];&lt;br /&gt;
&lt;br /&gt;
string phonenumber = smsparameter[SMS_FROM];&lt;br /&gt;
&lt;br /&gt;
string smscontent = smsparameter[SMS_CONTENT];&lt;br /&gt;
&lt;br /&gt;
addJournal(2188468, 1, &amp;quot;Comment&amp;quot;, smscontent); &lt;br /&gt;
&lt;br /&gt;
[[Category:Communicator_module]]&lt;/div&gt;</summary>
		<author><name>Huynhhuyphong</name></author>
	</entry>
	<entry>
		<id>https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24314</id>
		<title>SMS keywords</title>
		<link rel="alternate" type="text/html" href="https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24314"/>
		<updated>2012-04-12T08:08:10Z</updated>

		<summary type="html">&lt;p&gt;Huynhhuyphong: /* SMS keywords */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;﻿ &lt;br /&gt;
&lt;br /&gt;
== SMS keywords ==&lt;br /&gt;
&lt;br /&gt;
SMS keywords can be inserted into outgoing SMS. The SMS Keyword is the Identification text that will be used by people with mobile phones to send SMS back to us. A message might thus be &amp;quot;If you would like to receive a free newsletter pls send an SMS to 555-5555 with the message &amp;quot;KEYWORD&amp;quot;, where the keyword will depend on the provider they return the SMS to. All the KEYWORD merge-field in reality does is insert a keyword depending on the provider it is sent from instead of the KEYWORD tag. So it is a bit like a merge field. Only this mergefield is essential for anyone that wants to send an SMS to us to place first in the message so the provider knows that it is intended for your site as receiver. Besides this purpose, the keyword is also used as an &amp;quot;distribution rule&amp;quot; that identifies what resource&#039;s SMS inbox will receive the SMS. &lt;br /&gt;
&lt;br /&gt;
If you want to set up a keyword in Catglobe you can access the dialogue for this under the drop down menu of the Communicator SMS list. You will be introduced to a dialog like below. &lt;br /&gt;
&lt;br /&gt;
[[Image:8081.png|419px|SMS581-2]] &lt;br /&gt;
&lt;br /&gt;
When a keyword is added for a resource it means that this keyword is the one that will be merged into any mail sent from this resource for this provider. Thus there can only be one keyword per provider for the same resource. The keyword also has another function though. If the Catglobe site receives an SMS, then it will check if it can identify a keyword in it. If it can, then it will make sure that the incoming SMS is placed in the communicator of the resource that has this keyword registered. The keywords therefore also function as a type of distribution rule. &lt;br /&gt;
&lt;br /&gt;
Allthough you are sending an SMS with keywords from a specific resource it does not necessarily mean that this is the place to which you want its return messages sent. You can specify more distribution rules for SMS using this keyword by using the distribution rules feature of SMS. Activate the distribution rules button by highlighting one of your SMS keywords and click on it. You will then see the following dialog. &lt;br /&gt;
&lt;br /&gt;
[[Image:8082.png|450px|SMS581-3]] &lt;br /&gt;
&lt;br /&gt;
You can add multiple rules for the same keyword. Thus you can e.g. both sent a thank you SMS in return to the sender as well as well as move the SMS to a different resource in the system. &lt;br /&gt;
&lt;br /&gt;
Click create to add a rule. &lt;br /&gt;
&lt;br /&gt;
[[Image:8083.png|219px|SMS581-4]] &lt;br /&gt;
&lt;br /&gt;
At the top of the new SMS distribution rule dialog you can choose between 4 types of rules. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Move:&#039;&#039;&#039; Makes it possible for you to move the entire SMS to a different destination folder (typically the inbox) of a different resource. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Copy:&#039;&#039;&#039; Makes it possible for you to make a copy of the SMS on a different destination folder (typically the inbox) of a different resource. The difference to the move type is that this rule will leave not remove the original copy of the SMS. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Delete:&#039;&#039;&#039; Simply deletes the incoming SMS with the specific keyword. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Execute CGScript:&#039;&#039;&#039; This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project. &lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot; width=&amp;quot;875&amp;quot; style=&amp;quot;border-collapse:collapse; border:1px solid #010101&amp;quot; class=&amp;quot;tableintopic&amp;quot;&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Index&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Data type&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Value&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_KEYWORD&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The keyword of the sms&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_FROM&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;String&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The sender&#039;s number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_TO_RESOURCE_ID&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The resource ID of the resource to which the sms is delivered&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_CONTENT&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The content of the sms (including the keyword)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example : &#039;&#039;&#039; On the workflow using for adding the journal basing on the sms content : &lt;br /&gt;
&lt;br /&gt;
array smsparameter=Workflow_getParameters();  &lt;br /&gt;
&lt;br /&gt;
string smskeyword = smsparameter[SMS_KEYWORD];&lt;br /&gt;
&lt;br /&gt;
number parentResourceId = smsparameter[SMS_TO_RESOURCE_ID];&lt;br /&gt;
&lt;br /&gt;
string phonenumber = smsparameter[SMS_FROM];&lt;br /&gt;
&lt;br /&gt;
string smscontent = smsparameter[SMS_CONTENT];&lt;br /&gt;
&lt;br /&gt;
addJournal(2188468, 1, &amp;quot;Comment&amp;quot;, smscontent); &lt;br /&gt;
&lt;br /&gt;
[[Category:Communicator_module]]&lt;/div&gt;</summary>
		<author><name>Huynhhuyphong</name></author>
	</entry>
	<entry>
		<id>https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24313</id>
		<title>SMS keywords</title>
		<link rel="alternate" type="text/html" href="https://wiki.catglobe.com/index.php?title=SMS_keywords&amp;diff=24313"/>
		<updated>2012-04-12T07:29:35Z</updated>

		<summary type="html">&lt;p&gt;Huynhhuyphong: /* SMS keywords */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;﻿ &lt;br /&gt;
&lt;br /&gt;
== SMS keywords ==&lt;br /&gt;
&lt;br /&gt;
SMS keywords can be inserted into outgoing SMS. The SMS Keyword is the Identification text that will be used by people with mobile phones to send SMS back to us. A message might thus be &amp;quot;If you would like to receive a free newsletter pls send an SMS to 555-5555 with the message &amp;quot;KEYWORD&amp;quot;, where the keyword will depend on the provider they return the SMS to. All the KEYWORD merge-field in reality does is insert a keyword depending on the provider it is sent from instead of the KEYWORD tag. So it is a bit like a merge field. Only this mergefield is essential for anyone that wants to send an SMS to us to place first in the message so the provider knows that it is intended for your site as receiver. Besides this purpose, the keyword is also used as an &amp;quot;distribution rule&amp;quot; that identifies what resource&#039;s SMS inbox will receive the SMS. &lt;br /&gt;
&lt;br /&gt;
If you want to set up a keyword in Catglobe you can access the dialogue for this under the drop down menu of the Communicator SMS list. You will be introduced to a dialog like below. &lt;br /&gt;
&lt;br /&gt;
[[Image:8081.png|419px|SMS581-2]] &lt;br /&gt;
&lt;br /&gt;
When a keyword is added for a resource it means that this keyword is the one that will be merged into any mail sent from this resource for this provider. Thus there can only be one keyword per provider for the same resource. The keyword also has another function though. If the Catglobe site receives an SMS, then it will check if it can identify a keyword in it. If it can, then it will make sure that the incoming SMS is placed in the communicator of the resource that has this keyword registered. The keywords therefore also function as a type of distribution rule. &lt;br /&gt;
&lt;br /&gt;
Allthough you are sending an SMS with keywords from a specific resource it does not necessarily mean that this is the place to which you want its return messages sent. You can specify more distribution rules for SMS using this keyword by using the distribution rules feature of SMS. Activate the distribution rules button by highlighting one of your SMS keywords and click on it. You will then see the following dialog. &lt;br /&gt;
&lt;br /&gt;
[[Image:8082.png|450px|SMS581-3]] &lt;br /&gt;
&lt;br /&gt;
You can add multiple rules for the same keyword. Thus you can e.g. both sent a thank you SMS in return to the sender as well as well as move the SMS to a different resource in the system. &lt;br /&gt;
&lt;br /&gt;
Click create to add a rule. &lt;br /&gt;
&lt;br /&gt;
[[Image:8083.png|219px|SMS581-4]] &lt;br /&gt;
&lt;br /&gt;
At the top of the new SMS distribution rule dialog you can choose between 4 types of rules. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Move:&#039;&#039;&#039; Makes it possible for you to move the entire SMS to a different destination folder (typically the inbox) of a different resource. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Copy:&#039;&#039;&#039; Makes it possible for you to make a copy of the SMS on a different destination folder (typically the inbox) of a different resource. The difference to the move type is that this rule will leave not remove the original copy of the SMS. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Delete:&#039;&#039;&#039; Simply deletes the incoming SMS with the specific keyword. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Execute CGScript:&#039;&#039;&#039; This is a more advanced - but nonetheless extremely smart option. This rule offers you to choose a workflow or tabulation script. When an email with this keyword is received by Catglobe then the chosen script will be run. The SMS message will exist in context of the script and can thus be used to insert into e.g. a task or project. &lt;br /&gt;
&lt;br /&gt;
{| cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;2&amp;quot; border=&amp;quot;1&amp;quot; width=&amp;quot;875&amp;quot; style=&amp;quot;border-collapse:collapse; border:1px solid #010101&amp;quot; class=&amp;quot;tableintopic&amp;quot;&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Index&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Data type&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
| bgcolor=&amp;quot;#C0C0C0&amp;quot; width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&#039;&#039;&#039;Value&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_KEYWORD&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The keyword of the sms&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_FROM&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;String&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The sender&#039;s number&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_TO_RESOURCE_ID&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The resource ID of the resource to which the sms is delivered&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|- align=&amp;quot;left&amp;quot; valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| width=&amp;quot;292&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;SMS_CONTENT&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;116&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;string&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
| width=&amp;quot;467&amp;quot; style=&amp;quot;border:1px solid #010101;&amp;quot; | &lt;br /&gt;
&amp;lt;span class=&amp;quot;normalise&amp;quot;&amp;gt;The content of the sms (including the keyword)&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example : &#039;&#039;&#039; On the workflow using for adding the journal basing on the sms content : &lt;br /&gt;
&lt;br /&gt;
array smsparameter=Workflow_getParameters();  &lt;br /&gt;
&lt;br /&gt;
string smskeyword = smsparameter[SMS_KEYWORD];&lt;br /&gt;
&lt;br /&gt;
string parentResourceId = smsparameter[SMS_TO_RESOURCE_ID];&lt;br /&gt;
&lt;br /&gt;
string phonenumber = smsparameter[SMS_FROM];&lt;br /&gt;
&lt;br /&gt;
string smscontent = smsparameter[SMS_CONTENT];&lt;br /&gt;
&lt;br /&gt;
addJournal(2188468, 1, &amp;quot;Comment&amp;quot;, smscontent); &lt;br /&gt;
&lt;br /&gt;
[[Category:Communicator_module]]&lt;/div&gt;</summary>
		<author><name>Huynhhuyphong</name></author>
	</entry>
</feed>