Answers.Body: <p>We were told that CiviHR should be a completely separate install to CiviCRM and that is being designed to work quite independently, so this is no surprise.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T13:56:36.700Z
Answers.Text: To clarify: it's a separate instance, but even for that instance, I'd like to be able to see, for instance, the list of activities with a contact. I'm aware that using "normal" civicase types and the HR ones are potentially a problem, but this isn't what I'm trying to do ;)
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T13:55:20.277Z
Answers.LastActivityDate: 2015-06-02T13:55:20.277Z
Answers.UserDisplayName: Jon-man
Answers.Body: <p>(Note: My comments are focused mostly on CiviHR &lt;=1.4; for 1.5+, I haven't followed as closely.)</p>
  
  <p>CiviHR is broken down into several different extensions. Each extension defines a different piece of the data-model/UI (eg for tracking job contracts or tracking qualifications). If you pick and choose these individually, it should be possible to load them onto a CiviCRM site without disabling/removing features.</p>
  
  <p>One extension, <code>org.civicrm.hrui</code>, is particularly opinionated and aggressive about reworking the UI. Its primary purpose is to reshape the overall user-experience for standalone CiviHR deployments -- emphasizing HR-specific elements, de-emphasizing fundraising-specific elements, tweaking phrases/word-choices. It fills a role similar to Drupal's <em>installation profiles</em>.</p>
  
  <p>If you're an experienced Civi implementer/consultant looking to add some HR elements to an existing Civi site, then you've probably used most of the same tricks as <code>hrui</code> (eg toggling components and toggling display preferences), and you'll probably disagree with some of the opinions in <code>hrui</code>. So skip it; you're not the target audience for that extension. Browse the list of extensions and pick the ones which are relevant.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T13:51:01.963Z
Answers.Text: Part of the difficulty is that each extension has a rather minimal description of what it does, and if it depends (or not) of other extensions ;)
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T14:51:50.027Z
Answers.Text: For examples, some extensions seem to expect extended demographics (I think, I had errors until I enabled it), but it contains ethnic fields, that are strictly controlled in France (to the point of not being able to use a HR software that has them)
Answers.UserDisplayName: Xavier
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-03T04:20:13.553Z
Answers.Text: A few high-level extensions -- ```hrui```, ```hrrreport```, ```hrsampledata```, ```hrstaffdir``` -- would have broad dependencies on other extensions. A few low-level extensions -- ```hrcaseutils```, ```reqangular``` -- may show up frequently as dependencies. Otherwise, there shouldn't be many dependencies.
Answers.UserDisplayName: Tim Otten
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-02T13:35:36.783Z
Answers.LastActivityDate: 2015-06-02T13:35:36.783Z
Answers.UserDisplayName: Tim Otten
Body: <p>So I'm trying to use civiHR. I understand that some features are still beta and some new custom screen don't work so well and I'm prepared to live with that</p>
  
  <p>What I don't understand is that civiHR disable existing features, eg:
  - list of the cases "recruitement" isn't displayed n the case tab 
  - activity tab removed</p>
  
  <p>Is this on purpose or a bug? I don't see the point of removing features that would still have a sense because HR introduces different workflows too.</p>
  
  <p>Is there a way to let the existing features of CiviCRM enabled, even when using civihr?</p>
  
Tags: <civihr>
Title: Is this expected that civiHR removes lots of features (eg activities and cases)?
ThreadText: # Is this expected that civiHR removes lots of features (eg activities and cases)?
  
  (Asked by: username_0 on 2015-06-02)
  
  So I'm trying to use civiHR. I understand that some features are still beta and some new custom screen don't work so well and I'm prepared to live with that
  
  What I don't understand is that civiHR disable existing features, eg:
  - list of the cases "recruitement" isn't displayed n the case tab
  - activity tab removed
  
  Is this on purpose or a bug? I don't see the point of removing features that would still have a sense because HR introduces different workflows too.
  
  Is there a way to let the existing features of CiviCRM enabled, even when using civihr?
  
  **Tags:** civihr
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2015-06-02. Score: 8 | Accepted answer
  
  (Note: My comments are focused mostly on CiviHR <=1.4; for 1.5+, I haven't followed as closely.)
  
  CiviHR is broken down into several different extensions. Each extension defines a different piece of the data-model/UI (eg for tracking job contracts or tracking qualifications). If you pick and choose these individually, it should be possible to load them onto a CiviCRM site without disabling/removing features.
  
  One extension, `org.civicrm.hrui`, is particularly opinionated and aggressive about reworking the UI. Its primary purpose is to reshape the overall user-experience for standalone CiviHR deployments -- emphasizing HR-specific elements, de-emphasizing fundraising-specific elements, tweaking phrases/word-choices. It fills a role similar to Drupal's *installation profiles*.
  
  If you're an experienced Civi implementer/consultant looking to add some HR elements to an existing Civi site, then you've probably used most of the same tricks as `hrui` (eg toggling components and toggling display preferences), and you'll probably disagree with some of the opinions in `hrui`. So skip it; you're not the target audience for that extension. Browse the list of extensions and pick the ones which are relevant.
  
  > **Comments:**
  > **username_0**: Part of the difficulty is that each extension has a rather minimal description of what it does, and if it depends (or not) of other extensions ;)  
  > **username_0**: For examples, some extensions seem to expect extended demographics (I think, I had errors until I enabled it), but it contains ethnic fields, that are strictly controlled in France (to the point of not being able to use a HR software that has them)  
  > **username_2**: A few high-level extensions -- ```hrui```, ```hrrreport```, ```hrsampledata```, ```hrstaffdir``` -- would have broad dependencies on other extensions. A few low-level extensions -- ```hrcaseutils```, ```reqangular``` -- may show up frequently as dependencies. Otherwise, there shouldn't be many dependencies.  
  
  ---
  
  ### Answer by username_1 on 2015-06-02. Score: 2
  
  We were told that CiviHR should be a completely separate install to CiviCRM and that is being designed to work quite independently, so this is no surprise.
  
  > **Comments:**
  > **username_0**: To clarify: it's a separate instance, but even for that instance, I'd like to be able to see, for instance, the list of activities with a contact. I'm aware that using "normal" civicase types and the HR ones are potentially a problem, but this isn't what I'm trying to do ;)  
  
  ---
  
  