Jump to content
Deschutes Design Group LLC Open For Limited Support. All Other Services Closed Until August 2021. ×

Forums

Search In
  • More options...
Find results that contain...
Find results in...

"Discharge/ On Leave" status


Ignacio Pablo Duro
 Share

Recommended Posts

Hey everyone. 

Honestly I don't I remember if this feature is planned or not, but PERSCOM needs a way to identify certain status types as "discharged" or "On Leave" 

As long as the user is discharged or "on leave of abscense", the site admin should be able to apply certain rules like: 

  • No promotion eligibilty / positive actvion on discharge / LOA status
  • TIS/TIG count should freeze on discharge / LOA status
     

What do you think? Do you have any other considerations or rules that should apply to these statues?

Thanks.

Edited by Ignacio Pablo Duro
Link to comment
Share on other sites

  • Administrators

We can definitely add units/status to ignore to the promotion system however TIG/TIS would be difficult as we evaluate them off the promotion/induction dates. We would have to someway figure out how to keep track of such events so that we could subtract them from the overall time. Would be very difficult implementation.

  • Thanks 1

Owner
Deschutes Design Group LLC
email | [email protected]

Link to comment
Share on other sites

yes, I understand the complexity. Thanks for your answer

By definition, we do not delete any personnel file after discharge. We are interested in keeping a file of all our former members. This comes into direct conflict with the current PERSCOM approach. Probably we are not the only unit with this problem. 
Is there any other member of PERSCOM community who's facing the same situation? any ideas or workaround that could be implemented to solve this problem?

 

Link to comment
Share on other sites

5 hours ago, Ignacio Pablo Duro said:

yes, I understand the complexity. Thanks for your answer

By definition, we do not delete any personnel file after discharge. We are interested in keeping a file of all our former members. This comes into direct conflict with the current PERSCOM approach. Probably we are not the only unit with this problem. 
Is there any other member of PERSCOM community who's facing the same situation? any ideas or workaround that could be implemented to solve this problem?

 

@Ignacio Pablo Duro

We have the same issue where files are deleted after discharge. However, we have done a workaround of creating a discharged combat unit that is hidden and a discharged status that is not displayed anywhere. When we discharge them we keep the box ticked to keep their file but select their status and combat unit as discharged. This is the only way around it i have found.

 

@Jon Erickson back in perscom v1 days when you discharged someone it would remove them from everything but keep their file, i believe it just linked their forum id with a perscom id but removed them from been visible on everything. Is this possible to reimplement?

Edited by Ashton
  • Like 1
Link to comment
Share on other sites

  • 8 months later...
  • Administrators

Since LOA's are handle via a PAR in most circumstances, and are not an official feature of PERSCOM, there is no way to track these time changes. I can see it possibly being integrated into the Activity Tracker in which you can assign status/units as flags to keep track and then when a soldier is assign/or changed status, this change is tracked in separate database table that can be used to subtract from overall TIG. Etc... But then again, this would be difficult for TIG, since TIG changes when a promotion/demotion happens. Can anybody else talk through a better possible solution?

Owner
Deschutes Design Group LLC
email | [email protected]

Link to comment
Share on other sites

  • 4 months later...
On 8/11/2020 at 5:50 AM, Jon Erickson said:

Since LOA's are handle via a PAR in most circumstances, and are not an official feature of PERSCOM, there is no way to track these time changes. I can see it possibly being integrated into the Activity Tracker in which you can assign status/units as flags to keep track and then when a soldier is assign/or changed status, this change is tracked in separate database table that can be used to subtract from overall TIG. Etc... But then again, this would be difficult for TIG, since TIG changes when a promotion/demotion happens. Can anybody else talk through a better possible solution?

I'm not sure if I got this correctly but I read on a different topic the activity tracker runs on a task that adds TIS/TIG every day. We currently have it set so for example LOA is a separated combat unit. Can the implementation not have a setting where certain combat units are blacklisted from receiving TIS/TIG? We currently have the same issue with both LOA and Retired personnel. Both are defined as "Combat Units" in PERSCOM.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.