> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/parent-child-parent-project.md).

# Parent-Child: Parent Project

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. 

**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:


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appstrategy.com/apprules-r-documentation/samples/sample-projects/miscellaneous/parent-child-parent-project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.