Automate tasks with Platform triggers
Triggers give you a powerful way for you to automate tasks. They automatically make input, output, update, validations, emails, and Web Services calls in response to data changes. Anytime you have a regular event related to changing object records, you can add the event to your application in the form of a trigger.
For example, in a commissions application, you might have a trigger that posts to the General Ledger when a commission is added. Alternatively, you could have a trigger that updates a related object based on changes to the object in scope. You can also use triggers to create complex validations on data entry fields and return custom error messages to the user.
The Platform trigger infrastructure works on both standard and custom objects. Configuration objects cannot include triggers. Developers can place triggers before and after creating, updating, and deleting an object.
Access to certain features in Customization Services or Platform Services are based on your administrative privileges. See the table below to determine what kind of administrator you need to be for each feature. Learn more about Permissions for Customization and Platform Services.
| Feature | Permissions needed |
|---|---|
|
|
Only full administrators can edit page layouts on standard pages. |
Only full administrators can access Platform Services features because only they can change the behavior of Sage Intacct pages. |
|
We recommend limiting this permission to one or two admin users who control the authorization and installation of applications with UDDs. The installation of applications with UDDs must be authorized. There might be an associated cost for the company installing the application, UDDs cannot be uninstalled after they are in use, and transaction and report processing times can increase as UDDs are added. |