Overview of Infinity Record Operations
Record operations enable us to write custom operations that we can execute on rows of data. They are composed of two elements:
-
A stored procedure to perform the operation
-
A prompt definition to display a message to users before the operation executes
Record operations are most often used to delete records, although they can also update records.
You may have noticed multiple record operation templates when you added specs to the development environment. The table below provides a high-level overview of each type and when to use them.
Spec Template Name |
Description |
---|---|
Record Operation (SP) |
Creates a spec to define a stored procedure-implemented record operation. The good news is that the Infinity platform automatically handles most details for this type of spec. |
Record Operation (CLR) |
Creates a spec to define a CLR-implemented record operation. Unlike the Record Operation (SP), this spec gives the software developer the ability to invoke .NET code to handle the record operation. The .NET class that you develop will be a server-side catalog implementation that will be used to execute the record operation. This spec includes a CLRRecordOperation element that contains the AssemblyName and ClassName attributes. The AssemblyName attribute denotes the assembly that contains the catalog feature code. The ClassName attribute identifies the class within the assembly that contains the catalog feature code. This class should inherit the AppCatalog.AppRecordOperationPerform class. |
Record Operation (Wrapped SP) |
Creates a spec to define a stored procedure-implemented record operation based on an existing record operation spec. The spec that is created by the SDK wraps around an existing stored procedure. The existing stored procedure is created from a previous Record Operation (SP) spec type. When you create the wrapped spec, you select an existing Record Operation (SP) or "original" spec. A new spec template is created that invokes the stored procedure that was previously created in the original Record Operation (SP) spec. The purpose of the wrapped SP spec is to enable the software developer to extend the capabilities of a previously created spec by executing additional stored procedures in addition to the one referenced in the original spec. |