We are constantly mentioning the fact that appRules is the most powerful no-code engine for composing integration and business rules solutions. But that does not mean that appRules does not have the capability to integrate code in all forms when you need it. To the contrary, appRules includes easy-to-use facilities throughout the engine to extend your workflows using custom functions and expressions.
The App Object
Since we are talking code, we must discuss the App object which is the most widely used object in appRules.
App is automatically added and scoped to the main (top) Sequence when you create a new project in appRules.
You can access the methods and properties of the App object directly. The designer will accept conditions directly from the App object. This allows you to enter condition expressions such as App.Result, App.IsActionResultValid(), etc. while composing your workflow.
Below is an example of using a method from the App object in the If activity:
The Custom Function Editor is used for adding custom functions to appRules projects. Code can be added using either C# or VB. As in expressions, App exposes the methods and properties of the workflow to your function. The Custom Function Editor also supports intellisence for browsing the methods and objects.
Unlike typical development environments, you do not have to worry about compiling your code and referencing the assembly. Once validated, appRules takes care of compiling the code as needed.
Below is the appRules Custom Function Editor window:
Long story short, appRules – (the no-code engine) supports serious code when you need it. It uses familiar languages and objects giving you full access to .NET. This allows you to reuse existing code in your organization thereby saving money and completing projects much faster.
You can download appRules with sample projects at: http://www.appstrategy.com/appRulesTrial