Primary Group Management

[Arthur Cantu]

When soldiers are added to the roster or moved to new combat units, their secondary group is changed.

I would like the ability to either manage the primary group while editing the soldier, or have it change automatically based on the perscom function being used (defaults editable in settings).

Example, we have 3rd Infantry Division, CSTAFF, and Civilian as Primary groups. All combat units are secondary groups. So upon enlistment, assign them automatically to 3rd ID group as Primary and any secondary groups as applicable (combat and admin).

In addition, upon discharge, change primary group back to civilian.

Edited September 19, 2018 by Arthur Cantu

[Alexander Koch]

I'd like to see this, too. I may have missed something, but I didn't see it implemented yet at least.

[Arthur Cantu]

As I am using the system, I find that this may not be as necessary as I initially thought. 
Secondary groups manage permissions just as well as primary groups. The only real difference a Primary group gives, and please correct me if I am wrong, is the display of that group around the site. Such as on posting, in the hovercard, and in the profile page. I have found that this is reasonable for us, as I have chosen to simply replace the primary group display in all of these locations with the soldier's combat position and unit. This option will be available in a future PERSCOM plugin.

This works for us and I imagine will for a majority of units as well. 

[Alexander Koch]

That might actually work even better! Thanks for the heads up, Arthur

[Jon Erickson]

Correct. I opted not to have PERSCOM manage primary groups as I believe in the long run, it would be better to leave each organization with their own ability to manage primary groups with PERSCOM managing the secondary groups. I believe this will help with better flow.

[Alexander Koch]

With that being said - is there a plan to have it be able to manage several secondary groups? We have a workflow that has a couple of secondary groups required, so it'd help us a lot.

[Arthur Cantu]

Not sure how your workflow is designed specifically, but enlistment application processing, File Assignments, editing Administrative Duty Assignments, and discharges all manage secondary groups automatically.

[Jon Erickson]

I'm working on developing a set of definable "actions" that can be applied to a PERSCOM process. So for example....you could set up your own custom action to 1. move a group, 2. change a status, and 3. add a service record entry and then after each PERSCOM process (promotion, demotion, award, assignment, etc), you can choose what happens by selecting one of your defined actions. I think this will help increase the flexibility and customizability of the system! So stay tuned!

[Alexander Koch]

I was thinking more of having a one-to-many relationship rather than one-to-one for assigning secondary groups, but not sure how feasible that would be.

[Jon Erickson]

Can you provide an example workflow so we have better understanding? Thanks 

[Alexander Koch]

Workflow was a bad word to use, my mistake. We have very granular permissions, so when someone gets in, they need a few groups - not just one. This means that once they get in, it would be optimal if those multiple groups were assigned.

Hope that is easier to understand, my mistake for using the word workflow in the first place.