Administrators Jon Erickson Posted October 24, 2018 Administrators Share Posted October 24, 2018 PERSCOM 1.1.1 has been released and comes packed with several updates that you requested! It also fixes a licensing error that has recently popped up! Please download at your earliest convenience and report any critical bugs! Added Added the MemberFilter extension to allow filtering of soldiers in the Bulk Mail and Group Promotion features. Personnel File and Personnel Action Request Custom Fields now have assignable permissions. Prevent some groups from viewing certain data on your personnel file! Don't see a custom field? You may need to re-save the custom field's permissions to implement them! While were at it, Documents also have permissions now as well! Have a document that is just for your unit? Make sure the world doesn't see it! Don't use first and last names, but rather handles? Switch from managing a soldier's first and last name to a managing a single name. You can now change a soldier's supervisor when filing an assignment record. Documents has a new tag to display the new assignment supervisor. Choose which form fields you want to display on an Assignment Order in the settings menu. Set parameters for tasks to ignore while running such as soldier status and combat unit. Turn on application status change comments and have PERSCOM automatically post to your application forum topic when an application status is updated. Change the status of a soldier when they report in. If you change soldiers status when they miss a report in, this will allow PERSCOM to automatically change their status back when they report in. Set permissions on a Personnel Action Request Form specifying who can manage (approve/deny) specific form submissions. Changed Fixed a bug that prevented Personnel Action Request from being submitted if not all the fields were used on the form. If you delete a personnel action request custom field, it will now also delete it from any forms it is being used on. If a personnel action request form does not have a field yet, the language string won't appear empty in the table as it did before. The report in task no longer fails with an empty report in date. Enlistment service record entry now uses the application submission date rather then the date the application was processed. Assignment Orders changed a little in the sense that now each field will default to "Do not change" unless explicitly changed by the administrator. This forces the administrator to only specify what is changing in the assignment order rather than trying to set each field. If a field is marked "Do not change", it will use the current value of the soldier. Editing assignment orders will no longer change a soldier's personnel data. You must file a new Assignment Order every time you want to change the soldier's data. Notification emails now properly send. Quote Owner Deschutes Design Group LLC email | email@example.com Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.