An interesting thing happened on eServices sometime last night to myself and several members in my squadron that may affect many of you as well. Our membership type was changed from Senior to Patron. I used the Help Desk to alert them to the problem and apparently there was a job performed last night that affected both membership type and applications for some members and that they are working on it. I just checked and everything seems to be in order now, but I wanted to find out if this was an isolated issue to my squadron and to alert you to check your accounts on eServices.
Dan- I heard this happened to 20 members in ND- you were not alone.
I got this E-mail today:
QuoteIf your e-services record states that you are a "Patron" and not a "Senior Member" your record has been effected by a 'bug' in the computer system at NHQ.
Please be advised that I was informed by Ms. Sharon Jackson at CAP NHQ personnel at 0900 hours this morning (1 May 2009) that a major error was created in the data base that contains all personnel records yesterday. I received an e-mail from CAP NHQ dated today at 0758 hours stating "Duty Position Removal" in the subject line but no further information or explanation. I logged on to e-services where my record had been changed from "Senior Member" to "Patron" and all of my duty positions and qualifications were missing. Ms. Jackson stated that this problem has effected many including several wing CCs and is being looked at currently. They expect to have this problem resolved shortly. I was told to call back on Tuesday if my record had not been restored.
The status of four cadet's GES showed up as blank yesterday and into the evening. I wonder if the glitch affected other parts of members' records?
FYI, one other glitch that I've seen lately is that when you transfer to another unit, any duty positions you held are removed. Not a biggie, but you get an email from NHQ saying that the duty position was removed BY THE PERSON WHO ASSIGNED IT, even if they aren't in that unit or no longer have permissions to do so.
Quote from: Senior on May 01, 2009, 09:41:05 PM
The status of four cadet's GES showed up as blank yesterday and into the evening. I wonder if the glitch affected other parts of members' records?
If you revert to Patron status, then goodbye staff assignments and OPS quals......Patron's don't get to have those.
Quote from: JoeTomasone on May 02, 2009, 02:53:32 AMFYI, one other glitch that I've seen lately is that when you transfer to another unit, any duty positions you held are removed. Not a biggie, but you get an email from NHQ saying that the duty position was removed BY THE PERSON WHO ASSIGNED IT, even if they aren't in that unit or no longer have permissions to do so.
Isn't that the way it should be? Assignments are made by the Commander of the unit of assignment and expire upon reassignment. The new commander has to make the new assignments, including WSA access and permissions.
I think the operative term here is "held". any duty position that you have been assigned to should remain in you eServices record. There is a place for current positions, and another for past positions. Current positions may zero out when the commander changes (or not), but the past positions shouldn't change.
YMMV.
The current design isn't for eservices to track your entire personnel history, but just your current assignment. If you look at the current Compliance Inspection guide they are really focusing on making sure that if someone no longer holds a position that it be taken out of eservices. Why? Probably because NHQ is using eservices designations to send out targeted email to folks about issues of concern to that position and don't want to send stuff to people who are no longer in a particular program.
Given how often people's duty assignment changes, I'm not sure its worth it at a national level to try to keep a complete history electronically.
Quote from: SarDragon on May 03, 2009, 04:39:32 AM
I think the operative term here is "held". any duty position that you have been assigned to should remain in you eServices record. There is a place for current positions, and another for past positions. Current positions may zero out when the commander changes (or not), but the past positions shouldn't change.
YMMV.
That's why you have Sims and CAPF 45's, etc. Total history is held locally. The E-services shows current assignments.
Quote from: Cecil DP on May 03, 2009, 03:44:11 AM
Quote from: JoeTomasone on May 02, 2009, 02:53:32 AMFYI, one other glitch that I've seen lately is that when you transfer to another unit, any duty positions you held are removed. Not a biggie, but you get an email from NHQ saying that the duty position was removed BY THE PERSON WHO ASSIGNED IT, even if they aren't in that unit or no longer have permissions to do so.
Isn't that the way it should be? Assignments are made by the Commander of the unit of assignment and expire upon reassignment. The new commander has to make the new assignments, including WSA access and permissions.
Yes, but what can be confusing is that if you got assigned by Maj Snuffy, who later steps down and becomes the Public Affairs Officer and is replaced as Commander by Capt Crunch, when you transfer, your duty assignment is listed as being cancelled by Maj Snuffy, who has no permissions to do so. eServices just pulls the name of the person who assigned you and feeds that back as the person who removed you instead of saying something like "You have been removed due from the duty assignment of ______ due to your recent transfer".
Depending on the reasons for transfer, it can make for some awkward situations ("Why is *HE* removing me??!!") unless you know what to expect.
Quote from: Cecil DP on May 03, 2009, 02:29:48 PM
Quote from: SarDragon on May 03, 2009, 04:39:32 AM
I think the operative term here is "held". any duty position that you have been assigned to should remain in you eServices record. There is a place for current positions, and another for past positions. Current positions may zero out when the commander changes (or not), but the past positions shouldn't change.
YMMV.
That's why you have Sims and CAPF 45's, etc. Total history is held locally. The E-services shows current assignments.
Au contraire. eServices now shows current,
and past assignments. They need to have been assigned in eServices, though. My unit has used it extensively.
The past part might not be as up-to-date as you might like, but it's there. Mine goes back a couple of years.
Quote from: SarDragon on May 04, 2009, 07:34:34 AM
Quote from: Cecil DP on May 03, 2009, 02:29:48 PM
Quote from: SarDragon on May 03, 2009, 04:39:32 AM
I think the operative term here is "held". any duty position that you have been assigned to should remain in you eServices record. There is a place for current positions, and another for past positions. Current positions may zero out when the commander changes (or not), but the past positions shouldn't change.
YMMV.
That's why you have Sims and CAPF 45's, etc. Total history is held locally. The E-services shows current assignments.
Au contraire. eServices now shows current, and past assignments. They need to have been assigned in eServices, though. My unit has used it extensively.
The past part might not be as up-to-date as you might like, but it's there. Mine goes back a couple of years.
Goes back to at least 05, cuz it still has my original duty assignment from when i crossed into the dark side.
But when were you removed from that assignment? That's a more accurate dating.
Quote from: SarDragon on May 04, 2009, 08:09:23 AM
But when were you removed from that assignment? That's a more accurate dating.
Hm. April 06, when I moved to TN.
OK, so the info has been stored in the database for at least three years. The presence of the "past" listing is recent. An additional feature.
I just found a 2006 Duty Position Report that has assignment dates as far back as Aug 2004. Since there are many entries with the same date, I'm thinking that's when the tracking started.
YMMV.
I just found out that our Wing CC became a Patron in the glitch.....
Wonderful e-services also erased the pilot quals of a few of our pilots up here. Including the Wing Stan Eval guy and his flock of assitant flying monkeys, myslef included. It took a few hours to get it back in there.
All in All it is a very poorly designed site.
Quote from: AlaskanCFI on May 06, 2009, 12:33:36 AM
All in All it is a very poorly designed site.
Sooooooo true!