id int64 3 994 | golden_business_rule stringlengths 89 4.82k | finetuned_model_prediction stringlengths 77 4.48k | 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 for Monthly Profit Report
## Accommodation and Channel Revenue Rules
- The accommodation total for a booking must be calculated as the sum of the accommodation value, channel add-on value, and revenue, minus the transaction cost and channel commission.
- The channel tax and channel tax value for a boo... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Only bookings with a valid access can be extended.
- Only bookings with a status of Scheduled for Cancellation or Cancelled can be extended.
- Only bookings with a status of No Show can be extended.
- Only bookings that have not been extended before can be extended.
- Only bookings that have not been finalized can be... | businessrules/Qwen-base-br-qlora_exp17 |
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:... | # Business Rules for Booking Split
## General Rules
- Each booking may be split only if it is not finalised and not already split.
- A split booking must not overlap with the split date or any of the booking’s blocked dates.
- A split booking must not be available in the selected unit at the selected date and time.
#... | businessrules/Qwen-base-br-qlora_exp17 |
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 ... | - Each staff member must have a unique email address within the organization.
- Each staff member must be assigned at least one role, and each role must be valid and recognized by the system.
- Each staff member’s schedule must be synchronized with their calendar.
- Each new user must be assigned an API key upon creati... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Rate Rule Currency Validation
## Rule 1: Currency Consistency per Rate Plan
- Each rate plan associated with a rate rule must have the same currency as the rate rule’s specified currency, unless the rate rule is set to apply to all rate plans.
## Rule 2: Currency Requirement for Fixed Rate Change... | businessrules/Qwen-base-br-qlora_exp17 |
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 Integration
## Integration Setup and Configuration
1. Each PayPal integration must be associated with the PayPal integration partner.
2. Each PayPal integration must be linked to the appropriate organization.
3. Each PayPal integration must use the correct client ID and client secret.
4. P... | businessrules/Qwen-base-br-qlora_exp17 |
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 Finance and Accounting
## Tax Rate Rules
- Each tax schema must have a defined tax rate assigned to it.
## Investor Custom Gateway Rules
- A deal must exist for an investor to have custom gateway settings applied.
## Invoice Print Setting Rules
- Each customer invoice must have its bank account ... | businessrules/Qwen-base-br-qlora_exp17 |
21 | This snippet includes only technical behavior and implementation details; no business rules apply.
| - Each financial message queue must be processed only if it is not already completed.
- Each financial message queue must have a valid financial message queue id before it can be processed. | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Expense Excel Processing
## 1. Data Validation and Status Assignment
- Each expense Excel file must have a status assigned to it.
- If an expense Excel file contains any transfer records with an error state of "TRANSFERRED", its status must be set to "Invalid".
- If an expense Excel file contains ... | businessrules/Qwen-base-br-qlora_exp17 |
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 for Rate Rule Calculations and Applications
## Rate Rule Application Rules
1. Each rate rule application must be evaluated based on its priority and last update date.
2. A rate rule application may only be activated if it is not disabled and its priority or last update date is higher than or equal to... | businessrules/Qwen-base-br-qlora_exp17 |
26 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| # Agency Creation Business Rules
- Each agency must have a unique combination of Name and Code.
- An agency cannot be created if another agency already exists with the same Name or Code.
- Before a new agency can be created, all required information for the agency must be provided.
- No agency may be created if ... | businessrules/Qwen-base-br-qlora_exp17 |
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 LTSA Order Processing
## 1. Authentication and Token Retrieval
- An access token must be retrieved from LTSA before any title summary or order processing can occur.
## 2. Title Summary Retrieval
- Title summary information must be retrieved for a specified parcel identifier (PID) using the valid ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Notification Management
## Notification Status Rules
- Each notification must have a status indicating its current state.
- Accepted notifications must be recognized as such.
- Pending notifications must be recognized as such.
- Cancelled notifications must be recognized as such.
- Failed notifica... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Only properties that have been published may be accessed through the "property" route.
- Access to a property must be granted only to users who are authorized to view that property.
- The map view must display all published properties.
- Each property must have its own unique URL, and users must be able to access a p... | businessrules/Qwen-base-br-qlora_exp17 |
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
## 1. Eligibility and Scope
- Similar properties must be identified only for published properties.
- Similar properties must not include the property itself.
## 2. Area-Based Filtering
- Similar properties may be filtered by neighborhood only if the property is associated with ... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Only users with "anyone can register" enabled may register.
- Registration is not allowed if the current user is authenticated.
- Each new user must create a profile before being registered.
- Only valid and well-formatted passwords may be accepted for user registration.
- Users must agree to the terms and conditions... | businessrules/Qwen-base-br-qlora_exp17 |
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.
... | # Business Rules for Channel Manager and Rate Plan Mapping
## Property Synchronization Rules
- A property may be synchronized with a channel manager using a single operation.
## Channel Manager Connection Rules
- A channel manager may be connected to a property using a single operation.
- If a rate plan is linked to ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Expense Import
## 1. Expense Data Validation
- Each expense line must include an optional date (if missing, the current date must be used).
- Each expense line must include a start date (if missing, the first day of the current month must be used).
- Each expense line must include an end date (if ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Rate Calendar Navigation
## 1. Availability Filtering
- Only properties within the current organization that are active may be included in rate calendar navigation.
## 2. City-Specific Navigation
- The rate calendar for each property must be accessible under its property's area, and only properti... | businessrules/Qwen-base-br-qlora_exp17 |
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
1. Each company detail fill must be associated with the correct user who is responsible for the organization.
2. The company name must be provided and must match the organization's name if available.
3. The contact information (first name, last name, email, phone, city, add... | businessrules/Qwen-base-br-qlora_exp17 |
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 Notification Sending
1. Only notifications associated with organizations the user is currently viewing may be selected.
2. Only favorite automated messages may be selected for notification sending. | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Customer Invoice Processing
## Invoice Generation and Downloading
- Each customer invoice must be associated with a booking.
- When a customer invoice is requested to be downloaded, its associated booking must be determined and used to retrieve the invoice.
## Invoice Processing and Status
- A cu... | businessrules/Qwen-base-br-qlora_exp17 |
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 Secret and Publishable Key Retrieval
## Secret Key Rules
- The Stripe secret key for an organization must be determined based on the organization's ID.
- If the organization's ID is 66, the secret key must be "STRIPE_TEST_SECRET_KEY".
- For all other organizations, the secre... | businessrules/Qwen-base-br-qlora_exp17 |
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 Task Scheduling
## Booking Task Scheduling Rules
1. **Upon Booking Creation:**
- The date of the current booking task must be updated to match the booking’s starting date.
2. **Upon Booking Cancellation:**
- All existing booking tasks must be recalculated for the canceled booking.
... | businessrules/Qwen-base-br-qlora_exp17 |
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
- Only existing property units may be selected; no new property units may be created during selection.
- No additional search or creation options are available for property unit selection; selection must be performed directly from the list of existing units. | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Income Grid Export
- Each booking income record must specify the booking ID, booking number, and the booking status.
- Each booking income record must include the number of guests, the total number of nights, and the number of nights in the current month.
- Each booking income record must ... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Automated Message Triggering
## 1. Condition Generation
- Each automated message must allow users to define conditions using predefined condition types, such as "Time Line," "Number of Nights," "Arrival Date," "Departure Date," "Booking Date," "Guest Tag," "Corporation Tag," "Check-In Type," "S... | businessrules/Qwen-base-br-qlora_exp17 |
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 Management
- Each Rentals United rental must be associated with a valid brand and channel rate log.
- Each Rentals United rental must be managed by a Rentals United service.
- Each Rentals United rental must be assigned to the correct location.
- Each Rentals United rental transacti... | businessrules/Qwen-base-br-qlora_exp17 |
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
## 1. Breakdown Identification
- Each breakdown of a booking must include only lines that are add-ons and are not part of the main booking line.
- Each breakdown must be associated with a specific booking and must not be linked to any customer invoice.
## 2. Date Ran... | businessrules/Qwen-base-br-qlora_exp17 |
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 Messaging API Message Normalization
- Each message must include its message ID.
- Each message may include attached files.
- Each attached file must include a file name and its content in base64 encoded format.
- Each message must include its body.
- Each message may be associated with a boo... | businessrules/Qwen-base-br-qlora_exp17 |
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 Management
- Each key place profile must have an owner assigned when it is created.
- When a new key place profile is created, the user who is logged in as the administrator must be designated as the owner.
- Only users with the appropriate permissions may view or edit key place ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Metadata Normalization
1. Each payment collection must include metadata containing a unique identifier.
2. When payment data is presented in pageable form, metadata must include the total number of items, the current page, the last page, and the number of items per page.
3. When payment da... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Booking Normalization
## General Rules
- Each booking must be normalized according to the specified contexts and groups.
## Required Information
- Each booking must include the following information:
- Booking status
- Total price in breakdown
- Total price currency
- Security deposit
-... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Only users with the required roles may access or execute the transaction date synchronization process.
- Only properties that are currently active on Google may be included in transaction data synchronization.
- Transaction data must be synchronized for each eligible property on Google. | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Retrieval
- Each booking must be retrieved within a specified date range.
- Each booking must be associated with the correct unit type.
- Each booking must be linked to the correct organization. | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Property Normalization
- Each property must include its terms and conditions in the list of available documents. | businessrules/Qwen-base-br-qlora_exp17 |
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 Retrieval
1. Each property availability must be retrieved only for properties that exist.
2. Availability must be filtered by date to include only dates within the specified range.
3. Only unit types with active properties and a minimum capacity of at least the requested numb... | businessrules/Qwen-base-br-qlora_exp17 |
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 for Nightly Detail Report
## 1. Organization and Currency Rules
- Each nightly detail report must be associated with an organization.
- The default currency for the organization must be used if available; otherwise, the organization's default currency must be used.
## 2. Data Aggregation Rules
- The ... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Booking Creation and Management
## 1. Booking Creation Requirements
- Each booking must be associated with an arrival date and a departure date.
- Each booking must specify an arrival time and a departure time.
- Each booking must include an accommodation price, including any applicable tax and c... | businessrules/Qwen-base-br-qlora_exp17 |
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 SU Synchronization
- Property unit synchronization with SU must only proceed if the property's SU configuration is enabled and the property has a valid SU identifier.
- If a property unit is to be deactivated and synchronization with SU is enabled, the system must attempt to disco... | businessrules/Qwen-base-br-qlora_exp17 |
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 Unified Inbox Message Processing
- Each new message (including SMS, email, or body text) must be associated with a valid sender and recipient.
- Each new message must be assigned to the correct conversation.
- When a message is sent, the system must create a new contact if one does not already exi... | businessrules/Qwen-base-br-qlora_exp17 |
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 and Guest Mismatches
## Unallocated Payments Rules
- Only payments with a threeD state of "OK" and an unallocated payment allocation may be included.
- Payments must not be linked to a booking order.
## Guest Mismatch Rules
- If a booking has an order by corporation or order ... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Bill Cost Allocation
## 1. Batch Expense Processing
- Each batch expense must be associated with a unique batch identifier.
- Each batch expense must be linked to its corresponding bill.
## 2. Booking and Unit Integration
- Each bill must be linked to the relevant booking(s).
- Each bill cost all... | businessrules/Qwen-base-br-qlora_exp17 |
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 Management
- No business rules are defined at the business policy level in this section. All logic pertains to form configuration, presentation, or technical implementation details. | businessrules/Qwen-base-br-qlora_exp17 |
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 Integration
## Authentication and Authorization
- The Xero application must provide an authentication URL for users to initiate authentication processes.
- If the authentication code is missing and the authorization request is denied due to an access error, the user must be inform... | businessrules/Qwen-base-br-qlora_exp17 |
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 Bedding Configuration
## Booking Bedding Configuration Rules
1. Each booking must have a valid bedding configuration.
2. The bedding configuration for a booking must be retrieved only if the booking exists and has a valid bedding configuration.
3. If a booking does not have a defined bedd... | businessrules/Qwen-base-br-qlora_exp17 |
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
- Each unit type rate log must have an owner.
- Each unit type rate log must have an identifier (ID).
- Each unit type rate log may be set to override rate rules.
- Each unit type rate log must include one or more rate log lines.
- Each rate log line must be associated with the ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Creation and Origin Determination
## Review Creation Rules
- Each review must be associated with the same booking, property, and unit type as its linked booking.
- If a review does not have a property or unit type assigned, it must be set to match the booking’s property and unit type.
## O... | businessrules/Qwen-base-br-qlora_exp17 |
215 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | - A default accounting schema cannot be removed.
- Each accounting schema must have a unique identifier.
- Each accounting schema must not be marked as the default schema if it exists.
- Only administrators may remove an accounting schema.
- Each accounting schema must provide a valid identifier when deleted. | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Early Checkout
- Each booking early checkout event must reference the specific booking that is subject to the early checkout.
- The departure date for the booking must be updated to reflect the new departure date specified in the event.
- The departure date for the booking must be updated ... | businessrules/Qwen-base-br-qlora_exp17 |
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 and Rate Plan Management
## Tax Rate Rules
- A tax rate may only be associated with one set of rate plans at a time.
- If a tax rate is deleted, all associated rate plans must also be deleted.
## Rate Plan Rules
- Each tax rate may have one or more rate plans associated with it.
- A rate... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Cancellation Policy Human Rule
## Cancellation Policy Condition Rule
A cancellation policy term must specify the period during which a cancellation is allowed. This period must be defined as either:
- The time between booking and check-in, or
- The time after check-in, depending on the term's conf... | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Check-In and Check-Out Processing
## Check-In Type and Access Code Assignment
- For bookings with a check-in type of **KeySafe** or **Code Entry**, the access code must be determined based on the following order of precedence:
- If an override code is set for the booking, use that code.... | businessrules/Qwen-base-br-qlora_exp17 |
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
- Bedding configurations must be converted only for rooms that do not have a completed conversion status.
- The conversion process must be executed for the specified list of room IDs or for all rooms without a completed conversion status.
- The conversion process m... | businessrules/Qwen-base-br-qlora_exp17 |
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 Synchronization
## 1. Dictionary Synchronization Rules
- All Rentals United dictionaries that are subscribed for synchronization must be synchronized regularly.
- Synchronization must ensure that only valid and synchronized dictionary items are retained.
## 2. Data Consistenc... | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Worldpay Payment by CVV
1. Each booking must exist before a payment may be processed.
2. The payment process must use the organization’s Worldpay client key for authorization.
3. Each payment must be associated with the correct booking order and booking.
4. A payment status of “SUCCESS” mu... | businessrules/Qwen-base-br-qlora_exp17 |
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 for Cancellation Penalty and OTCredit Payments
## 1. Cancellation Penalty Payments
- Only payments of type "Channel Pay" or "OTA Credit" are considered when allocating payments for a cancellation penalty.
- Payments with a three-digit state of "OK" are included in the cancellati... | businessrules/Qwen-base-br-qlora_exp17 |
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
## 1. Cost Element Identification
- Each cost element must be uniquely identified by both its name and organization.
## 2. Cost Element Retrieval by Organization and Name
- All cost elements associated with a particular organization must be retrievable by name.
## 3. Cost... | businessrules/Qwen-base-br-qlora_exp17 |
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 Inline Property Selection
- No business rules are defined at the business policy level in this component. All logic pertains to user interface configuration and presentation details. | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Automated Message Generation
## 1. Data Selection and Filtering
- Only bookings belonging to the specified organization may be included in automated message queries.
- Automated messages may be filtered by a date range if the corresponding flag is set.
## 2. Join Categories
- When generat... | businessrules/Qwen-base-br-qlora_exp17 |
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 Channel Manager Booking Processing
- Each booking request must be processed according to the specified channel manager.
- For bookings via the "Rentals" channel manager, the booking must be created directly as a rental booking.
- For bookings via the "SU" channel manager, a booking must be created... | businessrules/Qwen-base-br-qlora_exp17 |
270 | # Sync History Business Rules
No business rules in this set; all items are technical implementation. | # Business Rules for Sync History
- Each sync history record must have a unique identifier.
- Each sync history record may specify the method used for the sync operation.
- Each sync history record may specify the URI of the sync operation.
- Each sync history record may specify the request header of the sync operatio... | businessrules/Qwen-base-br-qlora_exp17 |
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 Check-In Ready Settings
## 1. Check-In Ready Setting Management
- Each check-in ready setting must be associated with a brand and specific guest information.
- Each check-in ready setting must include terms and conditions, guest verification, payment information, and security deposit settings.
##... | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Split
## 1. Booking Split Attributes
- Each split booking must inherit all attributes from the original booking, including property, unit type, unit, arrival date, booking date, collection type, tax, brand, creation source, number of nights, accommodation price, OTA commission, and departu... | businessrules/Qwen-base-br-qlora_exp17 |
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 ... | # Business Rules for Booking Creation
## General Rules
- Each booking must have a valid booking date.
- Each booking must be associated with an arrival date and a departure date.
## Unit and Property Rules
- Each booking must specify a unit or a unit type when available.
- Each booking must have its unit or unit type... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Booking Arrival and Departure Date Changes
- Each booking date change must record the original arrival and departure dates before the new dates are updated.
- Each booking date change must record the new arrival and departure dates. | businessrules/Qwen-base-br-qlora_exp17 |
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 Automated Message Notification Processing
## Notification Creation and Update Rules
1. When updating a notification:
- If the referenced automated message exists, all associated guest notifications must be checked for validity.
- If at least one valid notification is found, the notificati... | businessrules/Qwen-base-br-qlora_exp17 |
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 Channel Configuration
- A channel must have a code.
- A channel may or may not require a deposit handling fee.
- A channel may or may not be able to be connected to other channels.
- A channel may or may not require hotel collection.
- A channel may or may not require commission.
- A channel may o... | businessrules/Qwen-base-br-qlora_exp17 |
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 Fee Mapping
1. **Default Fee**: The system must assign a default fee of **$0** to any fee not explicitly defined in the fee map.
2. **Inclusion-Based Mapping**: Any fee that is explicitly included in the fee map must be assigned the fee value provided for that inclusion.
3. **Exhaustive Mapping**:... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Each property must have at least one associated unit type.
- Each unit type must have all its upsells removed before any new upsells can be added.
- When new upsells are added to a unit type, each new upsell must be linked to the correct unit type and must reflect the sales price of the upsell, calculated in the prop... | businessrules/Qwen-base-br-qlora_exp17 |
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 ... | # Business Rules for Booking Finalization
## Booking Finalization Steps and Rules
1. **Initial Step Determination**
- The first step must be determined based on whether the booking can be finalized.
- If the booking cannot be finalized, the initial step must be set to 0.
2. **Deposit Capture Step Rules**
- ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Metadata Normalization
- Each deal collection must include a unique identifier in its metadata.
- When dealing with paginated results, the metadata must include the total number of items, the current page, the last page, and the number of items per page.
- For non-paginated results, the metad... | businessrules/Qwen-base-br-qlora_exp17 |
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 Deal Template Line Service Collection
- Each deal template line must include the following fields:
- Cost Element
- Charge to
- Profit Host Percent
- Profit Investor Percent | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for CSV Export
The following business rules apply to CSV exports:
1. **File Naming**: The filename for a CSV export must include the prefix corresponding to the entity type, followed by the current date and time in ISO format.
2. **Acceptance Header**: A CSV export must only be served when the Accept... | businessrules/Qwen-base-br-qlora_exp17 |
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 Unit Type Rate Log Synchronization
- Each rate log must be associated with a valid unit type.
- Each rate log must specify a start date and an end date in valid date format.
- If a price is provided for a rate log, it must be a valid numeric value and a currency code must be specified.
- If a mini... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Customer Specification in Booking Payments
1. Each payment associated with a booking must include the guest's address information.
2. If the guest provides a valid street address, it shall be used as the primary address for the payment.
3. If the guest's street address is unavailable, the organiza... | businessrules/Qwen-base-br-qlora_exp17 |
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
- Only bookings associated with the specified guest may be included in the list.
- Bookings may be filtered by a search term; only bookings whose booking code contains the search term (in any case) must match when filtering.
- Bookings may be filtered by the guest who is the boo... | businessrules/Qwen-base-br-qlora_exp17 |
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 Guest Provider Service
- Each guest must be identified by an email address, name, and surname.
- Each guest must provide a valid phone number, including the country code.
- If a country code is provided, the guest’s phone number must be formatted according to that country code.
- Each guest must b... | businessrules/Qwen-base-br-qlora_exp17 |
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 Resolve Conflict Mass Action
1. Each resolved conflict must be associated with the correct property, unit type, unit, channel, check-in type, or booking status, as specified by the user.
2. Only entities that match the specified identifiers may be resolved.
3. When resolving a conflict, the proper... | businessrules/Qwen-base-br-qlora_exp17 |
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
## 1. Channel Commission Eligibility
- A channel commission must only be calculated for a booking if the associated channel deal is not archived.
## 2. Channel Commission Calculation
- If a channel deal exists for a booking and is not archived, the channel commissio... | businessrules/Qwen-base-br-qlora_exp17 |
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 ... | # Business Rules for Booking Entity Preparation
## 1. Data Consistency and Update Rules
- The arrival date, departure date, arrival time, and departure time of a booking must be updated if any of these values has changed.
- The number of nights must be updated if it has changed.
- The unit, unit type, and check-in typ... | businessrules/Qwen-base-br-qlora_exp17 |
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 Ownership and Organization
## Ownership Rules
- Each unit type rate must inherit its owner and organization from its associated rate plan.
- If a unit type rate does not have an assigned owner or organization, it must be set to inherit these from its rate plan.
## Organization Rule... | businessrules/Qwen-base-br-qlora_exp17 |
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
## 1. Key Safe Code and Auto-Addon Rules
- If a booking contains an access code, the booking must be marked as requiring a key safe code override.
- If a booking contains an arrival or departure time, the booking must be marked as requiring automatic add-ons.
## 2. Data Inte... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Booking and Property Management
## Booking Rules
- Each booking must have an assigned arrival and departure date.
- Each booking must have an assigned check-in time.
## Property Rules
- Each property must have a defined property code and name.
- Each unit must have a defined unit type, property, ... | businessrules/Qwen-base-br-qlora_exp17 |
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... | # Business Rules for Payment Management
## Payment State and Type Rules
- Each payment must have one of the following states: OK, Pending, Not Authed, Rejected, Malformed, Invalid, Error, 3D Auth, Void.
- Each payment must have one of the following types: Bank Transfer, Cash, PDQ, Virtual Credit Card, PayPal, Online G... | businessrules/Qwen-base-br-qlora_exp17 |
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 Payment Term Condition Collection
- A payment term condition collection may include one or more payment term conditions.
- Each payment term condition must have a name, a description (if applicable), and may include a default currency. | businessrules/Qwen-base-br-qlora_exp17 |
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 Hotel Feeding
1. Each account name provided must correspond to a valid Google Hotel account.
2. Only accounts that require synchronization may be processed for feeding.
3. Accounts that have not been recently synchronized may not be processed for feeding. | businessrules/Qwen-base-br-qlora_exp17 |
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 Parking Type Management
- Each parking type must be associated with an owner and an organization.
- Each parking type must be created and managed by an authorized user (e.g., the system administrator).
- Different types of parking may include:
- Street parking
- Free street parking
- U... | businessrules/Qwen-base-br-qlora_exp17 |
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 Stripe Payment and Deposit Processing
## Payment Rules
1. Each payment made through Stripe must be associated with the correct booking and booking order.
2. The client key for a Stripe payment must be derived from the booking’s organization and investor deal.
3. A payment must be classified as “P... | businessrules/Qwen-base-br-qlora_exp17 |
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 Booking Date Changes
## 1. Authorization
- Only users with edit permission may modify a booking's date.
## 2. Unit Availability
- The system must verify the availability of the selected unit for the proposed date range.
- If the unit is not available, the date change must be denied.
## 3. Price ... | businessrules/Qwen-base-br-qlora_exp17 |
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 tax fee must be associated with a rate plan.
- Each tax fee must specify its type (amount or percent).
- Each tax fee must define its basis (room or person).
- Each tax fee must specify its period (night or stay).
- Each tax fee must include an amount.
- Each tax fee ma... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - A property may only be viewed if it is not in draft mode.
- The storage code for a property must be displayed if the property has storage.
- The list of amenities for a property must be displayed if there are amenities associated with the property.
- The application URL for the property must be retrieved from the con... | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Only single-unit properties with at least one active unit that is active can have their single unit's amenities migrated to the property level.
- All amenities associated with the unit type of a single-unit property must be added to the property when the migration is complete. | businessrules/Qwen-base-br-qlora_exp17 |
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. | # Bed Size Management Business Rules
- Only users with view permission may access bed size records.
- Only users with create permission may add new bed sizes.
- Only users with edit permission may update existing bed sizes.
- Each bed size must be validated before it is created or updated. | businessrules/Qwen-base-br-qlora_exp17 |
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... | - Each channel must be created and its details must be validated before it can be saved.
- After a channel is created, the user must be prompted to define an associated Channel Deal.
- Only users with the appropriate permissions may create or update channels. | businessrules/Qwen-base-br-qlora_exp17 |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 34