User Tools

Site Tools


replicator_snc_subscribe

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
replicator_snc_subscribe [2016/11/14 10:35]
josephm [Condition script]
replicator_snc_subscribe [2018/08/01 16:28] (current)
angela.zhang
Line 52: Line 52:
 } }
 </​code>​ </​code>​
 +
 +//4. When setting up the table, make sure you mark at least one of the options: Create, Update, Delete.//\\
  
 ===== Override system fields =====  ===== Override system fields ===== 
Line 60: Line 62:
  
 ===== Refresh history set ===== ===== Refresh history set =====
-A checkbox to indicate if the history set for this table should be refreshed and updated when content is updated in other tables ​that are tied to this table.  ​This is needed ​if the sharing instance is sharing journal field entries ​and attachments and this instance is subscribing ​to them so that new journal field entries/​attachments tied to this table will refresh ​for this table'​s ​entries ​to see them in their history set.  In general this setting should be checked //​with ​the exception of the sys_audit log// (which has a large number of entries ​tying everything together already so it doesn'​t need to be refreshed).+A checkbox to indicate if the history set for this table should be refreshed and updated when content is updated in other related ​tables.  ​For example, ​if you are subscribing to the incident table and you want to refresh ​the incident record'​s ​history set in order to see the record'​s journal field entries ​and attachments 
  
 +<WRAP round info>
 +This option **should not** be selected on subscribe configurations for the **sys_audit,​ sys_journal_field,​ sys_attachment and sys_attachment_doc tables**. ​ These tables themselves do not have history sets to refresh. ​ If you want to refresh to see these journal/​audit/​attachment records on a table such as incident, select this option on the incident table instead.
 +</​WRAP>​
 +
 +In <wrap info> [[updateset_releases|v3.20.0]] </​wrap>,​ a scheduled job will run every minute to refresh history set for subscribed records. ​ Previously, a Run Once scheduled job was created for each record that was to be refreshed.
 ===== Field prefix ===== ===== Field prefix =====
 A field indicating if fields in the sharing instance have a prefix that the table on this subscribing instance does not.  For example the sharing table may have fields with a prefix of "​u_"​ whereas the subscribing table may not.  This field can be left blank if the field names are the same which will apply in most cases. A field indicating if fields in the sharing instance have a prefix that the table on this subscribing instance does not.  For example the sharing table may have fields with a prefix of "​u_"​ whereas the subscribing table may not.  This field can be left blank if the field names are the same which will apply in most cases.
Line 70: Line 77:
 Similar to Condition allowing you to specify conditions in order to subscribe to data for this table. ​ The script will be evaluated and return a value "​anded"​ with those specified in the "​Condition"​. ​ The "​current"​ global variable represents the incoming record de-serialized into GlideRecord. Similar to Condition allowing you to specify conditions in order to subscribe to data for this table. ​ The script will be evaluated and return a value "​anded"​ with those specified in the "​Condition"​. ​ The "​current"​ global variable represents the incoming record de-serialized into GlideRecord.
  
-In <wrap info> [[updateset_releases|v3.16]] </​wrap>,​ users can access the inbound message in the condition script represented by //​qcurrent//​. For example the following script is set up to only accept messages from a specific instance, accessed by //​qcurrent//​.key.+In <wrap info> [[updateset_releases|v3.16.0]] </​wrap>,​ users can access the inbound message in the condition script represented by //​qcurrent//​. For example the following script is set up to only accept messages from a specific instance, accessed by //​qcurrent//​.key.
  
 <​code>​ <​code>​
Line 77: Line 84:
 ===== Before Subscribe Script ===== ===== Before Subscribe Script =====
  
-{{page> before_subscribe_script}}+{{page> before_subscribe_script&​noheader&​nofooter}} 
 + 
 +===== After Subscribe Script ===== 
 + 
 +{{page> after_subscribe_script&​noheader&​nofooter}}
  
  
replicator_snc_subscribe.1479148509.txt.gz · Last modified: 2016/11/14 10:35 by josephm