Ignacio Pablo Duro Posted November 21, 2019 Share Posted November 21, 2019 (edited) 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 November 21, 2019 by Ignacio Pablo Duro Quote Link to comment Share on other sites More sharing options...
Administrators Jon Erickson Posted November 21, 2019 Administrators Share Posted November 21, 2019 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. 1 Quote Owner Deschutes Design Group LLC email | jon@deschutesdesigngroup.com Link to comment Share on other sites More sharing options...
Ignacio Pablo Duro Posted November 28, 2019 Author Share Posted November 28, 2019 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? Quote Link to comment Share on other sites More sharing options...
Ashton Posted November 28, 2019 Share Posted November 28, 2019 (edited) 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 November 28, 2019 by Ashton 1 Quote Link to comment Share on other sites More sharing options...
Jannes Drijkoningen Posted August 10, 2020 Share Posted August 10, 2020 @Jon Erickson we would also love to see a TIG freeze for configurable combat units or statuses. IE if a soldier is assigned LOA/AWOL or other configurable status, OR a certain combat unit (like in the activity tracker) the TIG calculation is frozen. Quote Link to comment Share on other sites More sharing options...
Administrators Jon Erickson Posted August 11, 2020 Administrators Share Posted August 11, 2020 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? Quote Owner Deschutes Design Group LLC email | jon@deschutesdesigngroup.com Link to comment Share on other sites More sharing options...
Jannes Drijkoningen Posted January 10, 2021 Share Posted January 10, 2021 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. Quote Link to comment Share on other sites More sharing options...
Administrators Jon Erickson Posted January 10, 2021 Administrators Share Posted January 10, 2021 TIS/TIG determination is not based on a task - just a simple computation of dates. Current date, last promotion date and enlistment date. Quote Owner Deschutes Design Group LLC email | jon@deschutesdesigngroup.com Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.