CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Can timelines be calculated backwards from a future deadline?
Pages: [1]

Author Topic: Can timelines be calculated backwards from a future deadline?  (Read 1552 times)

marc

  • Guest
Can timelines be calculated backwards from a future deadline?
November 12, 2009, 03:23:50 am
Hi,

we want to implement a case for parliamentary reports, and the crucial information that we know is when it will be voted on. So rather than time the various activities starting from the opening of the case, we would like to set the future deadline, say 10th Dec, and schedule a reminder for 7 days before. Is it possible currently to do this with CiviCase, setting the date for a future event and scheduling other events backwards from there?

A second issue we have run into, is that the "client" for the case should be the report, rather than the rapporteur, or potentially it should be the committee that deals with it. From the posts in the forum, it seems that organisations still cannot be fully-fledged clients. Is this still the case, or have things changed since? Does anyone know a way to potentially work around this?

Thanks,

Marc

demeritcowboy

  • Ask me questions
  • ****
  • Posts: 570
  • Karma: 42
  • CiviCRM version: Always the latest!
  • CMS version: Drupal 6 mostly, still evaluating 7.
  • MySQL version: Mix of 5.0 / 5.1 / 5.5
  • PHP version: 5.3, usually on Windows
Re: Can timelines be calculated backwards from a future deadline?
November 12, 2009, 06:53:01 am
Don't know the current status of orgs as clients but two ideas for scheduling backwards:

1) It sounds like "start date" might not really have any meaning for you anyway, so if you just interpret start date to mean vote date and then put negative offsets in your timeline would that solve it?

2) You can have more than one timeline in your config file, so create the standard timeline to only have one additional entry for the vote activity, and create another timeline with your other activities and put <reference_activity> to be that vote activity and use negative offsets. Then after creating a case edit the date on the prepopulated vote activity, and choose add timeline from the manage case screen to add the second timeline.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Can timelines be calculated backwards from a future deadline?
November 12, 2009, 03:50:49 pm
Marc - The work to support organizations as clients has not been implemented yet. The original sponsor went with a different approach (and sponsored the contact subtype work for the upcoming 3.1 release). I think Michael McAndrew who is working with an organization that does "health-checks" for NGO's in the UK "may" be moving this forward in the near to mid-term.

http://wiki.civicrm.org/confluence/display/CRM/CiviCase+VAW+healthcheck+requirements

You might want to contact him and check on status.

Protect your investment in CiviCRM by  becoming a Member!

marc

  • Guest
Re: Can timelines be calculated backwards from a future deadline?
November 17, 2009, 07:35:48 am
Hi,

thanks guys. It hadn't occurred to me that I could use negative offsets, but I will certainly try out and let you know how it works. Nifty.

I will have a look at Michael's work, fortunately we should be able to work around it for now, although it is somewhat artificial.

Marc

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviCase (Moderator: Dave Greenberg) »
  • Can timelines be calculated backwards from a future deadline?

This forum was archived on 2017-11-26.