Making Raven work for You

Customization, Automation/Workflow

Raven Macros allow Enterprise customers to add features specific to their needs and automate actions. For example:

1. Special validation rules
   "If the Category includes 'Vacation Request' then the Notes field should contain special substrings that indicate the start date and end date (e.g. '#start:01/20/2022', '#end:01/25/2022')";
   
   
2. Execute helpful actions
   "When a Topic whose Category includes 'Client Meeting' is saved, create an Update, and attach the 'Expense Claim.pdf' file."
   

Macros can be computed internally or externally:

1. Internal
   These use built-in functions that have been coded into the Raven application by its developers.
   
   
2. External
   These are run by the RavenExtension program, which resides outside of the Raven App. The client can modify the RavenExtension to perform custom actions. One possible sequence of actions:
   

1. When a Record has been saved successfully, the Raven Macro sends data about the Record to the RavenExtension.
   
   
2. The RavenExtension assess whether to take action. For example, it might match the rule: "if the Status of a Topic changed from 'Prospect' to 'Prepare Quote', initiate a credit check.
   
   
3. The RavenExtension will then return control to Raven. In this example, there is no need to initiate another Macro, and the overall save operation will be completed.
   

1. A RavenExtension template, with extensively documented code, is available for Enterprise users.