Subscribe to the SSDT Newsletter by clicking here. Your email will be added to a distribution list.
Quite a few irons in the fire!
Our development team are rock stars! Along with the improvements and enhancements they are continually making in the USAS-R and USPS-R projects, a few of our developers are working exclusively on our upcoming Redesign inventory and workflow projects.
Inventory
Our inventory project will be a separate application in the redesign with a slightly different look than what you are accustomed to seeing in USXS-R. Inventory will use a different version of Vaadin so the color scheme and screen formats will be somewhat different. We 're are very pleased with how the redesigned version is coming along and looking forward to providing a quick demo soon! We would also like to thank the members of our inventory focus group for providing such helpful feedback the past several months. The projected beta release for Inventory is scheduled for July 16th and will be available through August 16th which is when we officially release the production version of the application. SSDT will be working on the documentation and providing training to ITC support staff this summer before the production version is released. Be on the look out for a feature article and video demonstration on the Inventory project in a future SSDT Newsletter.
Workflows
The implementation of workflows in both USPS-R and USAS-R is progressing quickly. The first USPS-R workflow will be employee onboarding which is a process of entering a new employee in the payroll system. The first USAS-R workflow will focus on a requisition approval system. The projected beta release for both the employee onboarding and requisition approval workflows is scheduled for August 2021 with the production version planned for September 22, 2021. A purchase order workflow will follow shortly thereafter with future workflows being developed based on user feedback.
Importing POs and Invoices in USAS-R
The ability to post Purchase Orders and AP Invoices via CSV file is available! This feature is accessible via the Import button on the grids and works similarly to the Receipt import. For your convenience, please download the sample template PO upload and/or sample template AP Invoice upload spreadsheets containing the correct headings. For further information regarding formatting of the spreadsheet columns, required fields or creating your own custom spreadsheet, please refer to the 'Import Criteria' section in the Purchase Orders and AP Invoices documentation. Please note that any rules pertaining to Purchase Orders or AP Invoices will be applied during importing.
Once a spreadsheet has been saved as a CSV file, the following steps can be used to import Purchase Orders or AP Invoices:
- Click on
displayed at the top of the grid. Click 
and upload the spreadsheet. Clicking 
will process the file and post the transactions. - The popup will appear displaying the number of "Records Loaded" and "Errors". The process produces a results file named "USASLOADERR.CSV".
- If there were no errors, the file will say "No errors. Records loaded: #" where # is the number of records successfully loaded.
- If there are records that did not load, the file will contain only those records that did not load successfully and will provide error messages explaining why. You can make corrections to this file, save it as CSV and use it to upload the remaining transactions.
- Please note, as with the other import options, this feature is intended to allow users to mass create Purchase Orders and AP Invoices via the CSV file import. This feature will not allow updates to existing purchase orders or invoices.
Please click here for a quick video demonstration on mass importing purchase orders.
New Compensation Code
We recently added a field called 'Code' to Compensations.
When creating a compensation, you are required to add a Code.
For existing compensations, the patch associated with the JIRA issue update made defaults the code to the start date of the compensation in MMYYYY format followed by a dash and a random character. For example, 032021-A. If the Contract has no Start Date entered, the Code will show only a Letter. For example, A.
The code is modifiable. If you change it, it will only allow alphanumeric characters and dashes. The code is also unique per employee/position. If a position has multiple compensations, those compensations CANNOT have the same code.
When creating a New Contract for employee'semployees, a unique Code will be given to the New Contract after Activating in Compensations. The Code will resemble.
Mass Load Compensations
The Code field needs to be included when using Mass Load Compensations. For more information on this, please Click Here.
Useful links:
| borderColor | #008080 |
|---|---|
| titleColor | Black |
| titleBGColor | #008080 |
| title | Did You Know? |
When adding a compensation, you have to add a Code.
A new field called Code has been added to compensations. A patch was written to default the compensation code value. The patch will default the code on existing compensations to the start date of the compensation in MMYYYY format followed by a dash and a random character. For example, 032021-A. If the Contract has no Start Date entered, the Code will show only a Letter. For example, A 
The code is modifiable. If you change it, it will only allow alphanumeric characters and dashes. The code is also unique per employee/position. If a position has multiple compensations, those compensations CANNOT have the same code. The Code field is a required field.
- When creating a New Contract for employee's, an unique Code will be given to the New Contract after Activating in Compensations. The Code will resemble
- When creating a Contract or Non Contract Compensation manually the Code must be entered manually. The Code can be any combination of letters and numbers and can include hyphens. The code has to be unique for a given position, ie: position 1 can not have 2 compensations with code set to "FY21", but position 1 can have a compensation with code set to "FY21" and position 2 can also have a compensation with code set to "FY21"
This Code field needs to be included when using Mass Load Compensations. For more information on this, please Click Here.
REDESIGN STATUS | |
|---|---|
507 Sites Live on Redesign | 200 Total Wave 7 Sites |
17 Participating ITCs | 551 Total Districts Participating |
Please view the Current List of Districts & Status to see a comprehensive list of school districts along with their ITC, implementation status and the wave they are scheduled to migrate from Classic to Redesign.
The following terminology is used to determine where in the implementation process the entity is currently at:
Implementing: The ITC is running test imports and balancing reports on the entity. The district and ITC are working to schedule dates to begin dual processing and go live.
Paralleling: The entity is inputting all production transactions into both Classic and Redesign.
Live: The entity is using Redesign for production processing; no parallel processing is being performed; Classic is available in 'read-only' mode.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Save/Recall Feature (Lori and Amanda) Many canned reports have a Save/Recall feature that will allow you to create the setup of a report that you can use over and over again simply by using this Save and Recall option. The Save and Recall is available on all USAS-R Template Reports. Some of the USPS-R reports that offer this option are:
|
