Difference between revisions of "About Data Policy Actions"
From LongJump Support Wiki
imported>Aeric |
imported>Aeric |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 22: | Line 22: | ||
|- | |- | ||
|[[Record#Record_Owners|Change Record Owner]]||Change the record owner, reassigning the record and effectively managing data flow||||align="center"|[[File:Checkmark.gif|link=]] | |[[Record#Record_Owners|Change Record Owner]]||Change the record owner, reassigning the record and effectively managing data flow||||align="center"|[[File:Checkmark.gif|link=]] | ||
|- | |- | ||
|[[ | |[[Add Record]]||Select an object to add a record to, and choose whether or not to execute data policies triggered by the addition.||||align="center"|[[File:Checkmark.gif|link=]] | ||
|- | |- | ||
|[[ | |<span id="update_action">[[Update|Update Record]]<span> | ||
| | |||
Update the record; change the value of any field, using any formula you define. | |||
In addition to fields in the current record, you can specify fields in [[Lookup]]-target records using "dot notation". For example, a data policy action for an Order record could update a field in a related Customer record: <tt>related_to_Customer.email_address</tt>. (In the GUI, Lookup fields appear with a ">" after the name. Clicking one opens a new list box opens that displays fields from the target object.)<br> | |||
''Learn more:'' [[Updating a Field in a Related Record during a Data Policy "Update Record" Action]] | |||
:'''Important:''' | |||
:This action does ''not'' generate record update events (in order to prevent infinite recursions). | |||
| | |||
|align="center"|[[File:Checkmark.gif|link=]] | |||
|- | |- | ||
|[[ | |[[Send Outbound Message]]||With this data policy action, [[REST]] messages can be sent to a valid end point || || align="center"|[[File:Checkmark.gif|link=]] | ||
|- | |- | ||
| | | Post Item to Relay Feed || Post a message to a [[Relay]] Feed. (All existing feeds are available.) || align="center"|[[File:Checkmark.gif|link=]] || align="center"|[[File:Checkmark.gif|link=]] | ||
|- | |||
| Assign Follower in Relay || Assign a user as a follower of a record (Available if Relay is enabled for the object.)|| align="center"|[[File:Checkmark.gif|link=]] || align="center"|[[File:Checkmark.gif|link=]] | |||
|- | |||
| Remove Follower in Relay || Remove a user as a follower of a record (Available if Relay is enabled for the object.)|| align="center"|[[File:Checkmark.gif|link=]] || align="center"|[[File:Checkmark.gif|link=]] | |||
|- | |||
|[[Invoke a Java Method From a Data Policy|Invoke Java Method]] || Invoke a method in a Java class||align="center"|[[File:Checkmark.gif|link=]] || align="center"|[[File:Checkmark.gif|link=]] | |||
|- | |||
|'''Execute Java Code''' || Execute a custom data policy action by writing Java code and making calls to the [[Java API]] || align="center"|[[File:Checkmark.gif|link=]] || align="center"|[[File:Checkmark.gif|link=]] | |||
|} | |} | ||
Latest revision as of 00:57, 22 May 2013
About Data Policy Actions
Things to know:
- Multiple data policy actions can be specified for a data policy
- Several types of data policy actions can be executed
- They can be invoked in any order (or reordered as needed)
- In a Calendar Based Data Policy, all of the following actions are available
- In an Action Based Data Policy, the Activation Sequence determines which actions are available
Actions Description Activation Sequence Before Triggering Actions (Pre)
Activation Sequence After Triggering Actions (Post)
Create Task Create a task and assign it to selected users (Record Owner, Supervisor of Record Owner, Specific User, System Administration) 
Send Email Send an email message based on roles; optionally, send the message to an individual email address
Change Record Owner Change the record owner, reassigning the record and effectively managing data flow
Add Record Select an object to add a record to, and choose whether or not to execute data policies triggered by the addition.
Update Record Update the record; change the value of any field, using any formula you define.
In addition to fields in the current record, you can specify fields in Lookup-target records using "dot notation". For example, a data policy action for an Order record could update a field in a related Customer record: related_to_Customer.email_address. (In the GUI, Lookup fields appear with a ">" after the name. Clicking one opens a new list box opens that displays fields from the target object.)
Learn more: Updating a Field in a Related Record during a Data Policy "Update Record" Action- Important:
- This action does not generate record update events (in order to prevent infinite recursions).
Send Outbound Message With this data policy action, REST messages can be sent to a valid end point
Post Item to Relay Feed Post a message to a Relay Feed. (All existing feeds are available.)
Assign Follower in Relay Assign a user as a follower of a record (Available if Relay is enabled for the object.)
Remove Follower in Relay Remove a user as a follower of a record (Available if Relay is enabled for the object.)
Invoke Java Method Invoke a method in a Java class
Execute Java Code Execute a custom data policy action by writing Java code and making calls to the Java API