Jon Erickson

@Benality[3SFG] are you currently utilizing the PERSCOM API?

I’ll look into this - could be a simple thing as the seconds of the record are off which causes it to show 11 months instead of 12.

@Benality[3SFG], are you saying you’d like the ability to sort the table based on a custom field you have for a personnel file?

To everyone affected by this IPB bug, please submit a support ticket, or reply if you have a current ticket open with your ACP login details. We have developed a plugin to specifically fix this bug that will work on IPB Cloud as well. Thanks. @Matthew Hawkins @ShawnJPN

If you are using IPB Cloud, you can attempt to contact Support and have them replace the file manually.

That shouldn’t happen. I’ll look into it.

Try to see if that’s the issue - remove yourself from the group that is restricted. It shouldn’t be that way, but just to test...

Are you in a group that does not allow admins to transfer personnel to combat units with admin privileges?

Yeah that’s fine. I’ll just install an older version. Thanks.

@Matthew Hawkins @ShawnJPN no problem. When we pass our local tests, will be happy to use cloud hosted clients to test as well 👍🏻

That actually would be great @Ashton. I think I've addressed the issue. It is a bazaar one. But essentially the .json file holding the ACP restrictions appears to get corrupted through the installation routine. I'd like to test a fresh install and an upgrade if possible.

@Matthew Hawkins, check your Support Request. I sent you an update. I think I have identified the issue. I need a client who is experiencing this issue to contact me so I can validate the bug as I am having difficult replicating it. Preferably a client who does not use IPB Cloud but uses self-hosted...

And using Pages is probably the better option in this case. It is designed for this exact workflow.

TIS/TIG determination is not based on a task - just a simple computation of dates. Current date, last promotion date and enlistment date.

Next release!

Hi @ShawnJPN, we are working through an active bug that is preventing you from assigning granular permissions using the native permission system. We hope to have it fixed next release.

The PERSCOM Setup Fee is a onetime initial purchase price for the software. We wish we could rename the fee as it doesn’t quite align with the purpose, but we are limited to the software we use. From then on, PERSCOM is $10/month.

@Rotten, the integration allows you to override a users avatar and use their rank from PERSCOM automatically. It also adds the ability to display several other PERSCOM profile characteristics alongside any post they make.

Guess what! It does. Visit the API section of your IPB ACP to generate an API Key and view the documentation on all the available routes. It hasn’t been fully developed but the core components are in place.

I like the idea of expanding the notes. I will definitely include your recommendations. As for the PSA feature, I like as well. We are actively working on a application wide event system that will allow you to create custom actions that execute on events emitted. This will allow you to do the same exact thing. Adding a queue is a great addition to this. Thanks for the suggestions!

That’s correct. That is an error from AWS S3 letting you know the images are not accessible. The S3 bucket needs to be set to public. Also, this is not a PERSCOM error but rather related to your file storage settings in IPB.

Absolutely. You’ll need to edit the template file where the image is displaying and add in some custom CSS to change the size.

As @Ashton mentioned, you can create a Personnel Action Report with all the fields mentioned above. This form will then be accessible in the operations center for members to fill out.

No problem, we can add it in.

Technically speaking, every template can be completely customized to display however you’d like. In this example, it would take a tremendous amount of customization but probably could be doable.