Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This project shows how to use a folder of CSV files to model a SQL database. The files model SQL database tables and can be queried and used just like regular SQL tables.
The project has been setup to iterate selected records in a file using SQL. The selected records are displayed using the ViewRuntimeRecords activity.
Explore the properties of the InitializeSource activity of the CSVDatabase module which is used to read the records.
The Decision Table - Customer Discount project illustrates the appRules Evaluate Decision Table activity.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Decision Table - Customer Discount" project.
EvaluateDecisionTable is the only workflow activity required for configuring a decision table in appRules. It can be accessed from the Business Rules module in the toolbox.
For simplicity, we have used a single activity in this sample project. In an actual project, the EvaluateDecisionTable activity is used in conjunction with other activities.
Also, in this sample, the values to be evaluated are passed to the EvaluateDecisionTable activity from the arguments used to run the project. In an actual project, the values passed to the activity typically come from record values in data sources such as CRM, ERP, Databases, etc. The project can also be called via the appRules WebAPI.
Note that the View Execution Results box of the EvaluateDecisionTable activity is checked to display the result when the activity is executed. This is the practice for debugging appRules activities. At deployment, the View Execution Results box is automatically deactivated if the project is not run in interactive mode.
You can experiment with this project by making changes and running the project to view results. No external data sources are required.
Define Conditions to be used in the decision table:
Define Actions to be used in the decision table:
Set up Conditions and Actions:
Define Decision Conditions Items:
Define Decision Action Items:
Configure Condition and Action combinations:
Run the project directly and pass arguments to be used for evaluating the decision table:
View the Execution Results and notice that row 3 in the result table below meets the criteria as defined by the arguments passed to the project.
The project can also be called via the appRules WebAPI.
Platform Product | Availability |
---|---|
Hosting Option | Recommended for Project |
---|---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
Conditional Actions Execution sample project demonstrates how to use the PerformActions activity in the Business Rules module to execute a series of actions.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
The action executions can be based on the results of executed conditions.
The page below shows how to configure the ActionItems property:
Points of Interest:
In row 1, the selected condition is executed. if the result is True, Action Default/True action is executed. If the result is False, the Action False action is executed.
In row 4, since no condition is specified, the action specified as the Default action is executed.
You can use the Option button to select the execution option from a list of available options.
Platform Product | Availability |
---|---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
The Snippet - Infinite Loop project demonstrates how to create an infinite loop project in appRules using the While activity and the Delay activity.
1. PerformAction Activity
The PerformAction activity is used to set the last LastResult to True to enable the While activity condition.
2. While Activity
The While activity has been configured to loop endlessly by setting the Condition to “Last Result is True”
3. Delay Activity
The Delay activity has been configured to simply delay execution and then continue.
This project has been pre-configured to run in the background. If you run it interactively, it will tie up your session.
Use the appRules Job Monitor to terminate the job.
This sample snippet project demonstrates how to use a function from the appRules Financial library.
The appRules Financial Library includes Microsoft Excel compatible financial functions that are accessible from the appRules Actions Editor.
This sample project uses the ACCRINT financial function which returns the accrued interest for a security that pays periodic interest.
Below is the definition of the function to be used in the PerformAction activity. It includes the configuration of the properties required for calculating the accrued interest.
For this sample, the Calculate Accrued Interest action is then used in the Perform Action activity as shown below. Note that the action can also be used in other objects or as part of other actions, conditions, queries, etc.
Note that the activity has been configured to display the result at runtime.
When this project is run, the result is displayed as shown below:
This snippet sample project demonstrates how to configure appRules Actions to generate and maintain counters and running totals without using scripts or code.
The project uses a single ViewRuntimeValues activity accessing actions and conditions that have been defined for the demonstration.
9 Actions have been defined in the project:
2 Conditions have been defined in the project:
17 Entries have been added in the ViewRuntimeValues activity used in the project:
When the project is run the results are shown as follows:
The Snippet – Arguments, Variables, Dynamic Values & Sourced Values project demonstrates how to define arguments, variables, dynamic values and shows how to use appRules Sourced Values to set these values.
Arguments are defined in the Arguments tab of the Project Details form as show below.
Note that the values shown are defaults. They can be changed by passing different values when you run the project.
Variables are defined in the Variables tab of the Project Details form as show below.
Dynamic Values are not pre-defined. They are created automatically the first time they are used in the project.
Sourced Values are used when getting and setting values in appRules. appRules includes several built-in value sources and editors are displayed at design time based on the Source(type) of the data. In this sample project, you will explore several editors displayed when setting the values.
The Sample Project:
Two activities are used in this project to set and display values.
This activity from the Base module is used for setting the values.
The Values property is a collection for setting values.
The following is the Sourced Value editor for setting the value:
The following is the selection of the Sourced Value that sets the new value:
This activity from the Dialogs module is used to display the values. When the project is run, the following form is displayed:
This snippet sample project demonstrates how to configure composite keys for updating and deleting records.
The sample uses a simple example for deleting a record from a SQL Customers table using multiple fields that make up the composite key. The process is the same for modifying a record using composite keys.
Activities:
InitializeTarget This activity initializes the Target activity that will be used for the deletion.
DeleteRecord This activity is used for performing the actual record deletion.
Edit the DeleteRecord activity:
Then click on the Option property:
Select Composite Key as the key type and configure the collection of composite keys:
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.
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The "Replicate Dynamics365 In Snowflake" sample project shows how to utilize the appRules Data Migration Engine for enterprise-scale data replication. As you review the project, note the following:
The entire project uses a single workflow activity - the MigrateData activity.
Configurations are used for all aspects of the project instead of scripts or code.
Easily configurable options for optimizing processing including Source and Target workers.
The process is the same not only for Dynamics365 but for hundreds of sources, such as Dynamics CRM, Salesforce, SharePoint, etc.
The process is the same not only for Snowflake but for other supported targets of appRules Data Replication, such as ADLS, AmazonS3, Azure Synapse, Cassandra, DB2, Databricks, BigQuery, MySQL, Oracle, PostgreSQL, Redshift, SQL Azure, SQL Server, etc.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Replicate Dynamics365 In Snowflake" project.
First, we will create a new project for the data replication job. Click the New button on the Project toolbar of the appRules Home Page. Simply enter the name of the project - (Replicate Dynamics365 In Snowflake) and click the Save button.
We will configure the entire job using the appRules MigrateData activity. Drag the MigrateData activity from the Migrate-Replicate-Synchronize module of the toolbox on to the designer and configure it as described in the following sections.
appRules uses data source metadata extensively for all processing. Before configuring the migration project we must first connect to Dynamics365 to generate the metadata of the data source. Once generated, the data source metadata can be used in all your appRules projects including Business Rules, Integration and Automation. There is no limit on the number of data sources and related metadata.
To generate metadata and create the Dynamics365 data source, click the "New DataSource" button on the toolbar. Select the Connector (from CRM or ERP categories) and configure as shown in figures below. Follow subsequent prompts to generate the metadata.
Now that we have created the Dynamics365 data source, select Dynamics365 as the default source, Data Replication as the data migration type, and Snowflake as the target. On subsequent modals, click the OK toolbar button to continue.
Configure the connection properties and schema options for Snowflake:
Select the Dynamics365 entities to be replicated in Snowflake:
The entities to be replicated are shown in the appRules Data Replication Target Entities collection:
Snowflake Table Definitions
The definitions of the target tables are automatically generated by appRules and can be modified to suit your needs:
Snowflake Table Column Definitions
The definitions of the target table columns are automatically generated by appRules and can be modified to suit your needs:
The definitions of the Dynamics365 to Snowflake field maps are automatically generated by appRules and can optionally be modified to suit your needs. For example, you can use appRules field mapping to transform Dynamic365 data before saving in Snowflake.
You can also optionally define Mapping Conditions to be utilized in the mapping process using the appRules Condition Editor:
To configure a Condition to be applied to a row in the MapRecordFields modal:
Configure the Condition by navigating the Condition tree on the appRules Condition Editor (Condition-->Category-->Type).
Configure the properties of the selected condition type.
Name and save the condition.
You can quickly transform values in the mapping activity modal by configuring Action Fields without writing code using the appRules Action Editor:
To transform a value using the ActionField option:
Configure the Action by navigating the Action tree on the appRules Action Editor (Field-->Field-->Module-->Type).
Configure the properties of the selected action type.
Name and save the action.
The appRules Data Replication Target Entities collection is automatically generated for you and is ready to run the replication jobs for the selected entities. As an option, you can make changes to the entities to suit your needs:
Job Execution Mode - Select Default, Sequential or Parallel execution
More ... Explore the other options of the collection entries for the entities to be replicated
As you configure your project, appRules automatically organizes and stores the project settings. Before running the project, you can review the project settings from a central location by clicking on the Project Details button:
Review and make any changes in the following tabs:
Run Options: Use this tab to make changes related to the defaults for running the job.
Status: View the current status of the project
Schedule: Use this tab to optionally schedule the job to be run
Notifications: Define optional notifications
Arguments: Define optional project variables
Activities: View the activities that have been defined for the project by dragging and dropping from the toolbox on the designer.
Notes: View or edit notes associated with the project
Json: View project JSON
Projects: View optional child projects associated with this project
Validations, error handling, and notifications are critical components for executing successful data migration, data replication and data synchronization projects.
appRules includes the following options for error handling and notifications:
Automatic and on-demand validation is available for all target entity definitions.
Configure each entity replication entry to suit your needs. Then the job can be run directly, scheduled to run, or run via the appRules Web API.
To run the project via the appRules Web API, follow the instructions in Using the Web API
If you are running a long running job, you can monitor it by using the appRules Job Monitor:
View job details
Set a job control value
Pause job
Cancel job
During and after the run, you can utilize the many facilities available in appRules to view results and statistics.
You can browse the the source and newly replicated data records using the appRules Data Source Browser as shown in the figure below.
You can define queries to load records and optionally even edit data records using the appRules Data Source Browser:
To view "Data Migration Logs and Statistics", click the "Logs/Statistics" button on the "appRules Data Migration: Target Entities" toolbar. The following modal will be displayed:
appRules Data Migration Logs and Statistics offer a rich set of options to give you insight into running or completed jobs as show in the sections below. Simply configure the selection criteria that meets your requirements and click on the Summary, Statistics, Project Run Details or Audit Log Details toolbar button.
At any point, you can access the Data Migration Job Summary to view the results of running or completed instances:
Job Status
Completed Record Counts
Skipped Record Counts
Error Record Counts
Gain insight on the state of running or completed job instances by viewing job statistics.
Gain insight on the state of running or completed job instances by viewing Project Run Details:
Job Instance detail including reference, start, end, duration, current state, etc.
Snapshot View of Audit Log Details including Success, Failed, and Skipped Record counts.
Workflow Activity Statistics
Data Source Statistics
Condition Execution Results
Action Execution Results
Arguments & Variables
Runtime Logs & Errors
You can configure your appRules data migration, replication and synchronization jobs to capture all pertinent information regarding every source and target record involved in the process. This level of detail is especially useful in heavily validated organizations and offers the best tool for reconciling the results of the process.
Audit Log Details can be viewed by accessing the Data Migration Logs and Statistics modal and selecting the range of log entries to view.
Conclusions
Powered by the all-in-one appRules Platform, the appRules Data Migration Engine offers the most powerful and flexible end-to-end solution for enterprise-scale data migration, data replication and data synchronization for IT Departments, Solution Providers, and Consultants.
This sample project has been used to showcase the powerful, easy-to-use, and fully configurable features of appRules including:
No-code environment
Replicates data from hundreds of sources including SaaS platforms into popular targets including SQL databases and data warehouses such as ADLS, AmazonS3, Azure Synapse, Cassandra, DB2, Databricks, BigQuery, MySQL, Oracle, PostgreSQL, Redshift, SQL Azure, SQL Server, etc.
Integrated support for hundreds of data source connectors.
Metadata-driven solution
All settings including source entities, target entities collection, target tables, and field mappings are automatically generated and can optionally be modified for customized implementations without writing code.
Conditioned field mappings using the powerful appRules Condition Editor.
Field transformations using Action Fields configured using the powerful appRules Action Editor.
Integrated Job Monitors, Logs, Statistics and the appRules Data Source Browser.
Next Steps
You can continue exploring the many features available for data migration, data replication and data synchronization in the appRules Data Migration engine. The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Replicate Dynamics365 In Snowflake" project.
If you require assistance, please contact support@appstrategy.com
Platform Product | Availability |
---|---|
Hosting Option | Recommended for Project |
---|---|
Apply the condition by selecting it on the Mapping Condition column of a specific row of the table in the MapRecordFields modal.
On a specific row of the MapRecordFields modal, select ActionField as the Source of the value to be mapped to a target field. Then select the Action that you have created above.
Target Loader Settings including batch size, and error tracking
Source records query options - Property Configuration or Custom Query
Optional Source Workers to split the source records and handing off to additional sessions
Optional Target Workers to optimize processing by configuring additional sessions and threads.
Audit Logging Settings to capture details for replication detail record reports and statistics.
Automatic and on-demand validation is available for all workflow activities.
Incomplete, Terminated, and errored job instances can be rerun to process only the incomplete or errored records. This saves a great deal of time as successfully transferred records are skipped - greatly reducing the load trips to the source.
Edit the LoaderSettings property of any Target Entity definition to optionally configure error tolerance threshold and the action to perform when the error limit is exceeded:
Edit the Notifications tab of the Project Settings to define project-wide notifications:
Click to Run toolbar button to run the project directly. Select the server and other settings for the job run.
To schedule the job, edit the Schedule tab of the Project Details:
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The "Migrate Parent/Child Records Using Target/Bulk Loader" sample project demonstrates another option for executing parent/child migrations and features the following:
The InitializeTarget workflow activity activated for Bulk Loading
The MapRecordFields activity used for mapping, inserting records and record iteration
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Migrate Parent/Child Records Using Target / Bulk Loader" project.
This sample project demonstrates how to use only a few activities to migrate parent/child records.
The sample migrates records from a Customer table in a SQL database to the Account and Contact tables in Salesforce. You must set the authentication properties for Salesforce before running the project.
Reads records from the Customers table of the SQL database to be imported into the Salesforce Account and Contact objects.
Initialize target for the Salesforce Account records. Customer company records will be stored using this activity.
Initialize target for the Salesforce Contact records. Customer contact records will be stored using this activity.
The while loop activity is used for iterating the records in the Customer table and mapping accounts/contacts, and specifying the Save options. It contains the two MapRecordFields workflow activities used in the project.
Maps Customer record using company fields to Salesforce Account record. After mapping, the record is saved using this activity.
Maps Customer record using company fields to Salesforce Account record. After mapping, the record is saved using this activity
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Export SQL Tables to CSV Using Flow" project.
This sample project has been configured to show how to use a regular flow to export records from a SQL database to a delimited file (CSV)
Note that this approach can also be used to export records from other data sources such as Salesforce, Dynamics 365, etc.
For this project, you must add the BaseData module to the toolbox. The BaseData module is used for generically accessing data sources. The same activities can be accessed from their specific modules. For example, the SQL initialization/access activities in this sample project can be accessed from the EmbeddedDB module and the CSV initialization/access activities can be accessed from the DelimitedFile module.
Activities:
1. InitializeSource – Initialize SQL Source
This activity initializes the SQL source. Check out the properties of this activity to see how you select fields, define filters etc. for reading the data from a data source.
2. InitializeTargetFile – Initialize CSV Target File
This activity initializes the CSV target file. Check out the properties of this activity to see how you select fields etc. for saving data into a csv file.
Note that if the full path name is not specified as the file is created in the appRules Shared Files folder in the ProgramData directory
3. While Activity
This While activity has been configured for iterating the records in the SQL source
MapAndSetFields
This activity maps and sets the CSV record field values.
WriteDelimitedRecord
This activity writes a record in the delimited file.
GetNextRecord
This activity reads the next record from the SQL data source
4. CloseSource
This activity closes the SQL source and releases resources. Note: This is also done automatically if the CloseSource activity was not included.
5. CloseTarget
This activity closes the CSV file and releases resources. Note: This is also done automatically if the CloseTarget activity was not included.
Platform Product | Availability |
---|---|
Hosting Option | Recommended for Project |
---|---|
Platform Product | Availability |
---|
Hosting Option | Recommended for Project |
---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
appRules Data Migration Engine |
appRules Integration & Automation Engine |
appRules Enterprise 360 |
IIS |
appRules Host Service |
appRules Desktop |
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Batch Data Source Entities to Files" project.
The '"Batch Data Source Entities to Files" sample project demonstrates how to use the appRules MigrateData activity to perform batch migration of entities in a data source to files in a folder.
In the sample project, a single workflow activity is configured to load tables from a SQL Database into CSV files in a folder.
Drag the MigrateData activity from the Migrate-Replicate-Synchronize module of the toolbox on to the designer and configure it as follows:
Select Source Database as the default source, and Export to Files as the data migration type.
Select the tables to be exported:
All properties required for the Target Entities collection will be automatically set for the process. You can make any required changes to suit your needs.
Run the project and the files will be created in the Output folder:
...DbFiles\Samples\DataMigration\Output\Source Database-Files
This project shows how to use the InitializeDeletedSource activity in the Salesforce module to iterate deleted records in Salesforce.
The Salesforce InitializeDeletedSource activity is one of the many specialized activities in appRules that encapsulate powerful functionality in a single activity. It retrieves the list of selected deleted records in Salesforce and turns them into a Source in appRules.
The Salesforce InitializeDeletedSource activity is accessible from the Toolbox and is also configurable as an Action in the Action Editor. Below are the key properties of the InitializeDeletedSource activity:
Below is the project to iterate the deleted records:
appRules features an unmatched number of options for migrating, replicating and synchronizing data.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Replicate Dynamics365 In Snowflake" project.
The One-to-Many Data Migration sample project demonstrates how to use the appRules MigrateData activity to perform One-to-Many data migrations.
In the sample project, a single activity is configured to load the Customers table from the SQL Database into the Account and Contact tables in Salesforce.
The process is the same not only for Salesforce but for other data sources, such as Dynamics365, Snowflake, etc. and does not require any code or scripts.
You will need to use your own credentials to access Salesforce to run this project.
Drag the MigrateData activity from the Migrate-Replicate-Synchronize module of the toolbox on to the designer and configure it as follows:
Select the default Source, Data Migration Type, and default Target:
Configure the Source Entity, the Primary Target Entity, and Secondary Target Entities:
Complete the configuration of the Target Entities to suit your needs including mapping, etc:
Notice the entries in the SecondaryEntities collection. Configure to suit your needs - mapping etc:
After running the project, you can view the Project Details and Audit Logs records and statistics.
Platform Product | Availability |
---|---|
Hosting Option | Recommended for Project |
---|---|
Platform Product | Availability |
---|
Hosting Option | Recommended for Project |
---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
appRules Data Migration Engine |
appRules Integration & Automation Engine |
appRules Enterprise 360 |
IIS |
appRules Host Service |
appRules Desktop |
The appRules conditions, actions, workflow activities and project types are very versatile. One of the many unique project types that you can compose quickly in appRules is “Round Robin Assignments”. Composing “Round Robin Assignments” projects in appRules is fast and easy. Simply drag, drop and configure the source, target and iteration workflow activities and you are good to go! Round Robin Assignments include lead assignments, territory realignments, and more.
This sample project shows how to use the 'iteration control' properties to perform round robin lead assignments.
The workflow activities and other modules used in this sample project are available in the following appRules Platform products:
If you are running the On-Premise, Azure Marketplace or AWS Marketplace editions, the following hosting options supported by appRules are recommended for running this sample project:
Since the appRules Host Service is automatically installed and ready to go, it is recommended that you use it for evaluating this sample project. Just point your browser to the appRules URL
The completed project is available in the appRules Samples project database. Click the "Open" toolbar button on the appRules home page to select the "Round Robin Lead Assignment" project.
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.
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.
Platform Product | Availability |
---|---|
Hosting Option | Recommended for Project |
---|---|
appRules Data Migration Engine
appRules Integration & Automation Engine
appRules Enterprise 360
IIS
appRules Host Service
appRules Desktop
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 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 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.