Managing Activities

When you initiate the creation of a new activity, you see a screen with several important sections. Each section has fields that must be filled out to define and configure your activity:

A unique identifier for the activity.

Ensures that each activity can be distinctly recognized and managed within the system.

A brief explanation of what the activity entails.

Helps users understand the purpose and scope of the activity at a glance.

This field links the activity to a specific function that is executed.

It is crucial to select an appropriate function with the correct API state (preferably API Active for productive use).

Recommended Initial State: Inactive.

By default, new activities should be set to Inactive. This allows for final checks and adjustments before the activity is made live.

You can later change the state to Active once everything is validated and ready for production.

This option allows you to document the expected duration of the activity in days.

The duration begins once you activate the environment and serves as a benchmark for tracking activity progress and identifying overdue tasks.

Within the activity creation process, there is an essential section called Operations where you define the actions that can be performed as part of the activity. These actions are critical for enabling interaction and ensuring the smooth execution of the activity's function.

The Operations section allows you to specify what actions users within a team can perform when the activity is executed. These actions include, but are not limited to:

Allows the team to execute the function linked to the activity.

This is the primary action that initiates the function’s operation.

Enables users to confirm the successful completion of the activity’s task.

Useful for validating that the intended outcome has been achieved.

Provides the option to reject or fail the activity if certain criteria have not been met.

Important for quality control and ensuring that only satisfactory outputs are accepted.

Displays data relevant to the activity.

This action is crucial for providing users with real-time information necessary for decision-making.

Allows users to bring external data into the activity.

Ensures that the activity has the most current and relevant data by enabling data import.

Allows user to lock the data for the specific selection (period, fiscal year, company, business unit, profit center, and so on).

Ensures data integrity and security.

This setting enables the system to send e-mail notifications whenever the status of an activity changes. It is particularly useful for keeping team members and stakeholders informed about the progress or any changes in the activities that they are involved in.

In the activity creation or configuration screen, you can select the send e-mail notification on the status change checkbox to enable e-mail notifications for that activity.

All users assigned to the Reader and Writer teams for the activity receive the e-mail notifications.

Reader Team: Users in this team have read-only or display permissions for the application, environment, or dataset.

Writer Team: Users in this team have permissions to edit and update the activity, making them directly involved in the activity execution and monitoring.