Answers.Body: <p>I have done this a long time ago but it was very specific to the org's workflow. It involved a custom activity type, some autoupdating of a pdf template, and then an internal approval -> email -> offline vendor signature -> email/fax -> inbound civi email processor.</p>
  
  <p>I'm not sure if cases would add anything unless there's more going on too.</p>
  
  <p>You've said wordpress but possibly drupal webform plus this <a href="https://civicrm.org/blog/mattwire/electronic-signing-with-drupal-webform-and-civicrm" rel="nofollow noreferrer">online signatures</a> addon could be useful, i.e. the PO is a webform, and then it gets signed online by the vendor and stored in civi.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-23T13:39:44.347Z
Answers.Text: Utilizing Activities alone is an interesting idea to keep it simple.  However, Cases can allow more roles, deeper automation, and templates of checklists of multiple activities that each have their own automated follow-up reminders.  This raises the KISS conundrum.
Answers.UserDisplayName: G H
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-02-11T18:54:58.270Z
Answers.Text: maybe if you can spell out the likely workflow in the original question. my initial thought was Activities could deliver without the added layers of Cases.  But i tend to work with Drupal too and therefore combinations of Views and Webforms add a lot of capabilities to such workflows
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-23T03:44:33.347Z
Answers.LastActivityDate: 2020-01-23T03:44:33.347Z
Answers.UserDisplayName: Demerit
Body: <p>I did a quick search, but only found the reverse about allowing registrations to accept incoming PO numbers.  We are looking to implement Purchase Order Forms internally, and wondering if anyone else has done so?  Cases seems like a pretty logical place to do this, but I'd love to hear about other potential possibilities.  Or if it's a terrible idea, give me some why's.  Shouldn't matter, but this is a WordPress install.</p>
  
Tags: <wordpress>
Title: Managing internal Purchase Order forms/requests in CiviCRM
ThreadText: # Managing internal Purchase Order forms/requests in CiviCRM
  
  (Asked by: username_0 on 2020-01-23)
  
  I did a quick search, but only found the reverse about allowing registrations to accept incoming PO numbers. We are looking to implement Purchase Order Forms internally, and wondering if anyone else has done so? Cases seems like a pretty logical place to do this, but I'd love to hear about other potential possibilities. Or if it's a terrible idea, give me some why's. Shouldn't matter, but this is a WordPress install.
  
  **Tags:** wordpress
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-01-23. Score: 0
  
  I have done this a long time ago but it was very specific to the org's workflow. It involved a custom activity type, some autoupdating of a pdf template, and then an internal approval -> email -> offline vendor signature -> email/fax -> inbound civi email processor.
  
  I'm not sure if cases would add anything unless there's more going on too.
  
  You've said wordpress but possibly drupal webform plus this [online signatures](https://civicrm.org/blog/mattwire/electronic-signing-with-drupal-webform-and-civicrm) addon could be useful, i.e. the PO is a webform, and then it gets signed online by the vendor and stored in civi.
  
  > **Comments:**
  > **username_0**: Utilizing Activities alone is an interesting idea to keep it simple.  However, Cases can allow more roles, deeper automation, and templates of checklists of multiple activities that each have their own automated follow-up reminders.  This raises the KISS conundrum.  
  > **username_2**: maybe if you can spell out the likely workflow in the original question. my initial thought was Activities could deliver without the added layers of Cases.  But i tend to work with Drupal too and therefore combinations of Views and Webforms add a lot of capabilities to such workflows  
  
  ---
  
  