LogoLogo
timvero.comMaven Repository
  • timveroOS SDK guide
  • timveroOS how-to
  • timveroOS admin-side setup
  • Campaigns in timveroOS
    • 7.11
      • Business Context
      • Introduction
      • Core Concept
        • Entity Diagram
        • Lifecycle Diagram
        • Expression
      • Design and Development of the Campaign Model
        • Campaign model
        • Campaign repository
        • Campaign forms
        • Campaign сontroller
        • UI elements
        • Campaign actions
      • Design and Development of the CampaignExecution Model
        • CampaignExecution model
        • CampaignExecution repository
        • CampaignExecution controller
        • UI elements
      • Expression
      • Services
        • CampaignService
        • CampaignExecutionService
      • Campaign Processing
        • Producer
        • Consumer
      • Post-processing
        • Checker
Powered by GitBook
On this page
  • Main Idea
  • Key Components
  • Basic Flow

Was this helpful?

  1. Campaigns in timveroOS
  2. 7.11

Core Concept

Main Idea

This system manages marketing campaigns that target eligible clients. It handles both manual and scheduled automatic campaigns.

Key Components

  1. Campaign

    • Can be MANUAL (user-triggered) or AUTOMATIC (scheduled)

    • When active, automatic campaigns are SCHEDULED

    • When inactive, automatic campaigns are IDLE

    • Contains an Expression that defines client eligibility criteria

  2. Expression

    • Embedded script written in JavaScript or Python

    • Evaluates client data to determine eligibility

    • Example: client.creditScore > 700 && client.income > 50000

    • Allows business users to define complex targeting criteria without coding

  3. Campaign Execution

    • Represents a run of a campaign

    • Has statuses: NEW → IN_PROGRESS → FINISHED

    • May encounter errors (EXCEPTION_OCCURRED)

    • Contains a set of target clients filtered by the expression

  4. Execution Checkers

    • Observer pattern components that react to execution status changes

    • NotifyFailedChecker: Triggers when execution fails to notify administrators

    • CreateAppChecker: Creates applications when execution finishes successfully

Basic Flow

  1. Create and configure a campaign with eligibility expression

  2. Activate the campaign

  3. Execute the campaign (manually or automatically)

  4. System evaluates the expression against potential clients

  5. Only clients matching expression criteria are included

  6. When status changes, checkers automatically:

    • Create applications for successful executions

    • Send notifications for failed executions

  7. Deactivate when no longer needed

The system provides a powerful way to target specific client segments and automate the campaign execution process.

PreviousIntroductionNextEntity Diagram

Last updated 18 days ago

Was this helpful?