Change Summary
Last updated: 10/18/2019
The following is a summary of the changes for this project.
System | Change Description |
---|---|
API | Accept true 5-digit club numbers and 10-digit agreement numbers in the URI (true means that the number must begin with 1-9; it has no leading zeros). Also, continue to allow traditional 4-digit club numbers and 9-digit agreement numbers. |
Auto Updater | Increase the club number field length to 5 digits in the database. |
CRS | Enable reports to dynamically change the length of the club and agreement numbers. |
Dashboard | In situations where the Dashboard displays the club number instead of the club short name (when there is no club short name in the database), display the entire 5-digit club number as long as it begins with the numbers 1-9 (no leading zeros). |
DataTrak | Increase the club number field to 5 digits and the agreement number field to 10 digits. Wherever manual entry of a club number is required, a 5-digit number must be entered with leading zeros if necessary. If manual entry of an agreement number is required, a 10-digit number must be entered with leading zeros if necessary. |
DataTrak Reports | If the club number begins with zero, drop the leading zero when generating the report; if the club number has 5-digits beginning with the numbers 1-9, the full club number will be displayed on the report. |
Door System | The 2.0 Door will leverage the club number from the local database's config table to call REST APIs for multiple endpoints. The local app running on the client's machine for the 2.0 Door will not be updated. |
Employee Portal | Continue to display the Club Name from DataTrak and the member's barcode as usual. The length of the member's barcode will not be changed; its length will remain as is. |
Hardware Services | Keep the existing Hardware Services configuration’s club number at 4 digits. Any new Hardware Services configuration’s club number can be 4 or 5 digits. |
MFEE | When creating a new workstation, you must enter a 5-digit club number, with leading zeros, where applicable (EX: 00012, 09003, 12345). |
MYiCLUBonline | Display the 5-digit club number and 10-digit agreement number. |
OAuth | Continue to echo back a 4-digit club number to the vendor unless the club number in the request is a true 5-digit number (EX: 12345). |
OBC | Continue to display the true club number and agreement number, as it does today, with no leading zeros. |
Payment Processing System | Expand the club number field from 4 digits to 5 digits, and the agreement number field from 9 digits to 10 digits. Generally, the club number will continue to be stored as a numeric value, which has no leading zeros. |