Adding Advanced Activity Rules

Overview

Important: This setup reflects Kizen’s default configuration, but your Admin may have customized your view or layout, so your columns or navigation may look different. If you’re using a trial version of the Kizen platform, some features may be limited.

This walkthrough shows you how to add Advanced Activity Rules using the Kizen UI. You’ll learn how to define rule conditions, apply logic, and specify which Activity fields are shown when those conditions are met, so Activities behave consistently during logging and submission.

Advanced Activity Rules are configured at the Activity Type level and take effect immediately once saved.

Before You Begin

Before adding Advanced Activity Rules, make sure the following are in place:

• You have Admin access to Activities

• The Activity Type includes:

  • One or more field types to use as rule conditions

  • The Activity fields you want to show when conditions are met

• You understand that:

  • Each field can be controlled by only one rule

  • Rules explicitly define which fields are shown

  • Required fields are ignored if they are hidden by a rule

Having the Activity fields configured first ensures they appear as selectable options when defining rules in the Advanced Rules tab. See Activity Fields for more information.

---

1

Navigate to Advanced Rules

1. Go to Platform> Activities

2. Choose an Activity

3. Click on the Advanced Rules Tab

2

Create a Rule

• Click +Add Activity Rule

• Select a field from the When the following conditions are met dropdown

Note: You can add multiple condition fields by selecting the +Add Condition button. When multiple conditions are present, the rule specifies whether any or all of them must be met.

• Select an Operator (If required). ANY allows you to define the condition by OR. ALL allows you to define the condition by AND.

• Select a field from the Show the following field(s) dropdown.

3

Save and Test

• Save the Activity configuration, then log or schedule a test Activity to verify

• When you verify, check the following:

  • Field visibility changes correctly

  • Required fields behave as expected

  • Submission succeeds in all valid scenarios

---

Design Guidance and Best Practices

• Keep your rules simple and predictable

• Avoid chaining rules that are hard to reason about

• Use Dropdown fields for clear branching logic

• Test rules with different permission levels

• Avoid making read-only fields required

---

What's Next

Next, continue to Activities APIs & Webhooks, which provides an overview of all API endpoints and webhook events available for Activities. This section helps you understand:

• Which Activity operations are available via API

• How Scheduled and Logged Activities are exposed programmatically

• Which Activity lifecycle events emit webhook notifications

Reviewing the APIs and Webhooks overview prepares you to work with individual endpoints and event types in the sections that follow.

Related Topics

• Activities

• Activities Core Concepts

• Activities Data Model

• Activity Permissions

• Advanced Activity Rules

• Activities API & Webhooks