Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Parent-Child: Child Project sample project is used for demonstrating the behavior of child projects in appRules. Child projects allow you to split very large projects into smaller projects to make them more manageable in the designer.
In this example, the project simply displays the values in the parent project at runtime using a single ViewRuntimeValues activity.
To create a child project, click the New button and select Child Workflow. as the project type. You must also select a Parent Project.
Designer:
Notice that you get access to all the data fields, variables, arguments, etc. that have been defined in the parent project. Explore the configuration of the ViewRuntimeValues activity on the sample project to view the values that have been defined.
This project will be called by the parent project (Parent-Child: Parent Project) at runtime.
This sample project demonstrates how to use the PurgeLogEntries activity from the Automation module to clean up and maintain your project. To automate the process the project has been scheduled to run every 24 hours.
Activities:
The project contains only a single activity - the PurgeLogEntries activity from the Automation module.
Edit the activity and notice that it has a single property. Enter the value of the number of days to be used for purging logging records. That's all that is required.
This project has been scheduled to be run by the appRules Scheduler. The project details shows the scheduling configuration in the Schedule tab:
You can select one of the preconfigured run frequencies or configure a new one using the Cron syntax.
The Parent-Child: Parent Project sample project is used for demonstrating parent/child projects in appRules. A parent project can has an unlimited number of child projects which can be called from the parent. Child projects allow you to split very large projects into smaller projects to make them more manageable in the designer.
In this example, the project reads values from a data source. In addition, it also sets some values to be displayed in a child project. Lastly it calls the child project which displays the values.
To create a parent project, click the New button and select Parent Workflow as the project type.
Below is the Project Details form of a parent project. Notice that the Projects tab shows the child projects for the parent project:
Designer:
This sample uses three activities to set up and call the child project as shown below. Explore the activities to view the settings of their properties.
When this parent project is run, it calls the child project to display the values retrieved in the child project using the ViewRuntimeValues activity:
This sample project demonstrates data record error tracking and logging on Target activities.
The activities in this sample project have been deliberately configured to generate data record errors.
Explore the MapRecordFields activity to see the invalid field mappings
After running the project, use the Logs/Stats button to view Project Run Details for job statistics.
Use the Audit Logs button from the Project Run Details toolbar to view additional statistics and the errored records and associated errors.
You can experiment with the configurations and run the project to view the results as the project has been configured to use the embedded database. No additional data source configurations are required.
The Task Parallelism sample project demonstrates how to use the appRules Parallel activity to implement Task Parallelism in appRules projects.
This is a very simple sample that launches three jobs that run in parallel in the background.
The jobs which are based on the Infinite Loop project, are launched using the ExecuteWorkflow activity.
To add a Parallel activity, drag it from the Control Flow module of the Toolbox.
The project has been preset to run in the background.
When you run the sample project, you can view or cancel the job(s) using the appRules Job Monitor.
This sample project demonstrates how to define and use a custom query to read data records.
In the sample, instead of configuring selection options for the source, the appRules Custom Query Editor is used to define a simple query.
Feel free to experiment with your own queries.
The appRules Custom Query Editor supports SQL query access for all data sources. This includes not only relational databases, but also SaaS platforms such as Salesforce, Dynamics365, Snowflake, etc.
Points of interest:
1 - InitializeSource Activity
Select CustomQuery as the QueryType instead of Configuration. Click the Add/Edit Query property to define the custom query:
2 - While Activity
The While activity is used to loop through and view the resulting records. It has been configured with a condition to to end after reading the last record from the dataset.
3 - ViewRuntimeRecords Activity
This activity has been configured to display the current record. In an actual project, the values can be used for loading additional data, calculations, etc.
4 - GetNextRecord Activity
This activity gets the next record from the resulting dataset.