id int64 3 994 | golden_business_rule stringlengths 89 4.82k | finetuned_model_prediction stringlengths 143 4.64k | 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 Booking Income Reports
## 1. Summary Model Structure
- Each Monthly Booking Income Report must include a summary model for accommodation income.
- Each summary model for accommodation income must show the income amount in the currency of the organization.
## 2. Investor Income and Expense... | businessrules/Qwen-base-br-qlora_exp14 |
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... | # Business Rules for Booking Extension
## 1. Access Control
- Only bookings accessible by the current user may be extended.
## 2. Eligibility for Extension
- A booking may not be extended if it is scheduled for cancellation or has been canceled.
- A booking may not be extended if it has already been extended.
- A boo... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Eligibility Requirements
- A booking may only be split if it has not been finalised.
- A booking may only be split if the split date is between the booking's arrival date and departure date, exclusive.
## 2. Unit Availability
- A split may only proceed if the selected unit is ... | businessrules/Qwen-base-br-qlora_exp14 |
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 ... | # Business Rules for Staff Creation
## 1. User Registration Rules
- Each staff member must have a unique email address.
- Each staff member must be associated with a user record.
- Each staff member must have a password set to their plain password.
## 2. Role Assignment Rules
- Each staff member must be assigned at l... | businessrules/Qwen-base-br-qlora_exp14 |
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 Constraints
## 1. Currency Consistency
- Each rate rule that specifies a currency and is not applied to all rate plans must have its currency matched to a currency associated with at least one of its rate plans.
- If a rate rule’s currency is not matched to any associated curren... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Integration Setup and Access
- Each PayPal integration must be associated with a valid PayPal client ID and client secret.
- The client secret must be determined using the appropriate environment (sandbox or live) based on the integration's environment setting.
## 2. Secr... | businessrules/Qwen-base-br-qlora_exp14 |
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 specify a tax rate.
## Investor Custom Gateway Rules
- A deal must be identified as having a custom integration gateway for a given landlord.
## Invoice Printing Rules
- Each customer invoice must allow the option to show bank accou... | businessrules/Qwen-base-br-qlora_exp14 |
21 | This snippet includes only technical behavior and implementation details; no business rules apply.
| # Business Rules for Nightly Detail Tax Component Creation
1. Each Financial Message Queue (FMQ) status must be checked before processing.
2. Only completed FMQs may trigger nightly detail tax component creation.
3. Each FMQ must be processed individually to ensure that nightly detail tax components are created only f... | businessrules/Qwen-base-br-qlora_exp14 |
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 Transferability
- An expense Excel file may only be transferred if no records have an "ERROR" or "TRANSFERRED" status.
## 2. Data Integrity and Acceptability
- An expense Excel file may only be processed if at least one record has a "WARNING" sta... | businessrules/Qwen-base-br-qlora_exp14 |
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 Rules
## 1. Rate Rule Application and Job Generation
- Each rate plan may have rate rules applied to it.
- Each rate rule may be applied to channels or direct bookings, and may specify actions such as changing rates, length of stay, or check-in/check-out restrictions.
- Each rate rule applica... | businessrules/Qwen-base-br-qlora_exp14 |
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 identifier (either name or code).
- An agency cannot be created if another agency with the same name or code already exists. | businessrules/Qwen-base-br-qlora_exp14 |
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. **Access Token Requirement**: To create an LTSA order, an access token must be obtained from the LTSA system.
2. **Title Summary Retrieval**: For each parcel identifier (PID), the system must retrieve the corresponding title summary information.
3. **Order Creation**: An... | businessrules/Qwen-base-br-qlora_exp14 |
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 Processing
## Notification Status Rules
- Each notification must have a valid status assigned to it.
- Accepted notifications must have a status of "Accepted".
- Pending notifications must have a status of "Pending".
- Cancelled notifications must have a status of "Cancelled".
- Compl... | businessrules/Qwen-base-br-qlora_exp14 |
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... | # Property Search and Viewing Business Rules
## Search Rules
- Only properties that are published may be searched for.
## Viewing Rules
- Each property may only be viewed by its owner.
- When a property is linked via a canonical URL, the user must be redirected to the canonical URL if the request referser is from the... | businessrules/Qwen-base-br-qlora_exp14 |
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 Property Recommendations
## 1. Eligibility and Scope
- Similar property recommendations are only available if the system module is enabled.
- Recommendations must consider both neighborhoods and districts when determining similarity.
## 2. Property Matching Criteria
- Similar properties m... | businessrules/Qwen-base-br-qlora_exp14 |
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... | - Users may register only if anyone can register is enabled.
- Users must provide a username and an email address.
- Users must provide a password that is at least 10 characters long.
- Users must agree to the terms and conditions. | businessrules/Qwen-base-br-qlora_exp14 |
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 unique identifier.
## Channel Connection Rules
- A channel manager may be connected to a property using a unique identifier.
- If a rate plan is linked to a unit... | businessrules/Qwen-base-br-qlora_exp14 |
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 have an assigned expense date.
- Each expense line must have a start date (from date).
- Each expense line must have an end date (to date).
## 2. Supplier and Supplier Reference
- If a supplier name is provided for an expense l... | businessrules/Qwen-base-br-qlora_exp14 |
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 Property Rate Calendar Navigation
1. Only properties belonging to the current organization and marked as active may be included in the rate calendar.
2. The rate calendar must be organized by city for each organization.
3. Each property in the organization must be linked to its corresponding rate ... | businessrules/Qwen-base-br-qlora_exp14 |
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. Organization and User Information
- Each company detail request must include the name of the organization.
- Each company detail request must include the email address of the organization.
- Each company detail request must include the phone number of the organizatio... | businessrules/Qwen-base-br-qlora_exp14 |
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
- Only notifications with a favorite status of **True** and associated with the current organization may be selected for sending.
- Only automated messages with a favorite status of **True**, are archived as **False**, and are associated with the current organization may be se... | businessrules/Qwen-base-br-qlora_exp14 |
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 Management
## General Rules
- Only users with appropriate permissions may view or process customer invoices.
## Invoice Creation and Generation
- Each customer invoice must be linked to its associated booking.
- When a customer invoice is generated from a booking, all correspondi... | businessrules/Qwen-base-br-qlora_exp14 |
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 Secrets and Account Ids
## Secret Key and Publishable Key Rules
- For all Stripe integrations associated with an organization, the secret key must be determined based on the organization identifier:
- If the organization identifier is not 66, the secret key must be StripeSecr... | businessrules/Qwen-base-br-qlora_exp14 |
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. **Booking Task Date Update**
- Each booking’s previous and current booking task dates must be updated whenever a booking is created or updated.
2. **Task Calculation on Cancellation**
- When a booking is canceled, all associated t... | businessrules/Qwen-base-br-qlora_exp14 |
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
- No property unit may be created or selected when the option to create is disabled.
- The selection must be limited to existing property units. | businessrules/Qwen-base-br-qlora_exp14 |
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
## Booking Information Rules
- Each booking income record must include the following details:
- Booking ID
- Booking Number
- Channel Name
- Channel Logo
- Guest
- Property Name
- Unit Type Name
- Arrival Date
- Departure Date
- Booking Date
- Booki... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Conditions
## 1. Condition Generation and Assignment
- Each Automated Message must be associated with a set of conditions that define its eligibility.
- Each condition must be valid and must not conflict with existing conditions.
## 2. Booking and Guest Rules
- A ... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Availability Logging
- Each Rentals United availability update must be recorded in the Rentals United availability log.
## 2. Brand Management
- Only authorized brands may manage Rentals United availability or rates.
## 3. Rate Logging
- Each channel rate update must... | businessrules/Qwen-base-br-qlora_exp14 |
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. Addon Breakdowns
- Only breakdowns associated with add-ons for the specified booking may be retrieved.
## 2. Date Range Breakdowns
- Breakdowns for a booking must only include those with a date range that falls within the specified date range.
## 3. Main Line ... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each message sent via the Messaging API must include its message ID.
2. Each message sent via the Messaging API must include all attached files and their contents.
3. The authorization header must be included in each request to the Messaging API.
4. Each mess... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each key place profile must be associated with an owner.
2. When a new key place profile is created without an existing identifier, the owner must be set to the current organization user.
3. Only users with the appropriate permissions may view or edit key place prof... | businessrules/Qwen-base-br-qlora_exp14 |
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 must include a unique identifier in its metadata.
2. When payment data is presented in a paginated form, metadata must include the total number of items, the current page, the last page, and the number of items per page.
3. For non-paginated payment d... | businessrules/Qwen-base-br-qlora_exp14 |
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 Data Normalization and Integration
## General Rules
- Each booking must include all relevant data elements, including guest information, payment details, unit information, and additional discounts and refunds.
## Guest Information Rules
- Each booking must include the full name of the gue... | businessrules/Qwen-base-br-qlora_exp14 |
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 Sending Transaction Data to Google
1. Each live property on Google that is currently active must have its transaction data sent to Google.
2. The transaction data must be sent for each property and its relevant contents, including:
- Property
- Promotions
- Taxes and Fees
3. Sending tr... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Required Information
- A listing must be specified when retrieving bookings.
- A start date must be specified when retrieving bookings.
- An end date must be specified when retrieving bookings.
## 2. Validity of Data
- If the provided start date is not valid, the retrieval... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Property Description and Summary
- The summary of a property must include its name and a brief description, truncated if necessary.
- The full description of a property must include its description or name, truncated if necessary.
## 2. Owner and Location Assignment
-... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each availability period must be defined for a property that is active.
2. Each availability period must be defined within a specified date range.
3. Each availability period must only include units with an active rate plan that originates from the booking engine.
4. Each ... | businessrules/Qwen-base-br-qlora_exp14 |
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 Configuration
- Each nightly detail report must use the default currency configured for the organization or, if none is configured, the organization's default currency.
## 2. Data Aggregation and Filtering
- Only nightly details belonging to t... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Details
- Each booking must be associated with an arrival date and a departure date.
- The booking price must be specified, including any applicable tax and commission amounts.
- The booking status must be set.
- The booking must be linked... | businessrules/Qwen-base-br-qlora_exp14 |
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-Sync
## Property Unit Su-Sync Rules
- Su-Sync functionality is only enabled for property units that have a valid Su-STAAH configuration and Su-STAAH settings are configured and enabled for the unit’s property.
- A property unit may be disconnected from Su-Sync if the Su-STAAH con... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Message Processing Rules
1. Each new message (including SMS, email body, or message line) must be processed and stored after its scheduled insertion.
2. Each update to a message (specifically, an SMS message) must be processed and stored after its scheduled upd... | businessrules/Qwen-base-br-qlora_exp14 |
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 Payment Processing
## 1. Unallocated Payments and State
- All payments with a state of "OK" and no associated allocation must be considered for payments that have not been allocated within the last six months.
## 2. Unallocated Payments and Guest Mismatch
- Payments where the guest is not equal t... | businessrules/Qwen-base-br-qlora_exp14 |
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 corresponding booking.
- Each batch expense must be processed to allocate costs to applicable property units.
## 2. Cost Allocation Based on Unit or Property
- For a bill allocated based on unit, th... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each unit type must be validated before it can be deleted.
2. Only users with appropriate permissions may delete a unit type.
3. If a unit type cannot be validated for deletion, the deletion request must be rejected with an error message.
4. If a deletion error occurs, the ... | businessrules/Qwen-base-br-qlora_exp14 |
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
- No authentication may proceed if the user denies access to Xero.
## Integration Configuration
- Each organization must have a corresponding Xero integration configuration.
## Connection Management
- A user may disconnect their Xe... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Bedding Configuration Retrieval Rules
- The bedding configuration for a booking must include all rooms in the booking with their associated bed details.
- If a booking has a bedding configuration, the retrieved bedding configuration must include all rooms in tha... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Ownership and Authorship
- Each unit type rate log must have an associated owner.
## Override Rate Rules
- Each unit type rate log may be set to override rate rules.
- When a unit type rate log is created or updated, its owner must be set to the same as the current user.
##... | businessrules/Qwen-base-br-qlora_exp14 |
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 Assignment and Origin
## Review Assignment Rules
- Each review must be associated with the booking it pertains to.
- If a review does not specify a property or unit, it must be set to match the booking's associated property and unit.
## Origin and Organization Rules
- When a review is crea... | businessrules/Qwen-base-br-qlora_exp14 |
215 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | # Business Rules for Accounting Schema Defaults
- A default accounting schema cannot be removed; removal is restricted to non-default schemas only.
- Removal of any accounting schema must comply with business policy regarding schema validity and consistency. | businessrules/Qwen-base-br-qlora_exp14 |
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 new departure date for the booking must be specified as the date on which the booking is to be cancelled or rescheduled early.
- The old departure date, if av... | businessrules/Qwen-base-br-qlora_exp14 |
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 Management
## Tax Rate Application and Plan Rules
1. Each tax rate must be associated with one or more rate plans.
2. If a tax rate is associated with at least one rate plan, it must be considered eligible for application.
3. When a tax rate is deleted and archived, all related rate plan... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Term Condition and Action Rules
- The cancellation policy human rule must define the conditions under which a cancellation fee applies based on the term's duration and booking/checkout dates.
- The cancellation fee action must specify whether the fee is applied w... | businessrules/Qwen-base-br-qlora_exp14 |
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 Cancellation
## 1. Check-In Type and Access Code Assignment
- When a booking's check-in type is either KeySafe or Code Entry, the access code must be set based on the following precedence:
- If an override code is set for the booking, use that code.
- If a key-safe code is... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each room that has not completed its bedding configuration conversion must be processed for conversion.
2. The bedding configuration of each eligible room must be converted.
3. Conversion of a room's bedding configuration must only occur if the operation is not ... | businessrules/Qwen-base-br-qlora_exp14 |
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 updated with the items that have been synced.
- Synchronization of a dictionary must only proceed if the dictionary is subscribed for... | businessrules/Qwen-base-br-qlora_exp14 |
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 Worldpay Payment by CVV
1. Each booking must exist before a payment by CVV may be processed.
2. The payment process must be initiated only if the required token is provided.
3. A successful payment must be recorded with the correct payment status and order code.
4. An unsuccessful payment must rec... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Cancellation Penalty Payments
- Only payments of type "OK" (Payment State: PAYMENT_STATE_OK) and not of type "Channel Pay" (Payment Type: PAYMENT_TYPE_CHANNEL_PAY) may be included for a booking cancellation penalty.
## OTCredit ... | businessrules/Qwen-base-br-qlora_exp14 |
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 Naming and Identification
- Each cost element must have a unique name within its associated organization.
- Each cost element must be identifiable by both its name and its category.
## 2. Cost Element Classification and Filtering
- Cost elements must be ... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Booking
1. A property must be selected or provided when creating or selecting a booking inline.
2. Both the arrival date and departure date are required for inline booking creation or selection.
3. The availability status must be provided for each selected property.
4... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Automated Message Generation
## 1. Data Source and Organization
- All bookings must be associated with the specified organization.
## 2. Time Range Selection
- If a time range is specified, only bookings created after the specified date must be included.
## 3. Joining Categories
- Wh... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Channel Manager Booking Rules
1. Each booking request must be assigned to the appropriate channel manager based on the defined channel.
2. For rentals by United, the booking must be processed directly by the channel manager responsible for rentals.
3. For the... | businessrules/Qwen-base-br-qlora_exp14 |
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 include a method, URI, request header, request body, status code, response body, response ID, and sent timestamp.
- Each sync history record may be associated with an organization. | businessrules/Qwen-base-br-qlora_exp14 |
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 Configuration
- Each organization must have the option to configure check-in ready settings for its bookings.
- Each check-in ready setting must include essential information such as guest information, terms and conditions, guest verification, p... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Creation
- Each split booking must inherit the properties and constraints of the original booking, including the property, unit type, unit, arrival date, booking date, split from, collection type, brand, creation source, and tax.
- The arrival and departure ti... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Booking Creation Constraints
- Each booking must have a valid arrival date and, if provided, a valid departure date.
- If a unit or unit type is specified, the booking must be associated with that unit or unit type.
- If a guest is specified, the booking must be associated ... | businessrules/Qwen-base-br-qlora_exp14 |
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 Change Arrival/Departure Date
- Each booking change to arrival or departure date must specify the new arrival and departure dates.
- Each booking change to arrival or departure date must specify the old arrival and departure dates.
- The new arrival date must replace the old arrival date.
... | businessrules/Qwen-base-br-qlora_exp14 |
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 Notification Processing
1. Each automated notification must be either created or updated based on the operation type specified.
2. If a notification is to be updated, only those notifications that already exist and are associated with the correct booking or automated message must be cons... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. **Channel Code**: Each channel must have a unique code.
2. **Deposit Handling**: The channel must specify whether deposit handling is enabled or disabled.
3. **Channel Collection**: The channel must be configured to either allow or not allow connecting to the channel.
4. *... | businessrules/Qwen-base-br-qlora_exp14 |
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 default fee for all rentals is **$0**.
## 2. System-Defined Fees
The following fees are defined system-wide and must be applied regardless of the fee name:
- Bed linens fee (14)
- Bed linens fee (2)
- Bed linens fee (3)
- Bed linens fee (4)
- Bed linens fee (5)
-... | businessrules/Qwen-base-br-qlora_exp14 |
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 Property Upsells to Unit Types
## 1. Unit Type Upsell Association
- Each property must have at least one unit type associated with it.
- Each unit type must be linked to at least one upsell from the property.
## 2. Upsell Mapping
- Each upsell within a property must be mapped to a corre... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Confirmation and Step Assignment
- The finalization process for a booking must start with a confirmation step if the booking can be finalized.
- The finalization process must proceed to the next step based on the booking's current status and available options:
- If t... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each deal collection must include a metadata section containing a unique identifier.
2. The total number of deals must be included in the metadata.
3. If the collection is paginated, metadata must include the total number of items, the current page, the last page, and th... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each deal template line must include the following fields:
- Cost Element
- Charge to
- Profit Host Percent
- Profit Investor Percent
2. The ownership of each service line must be managed according to the deal template line’s ownership rules. | businessrules/Qwen-base-br-qlora_exp14 |
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 Response Handling
1. **File Naming and Content-Disposition**
- When a CSV response is requested, the file name must be generated using the current date and time, appended with the file extension ".csv".
- The file must be served with a content disposition that indicates it is a downloada... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each rate log must be associated with a valid unit type.
2. Each rate log must have a start date and an end date.
3. If a price is provided for a rate log, it must be a valid numeric value and a currency code must be specified.
4. If minimum or maximum stay is... | businessrules/Qwen-base-br-qlora_exp14 |
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 Setting Customer Specifications
## 1. Guest Address and Contact Information
- The first line of the guest's address must be determined using either the guest's provided street address or the organization's address, whichever is available and has a street address.
- The second line of the guest's a... | businessrules/Qwen-base-br-qlora_exp14 |
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
1. Each guest booking list must only include bookings associated with the specified guest.
2. Only bookings where the guest is either the assigned guest or the booking's primary guest, or any guest listed as a booking guest, or any guest listed as an order-by guest, may be inclu... | businessrules/Qwen-base-br-qlora_exp14 |
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
## Guest Creation Rules
1. A guest must be created for each customer based on the provided contact information.
2. The guest’s email, name, and surname must be used to identify the guest.
3. The guest’s phone number must be validated and used for identification.
4. The gues... | businessrules/Qwen-base-br-qlora_exp14 |
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 Booking Conflict Resolution
1. Each booking conflict resolution must be performed on bookings identified by their unique identifier.
2. Each booking must be resolved according to the specified properties, unit type, unit, channel, check-in type, and booking status.
3. If a property is specified, t... | businessrules/Qwen-base-br-qlora_exp14 |
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 by Channel Deal
## 1. Commission Eligibility
- A channel commission may only be calculated for a booking if the associated channel deal is not archived.
## 2. Commission Calculation
- The channel commission for a booking must be calculated as follows:
- If the c... | businessrules/Qwen-base-br-qlora_exp14 |
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. Entity Creation and Update Rules
- Each booking entity must be created or updated based on its source (e.g., Channel Manager, Manual Entry).
- When a booking is updated, all relevant booking details, such as arrival date, departure date, number of nights, unit, uni... | businessrules/Qwen-base-br-qlora_exp14 |
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 Synchronization
## 1. Ownership and Organization Assignment
- Each newly inserted Unit Type Rate must inherit its owner and organization from its associated Rate Plan.
- Each updated Unit Type Rate must not have an assigned owner or organization unless the Rate Plan itself does not ... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Denormalization
## 1. Access Code Handling
- When a booking includes an access code, the access code must be marked as safe code override.
## 2. Arrival and Departure Time Handling
- When a booking includes arrival or departure times, the booking must be marked as automa... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Booking and Property Management Entities
- Each booking must have a unique identifier.
- Each property unit must have a unique identifier.
- Each property must have a unique identifier.
## 2. Booking Status and Check-In
- A booking may have its status changed... | businessrules/Qwen-base-br-qlora_exp14 |
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_exp14 |
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
- Each payment term condition collection must allow addition and removal of conditions.
- Each condition in the payment term collection must be defined and can be associated with a payment term. | businessrules/Qwen-base-br-qlora_exp14 |
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
1. **Account Synchronization**
- Each account name provided must be checked for existence.
- If an account exists, its synchronization status must be verified.
- If the account has a recent XML update, it must be included in the next sync.
- If the account's XML last upd... | businessrules/Qwen-base-br-qlora_exp14 |
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 Definitions
## Parking Type Creation Rules
1. Each parking type must have a unique name.
2. Each parking type must be associated with its owner and the organization it belongs to.
3. Each parking type must be created by an authorized user. | businessrules/Qwen-base-br-qlora_exp14 |
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 Processing Rules
1. Each payment for a booking must be associated with the correct booking and booking order.
2. Each payment must use the client key configured for the booking’s organization and investor deal.
3. Each payment must be linked to the... | businessrules/Qwen-base-br-qlora_exp14 |
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 and Permissions
- Only users with edit permissions may perform booking date changes.
## 2. Unit Availability
- Each booking date change must check the availability of the selected unit for the specified dates and time slots.
- The availability check must i... | businessrules/Qwen-base-br-qlora_exp14 |
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 Models
## 1. Tax Fee Definition
- A tax fee must be defined for a property rate plan.
- Each tax fee must specify the type, basis, period, amount, minimum length of stay, maximum length of stay, and any applicable add-on.
## 2. Rate Plan Association
- Each tax fee must be associa... | businessrules/Qwen-base-br-qlora_exp14 |
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
## 1. Property Creation and Editing
- A property may be accessed directly or through creation wizards.
- Only if a property is marked as a draft, is it permitted to create a new wizard for it.
## 2. Property Details and Display
- If a property has associated storage, its storage cod... | businessrules/Qwen-base-br-qlora_exp14 |
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 Level
1. Each property that is marked as active and is a single unit property must have all its active units' amenities migrated to the property level.
2. Only the first active unit within a single unit property may have its amenities migrated to the pro... | businessrules/Qwen-base-br-qlora_exp14 |
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
- Each bed size must be created and managed by an authorized user.
- A bed size must be valid when it is created or updated.
- Only users with the appropriate permissions may view, create, or edit bed sizes. | businessrules/Qwen-base-br-qlora_exp14 |
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 Application
1. **Access Control**
- Only users with view access to channels may view individual channels.
- Only users with create access to channels may create new channels.
2. **Data Validation**
- All channel data must be valid before it is persisted.
3. **Association Require... | businessrules/Qwen-base-br-qlora_exp14 |
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 Property Collection Metadata
1. **Collection Metadata Identification**
- When processing property collections, the metadata must include the identifier for the collection.
2. **Total and Page Information**
- For collections that support pagination, the metadata must include the total number... | businessrules/Qwen-base-br-qlora_exp14 |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 31