**Data Modeling Hub > Events > Add event**.
2. In the **Name** field, enter `quest.renewableComplete`.
In the API and SDK, the name parameter is usually called `action` or `action name`.
3. Optionally, define a human-friendly display name that will be shown in **Data Modeling Hub** and **Decision Hub**.
4. Optionally, in the **Description** field, enter the description of the event.
5. Enable the **Make this event available to anonymous profiles without JWT** toggle.
6. Click **Apply**.
8. In the list of events, find the event you just created.
9. On the right side of the screen, click **Add property**.
10. In the **Source parameter** field, enter `gameName`.
11. In the **Property name** field, enter a human-readable label for display in the Synerise platform.
12. Optionally, in the **Description** field, you can add an explanation about the purpose of this parameter.
13. In **Property type** and **Link** fields, leave the default `string` and `-`.
13. To complete the process, click **Save**.
## Create an aggregate that returns the timestamp of the last finished quest
---
In this step, we create an aggregate that provides the timestamp of the most recently completed quest. The timeframe for the quest begins on the day it starts and continues until the expected completion time.
1. Go to 
**Behavioral Data Hub > Live Aggregates > Create aggregate**.
2. As the aggregate type, select **Profile**.
2. Enter the name of the aggregate as `[UC] Timestamp of last finished quest`.
3. Click **Analyze profiles by** and select **Last**.
4. From the **Choose event** dropdown, select the `questRenewableComplete` event, that you created in the [previous](/use-cases/renewable-quest#create-a-questrenewablecomplete-event) step.
5. As the event parameter, choose **TIMESTAMP**.
6. From the **Choose parameter** dropdown list, select the **gameName** parameter.
7. From the **Choose operator** dropdown list, select **Equal**.
8. Enter the name of the quest. In our case, it’s `Towel's quest`.
7. Set the period for the aggregate to **Custom** and specify the desired data range. In this scenario, we will select the following time range `02.06.2023 - 30.05.2024`.
8. To save the aggregate, click **Save**.
**Behavioral Data Hub > Live Aggregates > Create aggregate**.
2. As the aggregate type, select **Profile**.
2. Enter the name of the aggregate as `[UC]Number of products purchased after last finished quest`.
3. Click **Analyze profiles by** and select **Sum**.
4. From the **Choose event** dropdown, select the **product.buy** event.
5. As the event parameter, choose **$quantity**.
5. Click the **+ where** button and from the **Choose parameter** dropdown menu, choose **category** parameter.
6. From the **Choose operator** dropdown menu, select **Equal**.
7. Type the name of the product category - `Paper_towels`.
8. Click the **+ where** button and from the **Choose parameter** dropdown menu, choose **TIMESTAMP** parameter.
9. From the **Choose operator** dropdown menu, select **More than** number operator.
10. Click the 
(Choose value icon).
11. From the **Choose value** dropdown list, select the aggregate you created [earlier in the process](/use-cases/renewable-quest#create-an-aggregate-that-returns-the-timestamp-of-the-last-finished-quest).
12. Set the period for the aggregate to **Lifetime**.
13. Save the aggregate.
**Behavioral Data Hub > Expressions > New expression**.
2. Enter the name of the expression as `[UC]Target amount`.
3. Leave the **Expression** option at default **(Attribute)**.
4. Click the **Select** button.
5. Choose **# Constant**.
6. Open the settings of Constant value by clicking `0`.
7. In the field below, type `10`
8. Click **Save**.
The logic in the expression compares the number of products purchased after the last finished quest to the target amount, which is 10 units needed to complete the quest. There are two possible scenarios:
If the number of products purchased in a single transaction exceeds the target of 10, the surplus is not carried over to the next quest.
**Behavioral Data Hub > Expression > New expression**.
2. Enter the name of the expression as `[UC]Products purchased`
3. Leave the **Expression** option at default (**Attribute**).
4. Build the following formula of the expression:
The expression will produce one of two results based on certain conditions:
**Behavioral Data Hub > Expression > New expression**.
2. Enter the name of the expression as `[UC]Comparing amount of products bought`
3. Leave the **Expression** option at default (**Attribute**).
5. Build the following formula of the expression:
**Automation Hub > Workflows > New workflow**.
2. Enter the name of the workflow as `[UC]Renewable Quest`.
### Define the Profile Event node
---
The workflow will be triggered by the `product.buy` when customers will purchase any product from the `Paper_towels` category.
1. As the first node of the workflow, add **Profile Event**.
1. From the **Choose event** dropdown menu, choose the `product.buy` event,
2. As the parameter, choose **category**,
3. As the operator, choose **Equal**,
4. As the value of the parameter, add `Paper_towels`,
2. Confirm by clicking **Apply**.
{
"gameName": "Towel's quest"
}
{
"gameName": "Towel's quest",
"points": 1000
}
**Data Modeling Hub > Documents > Add document**.
2. Enter the name for your document.
To create a document, you have to set up three steps of settings: audience, configuration, and schedule.
### Set up Audience
---
In the audience section, determine who will be the recipient of the document.
2. Click **Define**,
3. Select **Everyone**,
4. Save by clicking **Apply**.
{
"current_status": " {% expression %} 1c92f585-3342-4fbd-af05-93f53ebe5882 {% endexpression %} ",
"description": "Buy 10 product from towels category and get 1000 loyalty points",
"format": "stamps",
"image": "https://ecommerce.pl/media/catalog/product/towels/1/image/9df78eab33525d08d6e5fb8d27136e95/94989/regina-wish-recznik-papierowy-bialy-2-rolki-reczniki-papierowe-artykuly-higieniczne_0.jpg",
"name": "Towels",
"prize": "1000",
"prizeType": "points",
"target": "{% expression %} 930673cb-28d2-4a81-9100-7306bdfcce86 {% endexpression %}",
"visibility": "1"
}
