In the last article, we learned about the default (overridable) Sightlane Evaluation Flow and how it can help you inspect Transaction Security Policy Events. As mentioned, you are not required to use the default Flow. You can create your own, as long as you stick to a few rules. In this article, we will go through the requirements for building a custom Evaluation Flow.
|
First, it must contain an input variable called PolicyEvent of the type sightlane_em__PolicyEvent. You don't need to assign a value to this variable; if it is present, SightLane will automatically populate it with appropriate Transaction Security Policy event data. |
Once the flow has been populated with the correct event data, you can use that data to make decisions about whether or not the event qualifies as meaningful for your organization or needs to be documented in a SightLane event.
|
In addition to populating event data, you must define two boolean output variables called NeedsReview and Result. These are the flow's "return values" and give SightLane the information it needs to decide how to proceed. |
It is a common practice to assign default values to these variables based on the most likely outcomes. For example, the NeedsReview variable might have a default value of False since most events will not need review (or maybe in your company, they will!) This simple practice can help you to avoid unnecessary assignment statements in your Flow.
For everything to work correctly, don't forget to assign your custom Flow to the appropriate Policy Event record!
Once you've created these three variables and linked the Flow to the appropriate Policy Event record, you're all set. The logic for determining whether an event is relevant to your organization is entirely customizable. You have the full capabilities of Salesforce Flows at your disposal, allowing you to make decisions as simple or complex as needed.