About Data Policy Actions

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, like this: related_to_Customer.email_address.
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