id int64 3 994 | golden_business_rule stringlengths 89 4.82k | finetuned_model_prediction stringlengths 42 4.86k | finetuned_model stringclasses 1
value |
|---|---|---|---|
3 | # Business Rules: Monthly Profit Report
## Rule 1: Monthly Report Frequency
The Monthly Profit Report must be generated for each calendar month.
## Rule 2: Report Scope Based on Contract
- If a **contract exists** for a unit, the Monthly Profit Report **must be calculated per contract**.
- If **no contract exists**, ... | ### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### B... | businessrules/deepseek-br-qlora_exp2 |
5 | # Business Rules: Booking Extension
## Rule 1: Split Bookings
A booking that has been **split** must **not be extended**.
## Rule 2: Cancellation Status
A booking with status **"Cancelled"** or **"Scheduled for Cancellation"** must **not be extended**.
## Rule 3: No-Show Status
A booking with status **"No Show"** mu... | - A booking can only be extended if it is not cancelled, no show, or split.
- A booking can only be extended once.
- A booking can only be extended if it is not split.
- A booking can only be extended if it is not finalized.
- A booking can only be extended if it is not cancelled, no show, or split.
- A booking can onl... | businessrules/deepseek-br-qlora_exp2 |
6 | # Business Rules: Booking Splitting
## Rule 1: Split Date Validity
The split date must be selected and must fall after the booking's check-in date and before its check-out date.
## Rule 2: Required Fields for Splitting
When splitting a booking, the following must be selected:
- Property
- Unit Type
- Unit
## Rule 3:... | - A booking can not be split if it has been finalised.
- A booking can not be split if it has been marked as finalised.
- A booking can not be split if it has been finalised or marked as finalised.
- A booking can not be split if it has been finalised or marked as finalised.
- A booking can not be split if it has been ... | businessrules/deepseek-br-qlora_exp2 |
7 | # Business Rules: User and Staff Management
## Rule 1: Unique Email Address
A user's email address must be unique across all users, landlords (owners), and suppliers (companies). Duplicate emails are not allowed.
## Rule 2: Valid Role Assignment
Each role assigned to a staff member must match a valid role defined in ... | - A staff must have a unique email address.
- A staff must have a unique username.
- A staff must have a unique user ID.
- A staff must have a unique organization ID.
- A staff must have a unique team ID.
- A staff must have a unique calendar template.
- A staff must have a unique API key.
- A staff must have a unique ... | businessrules/deepseek-br-qlora_exp2 |
13 | # Business Rules: Rate Rule Currency Validation
## Rule 1: Currency Matching for Rate Plans
If a rate rule applies to specific rate plans and includes a currency, the currency must match the currency of each associated rate plan.
## Rule 2: Currency Requirement for Fixed Amount Adjustment
A currency must be specified... | - Each rate rule must have a currency.
- If the currency is not specified, a violation must be raised.
- If the currency is specified, the currency must be unique for each rate plan.
- If the currency is specified, the currency must be unique for each rate rule.
- If the currency is specified, the currency must be uniq... | businessrules/deepseek-br-qlora_exp2 |
14 | # Payment and Contact Integration Business Rules
- Each contact must be linked to its corresponding staff member.
- Each PayPal integration must include a client secret.
- Each PayPal integration must include a client ID.
- When a deal requires a custom gateway deposit, the landlord’s primary integration must se... | # Business Rules for PayPal Configuration
- PayPal configuration is managed by the organization.
- PayPal configuration is managed by the organization's integration partner.
- PayPal configuration is managed by the organization's integration partner's integration level.
- PayPal configuration is managed by the organiz... | businessrules/deepseek-br-qlora_exp2 |
18 | # Business Rules
## Contact Rules
- Each contact must be linked to its corresponding staff member.
## Tax Rules
- Each Tax Schema must have a defined rate; if no rate exists, the rate must be considered 0.
## Deal Rules
- Each deal with a custom investor gateway must be associated with that investor.
## Custo... | # Business Rules for Tax Schema
- Each tax schema must have a unique ID.
- Each tax schema must have a unique name.
- Each tax schema must have a unique rate.
- Each tax schema must have a unique description.
- Each tax schema must have a unique category.
- Each tax schema must have a unique type.
- Each tax schema mu... | businessrules/deepseek-br-qlora_exp2 |
21 | This snippet includes only technical behavior and implementation details; no business rules apply.
| # Business Rules for Creating Nightly Detail Tax Components
- Each message in the queue must be processed in order.
- If a message is not processed, it must be requeued.
- If a message is processed, it must be acknowledged.
- If a message is not processed, it must be rejected.
### END | businessrules/deepseek-br-qlora_exp2 |
23 | # Expense Excel Business Rules
## Deletion and Transfer Restrictions
- No Expense Excel record may be deleted if it contains any lines in the "Transferred" state.
- No Expense Excel record may be transferred if it contains any lines in the "Error" or "Warning" state.
- No Expense Excel record may be transferred if... | - A business rule is a set of conditions that must be met for a system to be considered valid.
- Business rules are used to ensure that the system is functioning correctly and that it meets the requirements of the business.
- Business rules are used to ensure that the system is secure and that it does not contain any s... | businessrules/deepseek-br-qlora_exp2 |
24 | # Rate Rule Business Rules
## 1. Priority
- Each rate rule must be applied according to its assigned priority, with higher-priority rules applied before lower-priority rules.
- Only rate rules that are not disabled may be applied.
## 2. Rate Rule Actions
- Each rate rule that changes a rate must adjust the price ... | ### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### B... | businessrules/deepseek-br-qlora_exp2 |
26 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| - An agency must have a unique name and code.
- An agency cannot be created with a name or code that already exists.
### END | businessrules/deepseek-br-qlora_exp2 |
35 | # LTSA Business Rules
## 1. Title Summary Rules
- A Title Summary may only be retrieved for a valid Parcel Identifier (PID).
## 2. Title Order Rules
- Each Title Order must be based on a Title Summary issued by LTSA.
- Each Title Order must include the Title Number provided by LTSA.
- Each Title Order must incl... | - Business rules for processing an LTSA request for a specific parcel identifier.
### End of Instruction:
### END | businessrules/deepseek-br-qlora_exp2 |
37 | # Notification Update Rules
- Each CHES status must correspond to one valid notification status.
- A notification’s status must not be updated if the CHES status is unrecognized.
- Notifications in Pending or Accepted status may be updated with new status from CHES.
- Notifications in final statuses (Cancelled, ... | - Business rules for updating notification status based on CHES status.
- Business rules for cancelling notifications based on CHES status.
- Business rules for resending notifications with new properties.
### End Instruction:
### End of Instruction:
### End of Instruction:
### End of Instruction:
### End of Instructi... | businessrules/deepseek-br-qlora_exp2 |
43 | # Property Business Rules
## Property Access and Visibility
- Users may only view a property if they are the owner or have been explicitly granted viewing rights.
- Only properties marked as published may be made visible to users.
## Property Information
- Each property must display the total number of associated... | # Business Rules for Property Search
- A user must be able to search for properties by city, state, and/or zip code.
- A user must be able to view a map of all properties.
- A user must be able to view a property's details and similar properties.
- A user must be able to view a property's details and similar propertie... | businessrules/deepseek-br-qlora_exp2 |
44 | # Similar Properties Business Rules
- Similar properties may only be suggested if the feature is enabled.
- Similar properties should be identified primarily within the same neighborhood as the current property, when applicable.
- If no similar properties exist in the same neighborhood, similar properties should b... | - Business rules for similar properties
- Business rules for similar properties must be implemented by the following code:
- Similar properties must be found in a small area if the property is located in a neighborhood.
- Similar properties must be found in a larger area if the property is located in a distri... | businessrules/deepseek-br-qlora_exp2 |
48 | # User Registration Business Rules
- Existing users may not register again.
- User registration is only allowed when registration is enabled.
- A successfully registered user must have a profile created and linked to their account.
- A successfully registered user must receive a confirmation email.
- A usernam... | - Business rules for the registration form must be extracted and displayed in a bulleted list.
- Each bulleted list item must be preceded by a number.
- Each bulleted list item must contain a description of the business rule.
- The business rules must be limited to the business rules implemented by the registration for... | businessrules/deepseek-br-qlora_exp2 |
55 | # Business Rules for Channel Manager Integration
## Property and Unit Type Synchronization
- Each property may be synchronized with the channel manager to establish or update its external representation.
- Each unit type may be synchronized with the channel manager to establish or update its external representation.
... | - A channel manager can connect to a channel for a property.
- A channel manager can disconnect from a channel for a property.
- A channel manager can map a rate plan to a channel room type for a property.
- A channel manager can unmap a rate plan from a channel room type for a property.
- A channel manager can map a r... | businessrules/deepseek-br-qlora_exp2 |
60 | # Business Rules for Expense Excel Import and Transfer
## 1. Expense Excel Processing Workflow
- An expense Excel file must be validated before processing.
- The status of an expense Excel file must be set to "PROCESSING" during transfer and updated to "OK" upon successful completion.
## 2. Expense Line Date Defaults... | - Business rules for transferring expenses from an Excel file to a database.
### End of Instruction:
### END | businessrules/deepseek-br-qlora_exp2 |
62 | # Business Rules for Occupancy Rate Calendar Navigation
1. Only active properties belonging to the current organization must be considered when generating occupancy rate calendar navigation options.
2. Each city with at least one eligible property must be represented as a selectable option in the occupancy rate calend... | - Business rules for the occupancy rate calendar navigation menu.
### END | businessrules/deepseek-br-qlora_exp2 |
68 | # Business Rules for Company Details Submission
1. The company name, address, city, postal code, region, and country must be provided for each organization.
2. The company’s contact information must include a valid email address and phone number.
3. The company’s website address must be included if available; otherwis... | - Business rules for filling company details for a user's organization.
- Business rules for filling company details for a user's organization.
- Business rules for filling company details for a user's organization.
- Business rules for filling company details for a user's organization.
- Business rules for filling com... | businessrules/deepseek-br-qlora_exp2 |
82 | # Business Rules for Sending Notifications
## Property Selection Rules
- Only properties marked as favorites within the current organization may be selected for notification purposes.
## Automated Message Selection Rules
- Only automated messages that are marked as favorites, not archived, and belong to the current o... | - Business rules for sending notifications to guests for a property.
- Business rules for sending notifications to guests for a property.
- Business rules for sending notifications to guests for a property.
- Business rules for sending notifications to guests for a property.
- Business rules for sending notifications t... | businessrules/deepseek-br-qlora_exp2 |
95 | # Business Rules for Customer Invoice Management
## Access and Authorization Rules
1. A user must have appropriate permissions to view or download a customer invoice.
2. A user must have appropriate permissions to post a customer invoice to Xero.
3. Only authorized users may void a customer invoice from Xero.
## Invo... | - A customer invoice can only be voided if it is in a draft state.
- A customer invoice can only be voided if it is in a posted state.
- A customer invoice can only be voided if it is in a complete state.
- A customer invoice can only be voided if it is in a draft state.
- A customer invoice can only be voided if it is... | businessrules/deepseek-br-qlora_exp2 |
98 | # Business Rules for Stripe Configuration
## 1. Stripe Secret Key Usage
- Organizations with a Stripe integration must use the appropriate secret key based on whether the integration is for production or testing.
- If no specific integration is provided, the organization must use its default Stripe configuration.
... | - Business rules for Stripe integration
- Business rules for Stripe integration for organization
- Business rules for Stripe integration for organization for release date
- Business rules for Stripe integration for organization for release date for Stripe account ID
- Business rules for Stripe integ... | businessrules/deepseek-br-qlora_exp2 |
103 | # Business Rules for Booking Task Management
- When a booking is inserted, the dates of tasks related to both the previous and current bookings must be updated accordingly.
- When a booking is canceled, all tasks associated with that booking must be recalculated. If the booking was an extension of another booking, tas... | # Business Rules for Booking Tasks
- Each booking must have a task associated with it.
- Each task must have a subject associated with it.
- Each task must have a start date associated with it.
- Each task must have an end date associated with it.
- Each task must have a frequency associated with it.
- Each task must ... | businessrules/deepseek-br-qlora_exp2 |
107 | # Business Rules for Property Unit Selection
*No business rules are defined for Property Unit Selection in this code. The implementation only concerns technical configuration and user interface behavior.* | # Business Rules for Property Unit Selection
- Each property unit must have a unique name.
- Each property unit must have a unique ID.
- Each property unit must have a unique code.
- Each property unit must have a unique description.
- Each property unit must have a unique display name.
- Each property unit must have ... | businessrules/deepseek-br-qlora_exp2 |
108 | # Business Rules for Booking Income Report Export
The following rules define the required data elements and structure for each exported booking income report record.
## Booking and Channel Information
- Each booking income report record must include the booking ID and booking number.
- Each record must specify the c... | - Business rules for the business logic of the file export of booking income report.
### End Instruction:
- End the instruction for extracting business rules from the code.
### END | businessrules/deepseek-br-qlora_exp2 |
109 | # Business Rules for Automated Message Trigger Rules
## Condition Assignment and Management
- When updating automated message trigger rules, all existing conditions associated with the message must be removed before assigning new conditions.
- Each automated message may have multiple conditions and timing rules assign... | - All popup options must be returned in a JSON format.
- Each popup option must contain the following information:
- Name
- Group Name
- Variables
- Operator 1
- Operator 2
- The main body of the JSON must contain the following information for each popup option:
- Name
- Group Name
- Variables
- Opera... | businessrules/deepseek-br-qlora_exp2 |
112 | # Business Rules for Rentals United Manager
*No explicit business rules are defined at the business policy level in this section. All logic pertains to form structure, field requirements, and presentation details.* | # Business Rules for Rentals United Manager
- Each manager must implement the `RentalsUnitedManagerTrait` trait.
- Each manager must have a constructor that takes the following arguments:
- `BrandService`
- `ChannelRateLogService`
- `ConfigManager`
- `EntityManagerInterface`
- `LocationAssignmentService`
-... | businessrules/deepseek-br-qlora_exp2 |
122 | # Business Rules for Booking Order Line Breakdowns
## 1. Addon Line Classification
- Each booking order line breakdown must be classified as either an addon line or a main line based on whether it includes an addon.
## 2. Date Range Relevance
- Addon breakdowns must correspond to the relevant date range for the... | - Business rules for booking order line breakdowns
- Business rules for addon lines
- Addon lines must be associated with a booking order line
- Addon lines must have a non-null addon
- Business rules for main line breakdowns
- Main line breakdowns must be associated with a booking
- Main line break... | businessrules/deepseek-br-qlora_exp2 |
125 | # Business Rules for Messaging API Push Normalization
- Only message line entities may be processed for outgoing messages.
- Each outgoing message must include the response content in the message body.
- If a message includes attachments, each attachment must include its file name and the file content encoded in b... | - Business rules for the business logic of the messaging API push normalizer.
### END | businessrules/deepseek-br-qlora_exp2 |
131 | # Business Rules for Key Place Profile Management
## Ownership Rules
- Each new Key Place Profile must have an assigned owner.
- The owner of a newly created Key Place Profile must be the current organization user at the time of creation.
## Access Control Rules
- Users must have the appropriate permissions to view, ... | # Business Rules for Key Place Profile
## Business Rules for Key Place Profile
### Business Rules for Key Place Profile
- Each key place profile must have a unique name.
- Each key place profile must have a unique description.
- Each key place profile must have a unique address.
- Each key place profile must have a ... | businessrules/deepseek-br-qlora_exp2 |
132 | # Business Rules for Payment Collection Metadata
- All payment and refund collections must include metadata that uniquely identifies each collection.
- The metadata must indicate the total number of items in the collection.
| # Business Rules for Payment Meta Data
- Payment meta data must be returned for each payment in a collection.
- Payment meta data must include the ID of the collection.
- Payment meta data must include the total number of items in the collection.
- Payment meta data must include the current page number in the collecti... | businessrules/deepseek-br-qlora_exp2 |
150 | # Business Rules For Booking Normalizer
## Guest Rules
- Each booking must calculate total guests as the sum of adult guests and child guests.
- Each lead guest must meet the property’s minimum age requirement.
- No guest may be accepted when the guest is below the minimum allowed age.
- Each booking must require docu... | ### End Instruction:
### Code:
// Snippet from: PMS-master\src\Peymans\Bundle\BookingBundle\Normalizer\BookingNormalizer.php
/**
* @param Booking $object
* @param $format
* @param array $context
* @return array|ArrayObject|bool|float|int|mixed|string|null
* @throws ExceptionInterface
... | businessrules/deepseek-br-qlora_exp2 |
154 | # Business Rules for Sending Transaction Data to Google
## Execution Rules
- The transaction data synchronization process must only run if the application URL is set to "https://hub.zeevou.com".
- The process must not run concurrently; only one instance may execute at a time.
## Data Transmission Rules
- For each Goo... | # Business Rules for Extracting Business Rules from a Cron Command
## Business Rules for Extracting Business Rules from a Cron Command
1. Each business rule must be a bullet point in Markdown format.
2. The business rules must be returned only for the cron command.
3. The business rules must not repeat the instructio... | businessrules/deepseek-br-qlora_exp2 |
157 | # Business Rules for Booking Retrieval via PriceLab Service
## 1. Access Control
- Only users with valid credentials (username and API key) may retrieve booking data.
## 2. Mandatory Parameters
- The following parameters are required to retrieve bookings:
- **listing_id** (unit type identifier)
- **start_date**
... | - Business rules for the "get bookings" endpoint
- The "get bookings" endpoint should only be accessible to users with the "view_bookings" permission.
- The "get bookings" endpoint should only be accessible to users within the same organization as the listing.
- The "get bookings" endpoint should only be accessib... | businessrules/deepseek-br-qlora_exp2 |
164 | # Business Rules for Property Normalization
## Ownership and Identification Rules
- Each property must have an owner assigned, and the owner's unique identifier must be retrievable.
- Each property must have a location assigned, and the location's unique identifier must be retrievable.
## Unit and Rate Plan Rules
- T... | - The business rules for the property normalizer are as follows:
1. The terms and conditions for the property must be displayed on the property page.
2. The terms and conditions for the property must be displayed on the property page.
3. The terms and conditions for the property must be displayed on the property page.... | businessrules/deepseek-br-qlora_exp2 |
167 | # Business Rules for Property Availability
- Each property must be identified and exist before availability can be determined.
- Availability data must be provided only for dates that are valid and within the specified range.
- The number of guests must not exceed the maximum capacity defined for each unit type.
- Onl... | # Business Rules for Property Availability Data Provider
- Each property availability must have a minimum stay of at least 1 night.
- Each property availability must have a maximum stay of at least 1 night.
- Each property availability must have a close to arrival stay of at least 1 night.
- Each property availability... | businessrules/deepseek-br-qlora_exp2 |
169 | # Business Rules for Nightly Detail Financial and Occupancy Reporting
## 1. Currency Determination
- All financial metrics in nightly detail reports must be calculated and displayed using the property's default currency.
- If a property's default currency is not set, the organization's default currency must be used.... | ### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### Business Rules:
### B... | businessrules/deepseek-br-qlora_exp2 |
176 | # Business Rules for Booking Creation and Order Management
## 1. Booking Creation and Assignment
- Each booking must be associated with a property, unit type, and, if applicable, a specific unit.
- The booking must record arrival and departure dates and times, guest counts (adults, children, infants), and booking stat... | - The business rules for adding a booking are as follows:
- The booking must be created with a guest, property, unit type, and channel.
- The guest must be associated with the booking.
- The property must be associated with the booking.
- The unit type must be associated with the booking.
- The channel must b... | businessrules/deepseek-br-qlora_exp2 |
181 | # Business Rules for Property Unit SU Synchronization
1. A property unit can only be disconnected from the SU system if the property is SU-enabled and both the property and unit type have valid SU Staah IDs.
2. If a property unit is disconnected, its status must be updated to "Deactivated" in the SU system.
3. If a pr... | # Business Rules for Property Unit Synchronization with Synchronization Unit Service
## 1. Property Unit Synchronization with Synchronization Unit Service
### 1.1 Business Rules for Property Unit Synchronization with Synchronization Unit Service
- **Business Rule 1:** Property Unit Synchronization with Synchronizati... | businessrules/deepseek-br-qlora_exp2 |
184 | # Business Rules for Message Insertion and Update
- Each newly created message must be included in the communication processing workflow.
- Each updated sent SMS message must remain included in the communication processing workflow.
| - Business rules for inserting messages into the database.
### End of Instruction:
### END | businessrules/deepseek-br-qlora_exp2 |
189 | # Business Rules for Payment Records
## Unallocated Payments
- Only payments created within the last six months may be considered for unallocated payment review.
- Only payments with a 3D state of "OK" may be considered for unallocated payment review.
- Only payments that are linked to a booking order may be consider... | - Business rules for unallocated payments in the last six months
- Business rules for payments with mismatched guest
### END | businessrules/deepseek-br-qlora_exp2 |
193 | # Business Rules for Bill Cost Allocation
## General Allocation Rules
1. Each bill cost allocation must be linked to its corresponding bill, organization, owner, and property unit.
2. If a bill is associated with a booking, the cost allocation must also reference that booking and its investor deal.
3. If no investor d... | - Each bill must be allocated to a property unit.
- Each bill must be allocated to a property.
- Each bill must be allocated to a multi-property unit.
- Each bill must be allocated to a unit type.
- Each bill must be allocated to a property unit.
- Each bill must be allocated to a property.
- Each bill must be allocate... | businessrules/deepseek-br-qlora_exp2 |
195 | # Business Rules for Unit Type Deletion
- A unit type must be validated for removal before it can be deleted.
- If a unit type cannot be removed due to business constraints, the deletion must be rejected with an appropriate error message. | # Business Rules for Unit Type Deletion
- Each unit type must have at least one unit.
- Unit types must be removed if they are not referenced by any units.
### END | businessrules/deepseek-br-qlora_exp2 |
204 | # Business Rules for Xero Application Integration
1. Only organizations without an existing Xero integration may create a new integration.
2. Each organization may disconnect its Xero integration at any time.
3. No organization may have more than one active Xero integration.
4. Each organization must have its Xero ... | # Business Rules for Xero Application Authentication
- ### Authentication URL
- The authentication URL is the URL that the user must visit to authenticate with Xero.
- The authentication URL should include a `code` parameter that the user must provide to complete the authentication process.
- The authentication ... | businessrules/deepseek-br-qlora_exp2 |
206 | # Business Rules for Booking Bedding Configuration
## Booking Bedding Configuration Rules
1. Each booking must have a bedding configuration that can be retrieved using the booking ID.
2. If a booking does not have a specific bedding configuration, the default bedding configuration of the associated unit type must be ... | # Business Rules for Booking Bed Configuration
## 1. Booking Bed Configuration Rules
### 1.1. Booking Bed Configuration Rules
- A booking must have a bed configuration if it has a bed configuration.
- A booking must have a bed configuration if it has a bed configuration.
- A booking must have a bed configuration if ... | businessrules/deepseek-br-qlora_exp2 |
209 | # Business Rules for Unit Type Rate
- Each Unit Type Rate must have an owner.
- When the "override rate rules" setting is enabled or disabled for a Unit Type Rate, the same setting must be applied to all of its rate lines.
- Each rate line added to a Unit Type Rate must inherit the current "override rate rules" setti... | # Business Rules for Unit Type Rate Log Model
- Each Unit Type Rate Log Model must have a unique ID.
- Each Unit Type Rate Log Model must have a unique owner.
- Each Unit Type Rate Log Model must have a unique selected data.
- Each Unit Type Rate Log Model must have a unique list of Unit Type Rate Log Lines.
- Each Un... | businessrules/deepseek-br-qlora_exp2 |
211 | # Business Rules for Review Creation
## 1. Review Property and Unit Assignment
- When a Review is created and linked to a Booking, the Review must inherit the Property, Unit Type, and Unit from the associated Booking if these fields are not already set.
## 2. Review Origin and Organization Assignment for Booking Eng... | # Business Rules for Review Entity
- Each Review entity must have a property and unit type associated with it.
- If a Review entity is associated with a Booking entity, the property and unit type must be set accordingly.
- If a Review entity is associated with a Booking entity, the organization associated with the Boo... | businessrules/deepseek-br-qlora_exp2 |
215 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | # Business Rules for Accounting Schema Default
- ### Business Rule 1: Accounting Schema Defaults Cannot Be Removed
- #### Business Rule Description
- Accounting Schema Defaults cannot be removed.
- #### Business Rule Preconditions
- The Accounting Schema Default must not be the default schema.
... | businessrules/deepseek-br-qlora_exp2 |
219 | # Business Rules for Booking Early Checkout
## Early Checkout Rules
- Each early checkout event must be associated with a specific booking.
- An early checkout event must record both the original departure date and the new (earlier) departure date.
- The new departure date must be earlier than the original departure ... | # Business Rules for Early Checkout
- A booking must have a departure date before its departure date.
- A booking must have a departure date before its departure date.
### End of Instruction | businessrules/deepseek-br-qlora_exp2 |
224 | # Business Rules for Tax Rate Management
## Tax Rate Application Rules
- A tax rate may only be applied to rate plans that exist and are valid.
- When applying a tax rate, only valid and existing rate plans must be associated with the tax rate.
## Tax Rate Deletion and Archiving Rules
- If any bookings exist that are... | # Business Rules for Tax Rate Service
- Each tax rate must have at least one rate plan.
- Each rate plan must have at least one tax component.
- Each tax component must have at least one cost element.
- Each additional tax component must have at least one additional tax.
- Each additional tax component must have a rel... | businessrules/deepseek-br-qlora_exp2 |
227 | # Business Rules for Cancellation Policy Terms
1. Each cancellation policy term must define the time intervals after booking and before check-in during which cancellation actions apply.
2. The cancellation conditions must be expressed as combinations of time intervals after booking and before check-in.
3. The cancella... | - The cancellation policy for human-readable terms must be implemented in a way that is consistent with the business rules for cancellation policies.
- The business rules for cancellation policies must be consistent with the business rules for human-readable terms.
- The business rules for cancellation policies must be... | businessrules/deepseek-br-qlora_exp2 |
233 | # Business Rules for Booking Event Processing
## 1. Check-In Type Handling
- When a booking's check-in type is set to **Keysafe** or **Code Entry**, an access code must be assigned to the booking.
- When a booking's check-in type is set to **KeyNest**, and the associated unit has available key sets, a key set assignme... | - Business rules for checking in and out of a booking
- Business rules for changing the price of a booking
- Business rules for cancelling a booking
- Business rules for changing the access code of a booking
- Business rules for changing the arrival and departure dates of a booking
- Business rules for changing the uni... | businessrules/deepseek-br-qlora_exp2 |
242 | # Business Rules for Bedding Configuration Conversion
1. Each room's bedding configuration must be converted according to the defined conversion process.
2. The conversion process must be applicable to all rooms that have not yet completed the bedding configuration conversion.
3. The conversion process may be limited ... | # Business Rules for Bedding Configuration Conversion
- All bed configuration conversion must be completed before any room can be converted.
- All bed configuration conversion must be completed before any room can be converted.
- All bed configuration conversion must be completed before any room can be converted.
- Al... | businessrules/deepseek-br-qlora_exp2 |
244 | # Business Rules for Rentals United Synchronization and Dictionary Management
- No dictionary item may be deleted while it is assigned to another entity.
| # Business Rules for Rentals United Dictionary Synchronization
- All dictionary types must be synchronized
- Dictionary types that are not synchronized must be created
- Dictionary types that are synchronized must be updated
- Dictionary types that are synchronized must be updated with the latest data
- Dictionary typ... | businessrules/deepseek-br-qlora_exp2 |
251 | # Business Rules for Worldpay CVC Payment Processing
## Booking Validation Rules
- A payment may be processed only if the associated booking exists.
- If the booking does not exist, the payment process must be terminated immediately.
## Token Requirement Rules
- A payment requires a valid payment token.
- If ... | - Business rules for payment by credit card using Worldpay's CVC payment method
### End of Instruction: | businessrules/deepseek-br-qlora_exp2 |
255 | # Business Rules for Payment Allocation Retrieval
## 1. Cancellation Penalty Payment Allocation
- Only payments with a type other than "Channel Payment" or "OTA Credit" and with a 3D state of "OK" may be considered as allocated payments for cancellation penalty for a booking.
## 2. OTA Credit Payment Allocation
- Onl... | # Business Rules for Payment Allocation
- Payment allocations must be allocated to a booking order line.
- Payment allocations must be allocated to a booking.
- Payment allocations must be allocated to a booking order.
- Payment allocations must be allocated to a payment.
- Payment allocations must be allocated to a p... | businessrules/deepseek-br-qlora_exp2 |
256 | # Business Rules for Cost Element Management
## Uniqueness and Identification
- Each cost element within an organization must have a unique combination of name and category.
- No two cost elements in the same organization may share the same name and category, except when validating the current record being updated... | # Business Rules for Cost Element Management
## Cost Element Management Rules
### Cost Element Management Rules
- Each cost element must have a unique name within its organization.
- Cost elements must have a category that is not a refund.
- Cost elements must have a formula keyword that is not a management fee or r... | businessrules/deepseek-br-qlora_exp2 |
262 | # Business Rules for Create or Select Inline Property Aware
This component does not define any business rules. All logic pertains to form configuration and user interface presentation. | - Business rules for creating or selecting an inline property-aware entity.
- Business rules for configuring the component options for the property-aware component.
- Business rules for building the view for the property-aware component.
- Business rules for configuring the extra configuration for the property-aware co... | businessrules/deepseek-br-qlora_exp2 |
264 | # Business Rules for Automated Message Query Generation
*No explicit business rules are defined at the business policy level in this section. All logic pertains to form structure, field requirements, and presentation details.* | - Business rules for the query generator service.
- Business rules for the join categories.
- Business rules for the join query.
- Business rules for the condition query generator.
- Business rules for the condition query generator for booking validation.
### END | businessrules/deepseek-br-qlora_exp2 |
265 | # Business Rules for Channel Manager Booking Conversion
- Only booking requests from approved channels may be converted to bookings.
- No booking request from an unapproved channel may be converted to a booking.
| # Business Rules for Booking Conversion
- Business rules for converting a booking request to a booking based on the channel manager.
1. If the channel manager is RENTALS_UNITED, the business rules for converting a booking request to a booking are as follows:
- The booking request must be associated with a propert... | businessrules/deepseek-br-qlora_exp2 |
270 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | - Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syncing history
- Business rules for syn... | businessrules/deepseek-br-qlora_exp2 |
274 | # Business Rules for Check-In Ready Settings and Booking Deposit Management
## Check-In Ready Settings
1. Each brand or organization may define check-in ready settings, including guest information requirements, terms and conditions, guest verification, payment, and security deposit policies.
2. When check-in ready se... | - Business rules for adding check-in ready settings for a brand.
- Business rules for retrieving check-in ready settings for a brand.
- Business rules for checking if an agreement is enabled for a brand.
- Business rules for checking if a booking is ready for check-in.
- Business rules for retrieving the subject and bo... | businessrules/deepseek-br-qlora_exp2 |
276 | # Business Rules for Booking Splitting
## Rule 1: Booking Split Creation
When a booking is split, a new booking must be created with its own property, unit type, unit, arrival date, and booking date, while retaining the brand and collection type of the original booking.
## Rule 2: Split Reference Linking
The new spli... | - Business rules for splitting a booking
- Business rules for changing the commission for a booking
- Business rules for updating the booking order lines
- Business rules for calculating the booking order lines based on the rate plan
- Business rules for updating the arrival and departure dates of a booking
- Business ... | businessrules/deepseek-br-qlora_exp2 |
285 | # Business Rules for Booking Creation and Update
## Booking Status and Access Rules
1. **Locked Bookings:** A booking that is finalized or locked cannot be edited or updated.
2. **Cancelled Bookings:** If a booking is cancelled, its status must be set to "Cancelled".
## Date and Time Rules
3. **Arrival and Departure ... | - A booking cannot be created if the arrival date is before the departure date.
- A booking cannot be created if the arrival date is before the departure date.
- A booking cannot be created if the arrival date is before the departure date.
- A booking cannot be created if the arrival date is before the departure date.
... | businessrules/deepseek-br-qlora_exp2 |
291 | # Business Rules for Booking Arrival and Departure Date Changes
## Rule 1: Tracking Booking Date Changes
- Any change to a booking’s arrival or departure date must record both the new and previous arrival and departure dates.
## Rule 2: Booking Association
- Each arrival or departure date change must be associated wi... | - A booking's arrival and departure dates must be changed only if the booking's status is "booked".
- If a booking's arrival date is changed, the booking must have a new arrival date.
- If a booking's departure date is changed, the booking must have a new departure date.
- If a booking's arrival date is changed, the bo... | businessrules/deepseek-br-qlora_exp2 |
296 | # Business Rules for Automated Notification Creation and Update
## Notification Update Rules
- When an update is requested, each relevant guest notification must be revised based on the latest booking and automated message information.
- If a guest notification is valid after revision, a new notification must be creat... | - Business rules for creating and updating notifications for automated messages.
### End Instruction:
### END | businessrules/deepseek-br-qlora_exp2 |
319 | # Business Rules for Channel Management
- A channel must have a unique code.
- Deposit handling must be specified for each channel (either "Yes" or "No").
- Commission type must be specified for each channel (either "PRE" or "POST").
- A channel must have at least one name alias defined. | - Business rules for the Channel entity
### END | businessrules/deepseek-br-qlora_exp2 |
326 | # Business Rules for Fee Mapping
- Each fee type must be assigned an internal fee code according to the predefined fee-type mapping.
- When a fee type does not match the predefined mapping, the fee code must be assigned based on recognized keywords in the fee name.
- When a fee type does not match by type or keywo... | - Business rules for the system fee map
- Business rules for the inclusion map
- Business rules for the exhaustive map
- Business rules for the default fee
### End Instruction:
### END | businessrules/deepseek-br-qlora_exp2 |
329 | # Business Rules for Property Upsell Migration
## 1. Upsell Assignment
- Each property’s upsells must be assigned to all of its unit types.
- Each unit type must remove all previously assigned upsells before new assignments.
## 2. Upsell Pricing
- The purchase price for each unit type upsell must match the original u... | - Business rules for migrating upsell properties to unit types
- Each property must have at least one upsell
- Each upsell must be associated with a unit type
- Each unit type must have at least one upsell
- Each upsell must have a purchase price and sales price
- Each unit type must have at least one upsell
- Each ups... | businessrules/deepseek-br-qlora_exp2 |
332 | # Business Rules for Booking Finalization
## Booking Finalization Steps
1. A booking may only proceed to finalization if it meets all required finalization conditions.
2. If a booking is eligible for finalization, the process must display a confirmation message to the user.
3. If there are authorized booking deposits ... | - The business rules for finalizing a booking are as follows:
- The business rules for finalizing a booking are as follows:
- The business rules for finalizing a booking are as follows:
- The business rules for finalizing a booking are as follows:
- The business rules for finalizing a booking are as follows:
- The busi... | businessrules/deepseek-br-qlora_exp2 |
336 | # Business Rules for Deal Collection Metadata Normalization
1. Each deal collection response must include a unique identifier representing the collection.
2. If the deal collection is paginated, the response must include metadata specifying the total number of items, current page, last page, and items per page.
3. If ... | # Business Rules for Deal Meta Normalization
- Each deal must have a unique identifier.
- Each deal must have a link to its metadata.
- The total number of deals must be included in the deal metadata.
- The current page number must be included in the deal metadata.
- The last page number must be included in the deal m... | businessrules/deepseek-br-qlora_exp2 |
338 | # Deal Template Line Service Rules
1. Each deal template must include one or more service lines.
2. Each service line must include the following fields:
- Cost Element
- Charge To
- Profit Host Percent
- Profit Investor Percent | - Business rules for the Deal Template Line Service Collection Type
### END | businessrules/deepseek-br-qlora_exp2 |
344 | # Business Rules for CSV and Spreadsheet Data Export
## Export Eligibility Rules
- Data export in CSV or spreadsheet format is permitted only for specific data types, including guests, companies, newsletter subscribers, suppliers, bookings, refunds, payments, invoices, expenses, staff, accounts, accounting schemas, pa... | 1. Business rules for the CSV response handler:
- Business rules for the CSV response handler must be implemented by the following code:
- Business rules for the CSV response handler must be implemented by the following code:
- Business rules for the CSV response handler must be implemented by the following code:
- Bus... | businessrules/deepseek-br-qlora_exp2 |
354 | # Business Rules for Rate Log Submission
- Each rate update request must include a valid unit type identifier.
- Each rate update request must include a valid start date.
- Each rate update request must include a valid end date.
- Each start date and end date must be a valid calendar date.
- If a price is provided,... | - Business rules for rate syncing
### END | businessrules/deepseek-br-qlora_exp2 |
355 | # Business Rules for Setting Customer Specifications
## 1. Customer Name
1. The customer’s first and last name must be taken from the guest’s first and last name.
## 2. Address Fields (Fallback Logic)
For each of the following fields — address line 1, address line 2, postal code, city, country, and region — the... | - The business rules for setting customer specifications are as follows:
- The first name, last name, postal code, city, country, and region must be set for each payment.
- The address lines must be set for each payment.
- The address lines must be set for each payment.
- The address lines must be set for each ... | businessrules/deepseek-br-qlora_exp2 |
356 | # Business Rules for Guest Booking List
- The guest booking list must be retrieved only if a valid guest identifier is provided.
- The booking list may include bookings where the guest is the main guest, the person who booked, a related guest, or the person who placed the booking order.
- Users may filter the booking ... | - Business rules for guest booking list data provider
- Business rules for guest booking list data provider
- Business rules for guest booking list data provider
- Business rules for guest booking list data provider
- Business rules for guest booking list data provider
- Business rules for guest booking list data provi... | businessrules/deepseek-br-qlora_exp2 |
357 | # Business Rules for Guest Creation and Lookup
## Rule 1: Guest Identification
- A guest must be identified using available customer information, including email, name, surname, phone number, address, and zip code.
## Rule 2: Country Code Resolution
- The country code for a guest must be determined based on the provi... | - Business rules for creating a guest for a customer in the United States
- Business rules for creating a guest for a customer in a country other than the United States
- Business rules for validating a phone number for a customer in a country other than the United States
- Business rules for formatting a phone number ... | businessrules/deepseek-br-qlora_exp2 |
368 | # Business Rules for Booking Conflict Resolution
1. When resolving booking conflicts in bulk, each selected booking must have its property, unit type, unit, channel, check-in type, and booking status updated according to the specified resolution parameters.
2. A unit may only be assigned to a booking if the unit is ac... | # Business Rules for Resolving Conflicts in Mass Actions
- Each conflict resolution action must be applied to a single entity.
- Each conflict resolution action must be applied to a single property.
- Each conflict resolution action must be applied to a single unit type.
- Each conflict resolution action must be appli... | businessrules/deepseek-br-qlora_exp2 |
372 | # Business Rules for Channel Deal Commission Calculation
## Channel Commission Rules
- For each booking associated with a channel deal, the channel commission must be recalculated whenever required.
- If a channel deal is active (not archived), the channel commission for a booking must be calculated as the sum of:
... | # Business Rules for Channel Commission Calculation
- A channel commission is calculated for each booking based on the channel deal.
- The channel commission is calculated based on the channel deal's percentage and fix value.
- If the channel deal is not set or is archived, the channel commission is set to zero.
- If ... | businessrules/deepseek-br-qlora_exp2 |
373 | # Business Rules for Booking Entity Preparation
## Booking Timing
- Each change to arrival date, departure date, arrival time, departure time, or number of nights must be detected and processed.
## Accommodation Details
- Each change to the assigned unit, assigned unit type, check-in type, or rate plan must be ... | - A booking can only be updated if the booking is not cancelled.
- A booking can only be cancelled if it is not cancelled.
- A booking can only be changed if the booking is not cancelled.
- A booking can only be changed if the booking is not cancelled.
- A booking can only be changed if the booking is not cancelled.
- ... | businessrules/deepseek-br-qlora_exp2 |
374 | # Business Rules for Unit Type Rate Management
## Ownership and Organization Assignment
- Each new Unit Type Rate must be assigned the same owner as its associated Rate Plan.
- Each new Unit Type Rate must be assigned to the same organization as its associated Rate Plan.
- If an updated Unit Type Rate does not have a... | - Business rules for unit type rate entities must be applied to all unit type rate entities.
- Business rules must be applied to unit type rate entities that have been inserted or updated.
- Business rules must be applied to unit type rate entities that have been inserted or updated.
- Business rules must be applied to... | businessrules/deepseek-br-qlora_exp2 |
378 | # Business Rules for Booking Normalization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior.
| # Business Rules for Booking Normalization
- Business rules for booking normalization
- Business rules for booking normalization
- Business rules for booking normalization
- Business rules for booking normalization
- Business rules for booking normalization
- Business rules for booking normalization
- Business rules f... | businessrules/deepseek-br-qlora_exp2 |
381 | # Business Rules for Booking Management (AjaxController)
## Promotion and Voucher Rules
- Each promotion application must be applied to a booking using the booking’s rate plan, channel, dates, and guest history to determine the discount and total price.
- Each voucher code must be validated for the current organizatio... | - The business rules for the unit detail endpoint are as follows:
1. If the unit ID is provided in the request, the endpoint should return the unit details for the specified unit.
2. If the unit ID is not provided in the request, the endpoint should return an empty response.
### Business Rules End:
### End of Busine... | businessrules/deepseek-br-qlora_exp2 |
387 | # Business Rules for Payment Actions and Listing
## Payment State Rules
- Only the following payment states may be used: OK, Pending, Not Authorized, Rejected, Malformed, Invalid, Error, 3D Authentication Required, and Void.
## Payment Type Rules
- Only the following payment types may be used: Bank Transfer, Ca... | - Payment State:
- OK
- Pending
- Not Authed
- Rejected
- Malformed
- Invalid
- Error
- 3D Authentication
- Void
- Payment Type:
- Bank Transfer
- Cash
- PDQ
- Virtual Credit Card
- PayPal
- Online Gateway
- Payment List Search Model:
- Organization
- ... | businessrules/deepseek-br-qlora_exp2 |
394 | # Payment Term Condition Business Rules
1. A payment term may include one or more payment term conditions.
2. Payment term conditions are optional; a payment term can exist without any conditions. | - Business rules for the Payment Term Condition Collection Type
- Business rules for the Payment Term Condition Type
- Business rules for the Payment Term Condition
- Business rules for the Payment Term Condition
- Business rules for the Payment Term Condition
- Business rules for the Paym... | businessrules/deepseek-br-qlora_exp2 |
400 | # Business Rules for Google Hotel Account XML Synchronization
There are no business rules defined at the business policy level in this section. All logic pertains to form configuration and user interface behavior. | - Business rules for Google Feeding Processor
### Business Rules for Google Feeding Processor:
1. Business rules for Google Feeding Processor
- Business rules for Google Feeding Processor
- Business rules for Google Feeding Processor
- Business rules for Google Feeding Processor
- Business rules for Google Feeding Pro... | businessrules/deepseek-br-qlora_exp2 |
415 | # Business Rules for Parking Type Definitions
## 1. Standard Parking Types
The following parking types must be defined and available in the system:
- Street Parking
- Free Street Parking
- Underground Parking
- Driveway Parking
- Secure Parking
- Valet Parking
## 2. Ownership and Organization Assignment
Each parking ... | - Business rules for Street Parking:
- Street Parking is a type of parking that is available for all streets.
- Street Parking does not require a fee.
- Street Parking is owned by the administrator of the organization.
- Street Parking is part of the organization's parking management system.
- Business rules fo... | businessrules/deepseek-br-qlora_exp2 |
416 | # Business Rules for Stripe Payment and Deposit Processing
## Booking Payment Rules
1. A payment may only be processed for an existing booking.
2. If a payment token is not provided, the payment process must not proceed.
3. When a payment is successfully processed through Stripe, the guest’s card details must be save... | - Business rules for the Stripe payment controller
### Business Rules:
- Business rules for the Stripe payment controller
### Business Rules:
- Business rules for the Stripe payment controller
### Business Rules:
- Business rules for the Stripe payment controller
### Business Rules:
- Business rules for the Stripe ... | businessrules/deepseek-br-qlora_exp2 |
420 | # Business Rules for Booking Date Change
## 1. Authorization
- Only users with edit permissions for a booking may change its dates or unit.
## 2. Unit Availability
- The selected unit for the new booking dates must be available; if not, the unit will be set to null.
## 3. Accommodation Price Update
- If the user req... | # Business Rules for Changing Booking Date
1. The booking date change must be valid.
2. The booking date change must be within the booking's unit's availability.
3. The booking date change must not exceed the booking's unit's availability.
4. The booking date change must not exceed the booking's unit's availability.
5... | businessrules/deepseek-br-qlora_exp2 |
421 | # Business Rules for Google Tax Fee Model
1. A tax or fee must be defined with a specific type, which can be either **amount** or **percent**.
2. The tax or fee must be applied on a defined basis, which can be either **per person** or **per room**.
3. The tax or fee must be applied for a specified period, which can be... | - Business rules for Google Tax Fee Model
- Each Google Tax Fee Model must have a rate plan
- Each Google Tax Fee Model must have a type (amount or percent)
- Each Google Tax Fee Model must have a basis (person or room)
- Each Google Tax Fee Model must have a period (night or stay)
- Each Google Tax Fee Model... | businessrules/deepseek-br-qlora_exp2 |
425 | # Business Rules for Property Viewing
## 1. Draft Properties
- A property that is in draft status must redirect to the property creation wizard before it can be viewed.
## 2. Amenities Display
- If a property has one or more amenities, their names must be listed and separated by commas.
## 3. Brand Display
- If a pr... | # Business Rules for Property View
- Business rules for property view must be implemented by the following code.
- Business rules for property view must be implemented by the following code.
- Business rules for property view must be implemented by the following code.
- Business rules for property view must be impleme... | businessrules/deepseek-br-qlora_exp2 |
429 | # Business Rules for Migrating Single-Unit Amenities to Property Level
## 1. Eligibility and Scope
- Only properties that are active and configured as single-unit properties are eligible for amenity migration.
- The migration applies only to active units within eligible properties.
## 2. Amenity Migration
- All extra... | # Business Rules for Migrating Single Unit Amenities to Property Levels
1. Each property must have at least one active unit that is a single unit.
2. Each amenity must be added to each active unit in the property.
3. The business rules must be applied to each property in the database.
### END | businessrules/deepseek-br-qlora_exp2 |
436 | # Bed Size Management Business Rules
- Only users with view permission may access bed size information.
- Only users with create permission may add a new bed size.
- Only users with edit permission may update an existing bed size.
- Each new or updated bed size must be valid before it is saved. | # Business Rules for Bed Size Management
## 1. Bed Size Management Rules
### 1.1 Bed Size Management Rules
- Each bed size must have a unique name.
- Each bed size must have a unique code.
- Each bed size must have a unique description.
- Each bed size must have a unique color.
- Each bed size must have a unique siz... | businessrules/deepseek-br-qlora_exp2 |
446 | # Channel Management Business Rules
1. Each channel must be created using the designated creation process.
2. Only users with the appropriate permissions may create, view, or edit channels.
3. After a channel is created, an associated channel deal must be defined.
4. All changes to a channel must be saved and persiste... | # Business Rules for Channel App
- Each Channel must have a Channel Deal associated with it.
- A Channel Deal must be associated with a Channel.
- A Channel Deal must be associated with a Channel Deal Type.
- A Channel Deal Type must be associated with a Channel.
- A Channel Deal Type must be associated with a Channel... | businessrules/deepseek-br-qlora_exp2 |
448 | # Business Rules for Property Meta Normalization
- Property collections may include or exclude metadata based on the provided context attributes.
- When metadata is included, each property collection must provide a unique identifier in the metadata.
- If the property collection is paginated, the metadata must include ... | - Business rules for extracting business rules from the code snippet.
### Business Rules:
1. Business rules for extracting business rules from the code snippet.
2. Business rules for extracting business rules from the code snippet.
3. Business rules for extracting business rules from the code snippet.
4. Business rule... | businessrules/deepseek-br-qlora_exp2 |
459 | # Business Rules for Property Data Persistence and Removal
## Mid-Stay Housekeeping Rules
- If the mid-stay housekeeping frequency is overridden and a new frequency is provided, the mid-stay housekeeping period for the property must be updated.
## Property Removal Rules
- A property cannot be removed if it has any fu... | - Business rules for the Property Data Persister class
### Business Rules:
1. Business rules for the Property Data Persister class
- Business rules for the Property Data Persister class
- Business rules for the Property Data Persister class
- Business rules for the Property Data Persister class
- Business rules for th... | businessrules/deepseek-br-qlora_exp2 |
460 | # Business Rules for Availability Logging and Overbooking
## Overbooking Detection and Notification
1. **Overbooking Identification**
- Each new availability log entry with a negative availability value must be identified as an overbooking.
2. **Overbooking Notification**
- A notification must be generated for... | - Business rules for overbooking notifications
- Overbooking notifications are created when a StaahAvailabilityLog entity is created and its availability is less than 0.
- Overbooking notifications are created for each overbooking notification.
- Overbooking notifications are created for each overbooking notifica... | businessrules/deepseek-br-qlora_exp2 |
468 | # Business Rules for Payment Integration Configuration
## Integration Type Rules
- Each payment integration type must have a unique name and description.
- Each payment integration type must be assigned an owner.
- Each payment integration type must be associated with an organization.
## Integration Parameter Rules
-... | - SAGEPAY
- Integration Key
- Integration Password
- URL
- Sagepay Vendor Name
- WORLDPAY
- Service Key
- Client Key
### END | businessrules/deepseek-br-qlora_exp2 |
473 | # Business Rules for Chart of Accounts List
## Account Listing Rules
1. Each account list must include only accounts belonging to the specified organization.
2. Each account in the list must display its identifier, name, code, type, and description.
3. The account list must support export in both CSV and XLSX formats... | - Business rules for extracting business rules from the code.
- Business rules for extracting business rules from the code.
- Business rules for extracting business rules from the code.
- Business rules for extracting business rules from the code.
- Business rules for extracting business rules from the code.
- Business... | businessrules/deepseek-br-qlora_exp2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.