1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 |
# Resource Management System A Spring Boot-based Resource Management System for managing project resources, allocations, and availability. ## π Features - Add/Edit/Delete resources - Assign resources to projects - View availability calendar - Theme customization ## π Tech Stack - Java 17 - Spring Boot 3.0 - Spring Data JPA - MySQL - ReactJS (Frontend) - Maven ## π§± Architecture This is a typical Spring Boot + ReactJS full-stack application with a REST API backend and React-based frontend. ## βοΈ Getting Started ```bash # Clone the repository git clone https://github.com/yourusername/resource-mgmt.git # Navigate to the backend folder cd backend # Run the application ./mvnw spring-boot:run ``` ## π§ Configuration Example `application.yml`: ```yaml spring: datasource: url: jdbc:mysql://localhost:3306/resource_db username: root password: your_password ``` ## π‘ API Endpoints ```http GET /api/resources - Get all resources POST /api/resources - Add a resource PUT /api/resources/{id} - Update a resource DELETE /api/resources/{id} - Delete a resource ``` ## ποΈ Database Setup - Create a MySQL database named `resource_db`. - Use the provided `schema.sql` and `data.sql` to populate sample data. ## β
Testing ```bash ./mvnw test ``` ## ποΈ Build Instructions ```bash ./mvnw clean install ``` ## π€ Contributing Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. ## π License This project is licensed under the MIT License. ## π€ Contact Created by [Your Name] - feel free to contact me! |



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
private String calculateLastFormularyResetDate(BenefitCoverageRequest request) { // If formulary reset is not overridden, return null if (!request.isOverrideFormularyReset()) { return null; } // Formulary reset date is required when override is true LocalDate formularyResetDate = request.getFormularyResetDate(); if (formularyResetDate == null) { throw new IllegalArgumentException("Formulary reset date is required when override is true"); } // Extract month and day from formulary reset date int month = formularyResetDate.getMonthValue(); int day = formularyResetDate.getDayOfMonth(); // Get year from as of date LocalDate asOfDate = request.getAsOfDate(); int year = asOfDate.getYear(); // Calculate the formulary reset date using year from as of date LocalDate calculatedResetDate = LocalDate.of(year, month, day); // If as of date is before calculated reset date, subtract one year if (asOfDate.isBefore(calculatedResetDate)) { calculatedResetDate = calculatedResetDate.minusYears(1); } // Return in YYYY-MM-DD format return calculatedResetDate.toString(); } |
http://clarifyall.com/docs/rule-compass-system-main.zip
Regulatory Rules Maintenance
Filters Available:
- Rule Type
- MD State
- Ship to State
- Zip Code
- Channel
- Reg Cat Code
- Drug Schedule
- Refill #
- Quantity
- Days Supply
- User Location
- Dispensing Location
- Protocol
- Days Ago
- Max Days Supply
- Max Quantity
- Max Refill
- Max Days Allowed to Expiry Date
Functionalities:
- Filtering Rules:
- Users can apply multiple filters using dropdown checkboxes.
- Rules are displayed based on selected filters.
- Users can choose to Edit or Add new rules under filtered/unfiltered lists.
- Read and Write Access:
- The table initially loads in Read-Only Mode.
- User groups can be assigned Read or Write Access to modify regulatory rules.
- Rule Identifier:
- Rules need a GUID stored in the ERR database.
- There’s a question about maintaining Sequence Number from the CDE table for rules loaded from CDE.
- Actions Available:
- Add New Rule Type
- Edit Existing Rules
- Extract Data
Frontend (ReactJS)
- A table to display regulatory rules.
- A dropdown for filtering options.
- Buttons for Add, Edit, Extract functionalities.
- A form to add or edit rules.
Backend (Spring Boot)
- A REST API to serve JSON data (initially hardcoded).
- Endpoints for fetching, adding, and updating rules.
JSON File (Sample Data)
- Store rules data in a file (rules.json).
- ReactJS will fetch data from this file.