Answers.Body: <p>A rule can't be created without indicating an explicit trigger - there is a cron job for CiviRules whose description reads: trigger civirules cron triggers.</p>
  
  <p>A few things about your condition: </p>
  
  <ol>
  <li>If you are not 100% sure that the created date will always equal the activity date, you're probably better off using the activity date instead since this is user-driven whereas created date is system-driven</li>
  <li>Using an operator of "Greater than or equal to" will allow you to capture any retroactively created/updated activities (another argument for using the activity date instead of the created date)</li>
  <li>"Compare Value" assumes system date, so it actually needs to be negative to compare the previous 90 days (when you save the condition, you will see the date 90 days ago listed as follows: Activity.activity_date_time >= YYYY-MM-DD). </li>
  </ol>
  
  <p>If you find that the activity based rule is not working out for you, you may wish to consider the development of custom triggers, conditions and actions as documented <a href="https://docs.civicrm.org/civirules/en/latest/create-your-own-introduction/" rel="nofollow noreferrer"><strong>HERE</strong></a>.</p>
  
  <p>Hope this helps,
  Tamar</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-28T21:48:04.507Z
Answers.Text: Thanks for the feedback Tamar. And for catching my date error! :-)
Answers.UserDisplayName: Elijah van der Giessen
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-27T00:59:50.100Z
Answers.LastActivityDate: 2018-09-27T00:59:50.100Z
Answers.UserDisplayName: Tamar Meir - Cividesk
Body: <p>I want to automatically move Contacts from my &quot;New Organizer&quot; group to my &quot;Active&quot; group 90 days after the Contact is ADDED to the &quot;New organizer&quot; group.</p>
  <p>I have created a pipeline to track the stages of my volunteer's involvement. I am triggering movement into each stage by manually setting an Activity Type and a Unique Activity Status for each stage of my pipeline. I'm then added people to groups based on their Activity Status using Civirules. This works great.</p>
  <p>But I also want to set rules that automatically move new and inactive volunteers into new groups.</p>
  <p>I can <em>almost</em> see the way there using Civirules, but don't see the option to do a Field Value Comparison on Date Added to Group (or Activity Created Date, which could be another option for me)</p>
  <h1>OPTION 1</h1>
  <p>LINKED TRIGGER: Daily trigger for group members</p>
  <p>FIELD VALUE COMPARISON: I can only select from Contact or GroupContact fields, so I can't proceed.</p>
  <h1>OPTION 2</h1>
  <p>LINKED TRIGGER: Activity Date reached ; Activity with type XX AND Status XX</p>
  <p>LINKED CONDITION: Field Value Comparison; Activity Created Date = +90 days
  <a href="https://i.sstatic.net/gfNNk.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/gfNNk.png" alt="Civirules field value comparison on activity created date" /></a></p>
  <p>LINKED ACTIONS: Remove Contact from initial Group; add Contact to new Group</p>
  <p>Is this going to work as I expect? Will the Civirule be activated without an explicit trigger to do the date comparison 90 days after the Activity Created Date?</p>
  
Tags: <activities><groups><civirules>
Title: Civirules: how to move contact into NEW group XX days after added to group
ThreadText: # Civirules: how to move contact into NEW group XX days after added to group
  
  (Asked by: username_0 on 2018-09-26)
  
  I want to automatically move Contacts from my "New Organizer" group to my "Active" group 90 days after the Contact is ADDED to the "New organizer" group.
  
  I have created a pipeline to track the stages of my volunteer's involvement. I am triggering movement into each stage by manually setting an Activity Type and a Unique Activity Status for each stage of my pipeline. I'm then added people to groups based on their Activity Status using Civirules. This works great.
  
  But I also want to set rules that automatically move new and inactive volunteers into new groups.
  
  I can *almost* see the way there using Civirules, but don't see the option to do a Field Value Comparison on Date Added to Group (or Activity Created Date, which could be another option for me)
  
  # OPTION 1
  
  LINKED TRIGGER: Daily trigger for group members
  
  FIELD VALUE COMPARISON: I can only select from Contact or GroupContact fields, so I can't proceed.
  
  # OPTION 2
  
  LINKED TRIGGER: Activity Date reached ; Activity with type XX AND Status XX
  
  LINKED CONDITION: Field Value Comparison; Activity Created Date = +90 days
  [![Civirules field value comparison on activity created date](https://i.sstatic.net/gfNNk.png)](https://i.sstatic.net/gfNNk.png)
  
  LINKED ACTIONS: Remove Contact from initial Group; add Contact to new Group
  
  Is this going to work as I expect? Will the Civirule be activated without an explicit trigger to do the date comparison 90 days after the Activity Created Date?
  
  **Tags:** activities, groups, civirules
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2018-09-27. Score: 1
  
  A rule can't be created without indicating an explicit trigger - there is a cron job for CiviRules whose description reads: trigger civirules cron triggers.
  
  A few things about your condition:
  
  1. If you are not 100% sure that the created date will always equal the activity date, you're probably better off using the activity date instead since this is user-driven whereas created date is system-driven
  2. Using an operator of "Greater than or equal to" will allow you to capture any retroactively created/updated activities (another argument for using the activity date instead of the created date)
  3. "Compare Value" assumes system date, so it actually needs to be negative to compare the previous 90 days (when you save the condition, you will see the date 90 days ago listed as follows: Activity.activity\_date\_time >= YYYY-MM-DD).
  
  If you find that the activity based rule is not working out for you, you may wish to consider the development of custom triggers, conditions and actions as documented [**HERE**](https://docs.civicrm.org/civirules/en/latest/create-your-own-introduction/).
  
  Hope this helps,
  Tamar
  
  > **Comments:**
  > **username_0**: Thanks for the feedback Tamar. And for catching my date error! :-)  
  
  ---
  
  