Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Jon Erickson

  • Content Count

  • Joined

  • Last visited

  • Days Won


Jon Erickson last won the day on August 7

Jon Erickson had the most liked content!

Community Reputation

125 Excellent


Recent Profile Visitors

1753 profile views
  1. That’s correct - we will support IPB 4.5. I’m not sure on the timeline but it is a priority.
  2. We've got it in the works, it will be merged into the master branch soon. We've been addressing some important fixes/features in the mean time and have been working on this on the side.
  3. @Ashton, just be aware, if you adjust the order through the ACP GUI, your custom order ID's will all reset to default 🤦‍♂️
  4. Hey @Ashton, the ranks are not sorted based off their ID, but rather on the 'order' column. For example, a rank can have an order of '1' in one category, and an order of '1' in another category which makes it difficult to differentiate between categories. This is the default behavior of IPB.
  5. @Ashton, it appears everything is working correctly. Ranks only sort against other ranks in the same category. There’s no way for them to be able to tell their sorting against another rank in another category. They are essentially in their own environment.
  6. Hi Colton, at this time there is no “front end” qualification list such as awards. If there is much interest, we can consider adding it!
  7. @J.Drake Posted to the Beta club. Please test at your earliest convenience!
  8. As for what you saw in the promotions - it is triggering the save user object as I mentioned above and messing the uaergroups. I believe the promotion/demotion/assignment functions are working as intended.
  9. I think here the uniform upload has nothing to do with the bug you are experiencing but rather when the users object is updated and a database transaction is executed, it triggers the update user group function. Essentially whenever a save() is called on the soldier, there uaergroups are all set based on their rank, combat unit and administrative unit. So for you, you were just noticing it when uploading the uniform. I think I may have found the issue in the administrative units. Please actively test when I release the beta. I want to make sure its right before releasing. Thanks!
  10. Can you outline your exact keystroke flow that triggers this error?
  11. @J.Drake, we have it already fixed. You can anticipate release tomorrow, latest Thursday.
  12. I would rather stay away from managing primary groups as it presents much more risk in error on the backend side - such as removing administrators and causing lockups. Secondary groups is easier to manage. As for selecting multiple secondary groups, I don't see an issue with this. I will work on getting it incorporated.
  13. @J.Drake, we've identified this issue and will be releasing a hot fix to fix it!
  14. After a bit of a wait, we're excited to announce the release PERSCOM 1.3.5. Packed with several bug fixes and some new features, make sure to download and install this update as soon as possible. We've included our new Qualifications Module as well as Custom Name Displays. Change how your personnel are displayed throughout the site and adjust the settings to best match your preferences. Also, award your personnel unit specific qualifications and keep track of them in their personnel file! Head on over your Account to get the latest update. UPDATES: ### Added - Brand new qualification module let lets you assign and create qualification records for your personnel. - Minimum Time in Grade now displays on the ACP Rank list for easier identification. - Ranks can now be included/disregarded when calculating a soldier's promotion eligibility. - Customize how you want your personnel names to display throughout the PERSCOM system. Using interchangeable variables, create a customizable setup for your personnel. ### Changed - Awards, Ranks, Documents, and Qualifications must now exist in a Category. - PERSCOM now only uses our new licensing system. If you have an old license, please contact support to transfer immediately. - Small permission changes that allow for more granular access. ### Fixed - Fixed an erroneous error while displaying eligible soldiers for promotions. - Fixed a bug where custom personnel file fields weren't using the custom formatting value for their field. - Fixed the wrong soldier showing within the Operations Center Report In record. - Fixed an error where an assignment record is filed without setting the 'From Combat Unit' field. - Fixed a bug displaying personnel MOS statistics. - Fixed a bug when trying to report in from a notification and not properly updating the soldiers last report in date. - Fixed a bug when clicking Application Status and the application returned was not the latest application. - Fixed a bug when withdrawing an application threw an error if the forum for moving applications was not set. - Fixed a bug where errors were formatted improperly.
  15. @Ashton, this will be in the next release! Stay tuned!
  • 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.