id int64 3 994 | golden_business_rule stringlengths 89 4.82k | finetuned_model_prediction stringlengths 77 3.92k | 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 and channel totals, excluding any discounts or commissions.
- The channel addon revenue for a booking must be calculated as the sum of all cha... | businessrules/Qwen-base-br-qlora_exp15 |
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.
- A booking cannot be extended if it is scheduled for cancellation or has been canceled.
- A booking cannot be extended if it has already been extended to a finalization status.
- A booking cannot be extended if it has been split.
- A booking cannot be extended if it... | businessrules/Qwen-base-br-qlora_exp15 |
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
- A Booking may only be split if it is not finalised and has not been split previously.
- The number of nights in the Booking must be at least 2 for it to be split.
- The Split Date must lie between the Booking's Arrival Date and Departure Date, exclusively.
- The Sp... | businessrules/Qwen-base-br-qlora_exp15 |
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 ... | 1. Each staff member must have a unique email address within the same organization.
2. Each staff member must be assigned at least one role.
3. Each staff member’s roles must be combined to determine their staff type.
4. The staff type for each staff member must be set based on their assigned roles.
5. Each staff membe... | businessrules/Qwen-base-br-qlora_exp15 |
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 for Non-Universal Rate Rules
If a Rate Rule specifies a currency and is not universal, each associated rate plan must have the same currency as the Rate Rule's currency, or the currency must be invalid.
## Rule 2: Currency Requirement ... | businessrules/Qwen-base-br-qlora_exp15 |
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 correct integration environment.
- For testing, the environment must be set to "test".
- For production, the environment must be set to "live".
2. Each PayPal integration mu... | businessrules/Qwen-base-br-qlora_exp15 |
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.
## 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 information and... | businessrules/Qwen-base-br-qlora_exp15 |
21 | This snippet includes only technical behavior and implementation details; no business rules apply.
| - Only financial message queues with a valid status of "completed" are eligible for nightly detail tax component creation.
- Each financial message queue must be uniquely identified before nightly detail tax component creation can proceed.
- Nightly detail tax component creation is not permitted for any financial messa... | businessrules/Qwen-base-br-qlora_exp15 |
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 Processing States
- Each expense Excel record must have a status indicating its current state.
- If a expense Excel contains any transfer records with an error state of "TRANSFERRED", the entire expense Excel record must be in a status indicating ... | businessrules/Qwen-base-br-qlora_exp15 |
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 active only if it is marked as active.
2. When a rate rule is marked as active, all previous active rate rule applications for the same date and scope must be deactivated.
3. A rate rule a... | businessrules/Qwen-base-br-qlora_exp15 |
26 | # Agency Uniqueness Rules
- No two agencies may share the same Name.
- No two agencies may share the same Code.
| - Each agency must have a unique name and code in the system.
- An agency cannot be created if another agency with the same name or code already exists. | businessrules/Qwen-base-br-qlora_exp15 |
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... | - An access token must be obtained from LTSA before retrieving title summary information.
- Only the first title summary in the response may be used for subsequent processing, such as order creation.
- An order may only be created using the correct title number and land title district code. | businessrules/Qwen-base-br-qlora_exp15 |
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 have a status of "Accepted".
- Pending notifications must have a status of "Pending".
- Cancelled notifications must have a status of "Cancelled"... | businessrules/Qwen-base-br-qlora_exp15 |
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 viewed.
- Only users with view permissions for a property may access its details.
- A property's canonical URL must be determined and used when the user requests to view the property.
- The ability to return to the previous page must be available when viewing a property... | businessrules/Qwen-base-br-qlora_exp15 |
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. Similar property recommendations must only be available when the similarity module is enabled.
2. Similar property recommendations must consider both neighborhood and district as areas for matching properties.
3. Similar property recommendations must exclude the... | businessrules/Qwen-base-br-qlora_exp15 |
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 who are not currently logged in may register.
- Users must agree to terms and conditions before registering.
- Passwords must be at least 10 characters long and no more than 4096 characters.
- Registration is restricted if anyone can register is disabled. | businessrules/Qwen-base-br-qlora_exp15 |
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 Property Management
## Property Synchronization Rules
- A property may be synchronized with the channel manager using a valid property identifier.
## Channel Connection Rules
- A channel may be connected to the channel manager using a valid property identifier.
- A channel con... | businessrules/Qwen-base-br-qlora_exp15 |
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 a valid date for the expense date.
- Each expense line must have a valid starting date (set to the first day of the current month if not provided).
- Each expense line must have a valid ending date (set to the last day of t... | businessrules/Qwen-base-br-qlora_exp15 |
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. Only properties that are active must be included in the rate calendar navigation.
2. Only properties belonging to the current organization may be displayed in the rate calendar.
3. Properties must be grouped by city before being used to populate the rate calendar naviga... | businessrules/Qwen-base-br-qlora_exp15 |
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 Company Details Filling
1. Each company details record must include the organization's name and its creation date.
2. Each company details record must specify the contact information for the organization's administrator, including the administrator's first name, last name, email, city, address, co... | businessrules/Qwen-base-br-qlora_exp15 |
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
There are no business rules defined in this code segment. The provided logic only configures form fields for user interface display and does not implement any business policy or domain logic. | businessrules/Qwen-base-br-qlora_exp15 |
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
## General Requirements
- Only authorized users may view or process customer invoices.
## Invoice Creation and Management
- Each customer invoice must be linked to its corresponding booking.
- A customer invoice may only be created if its associated booking exists and ... | businessrules/Qwen-base-br-qlora_exp15 |
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 secret key for a Stripe integration must be determined based on the organization's identity:
- For organizations other than the one with ID 66, the secret key must be **Stripe Partnership Secret Key**.
- For the ... | businessrules/Qwen-base-br-qlora_exp15 |
103 | # Business Rules for Booking Task Management
- When a booking is inserted, the dates of tasks related to both the previous and current bookings must be updated accordingly.
- When a booking is canceled, all tasks associated with that booking must be recalculated. If the booking was an extension of another booking, tas... | # Business Rules for Booking Tasks
## Booking Task Synchronization
- Each booking's previous and current booking task dates must be synchronized when a booking is created or updated.
- When a booking is canceled, all related tasks must be recalculated and updated.
## Task Recalculation on Booking Cancellation
- If a ... | businessrules/Qwen-base-br-qlora_exp15 |
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.* | - A property unit must be selected for each property.
- Users cannot create a property unit when selecting a property; only the selection itself is allowed. | businessrules/Qwen-base-br-qlora_exp15 |
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 booking status.
- Each booking income record must include the guest information, property name, unit type name, arrival date, departure date, booking date, and number of guests.
- Each booking ... | businessrules/Qwen-base-br-qlora_exp15 |
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
## Booking and Guest Rules
- Each automated message must include all conditions related to bookings and guests as defined by the following labels:
- Booking
- No of Nights
- Lead Time
- Adult Guest
- Arrival Date
- Departure Date
... | businessrules/Qwen-base-br-qlora_exp15 |
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 service must be associated with its respective brand.
- Each Rentals United service must be linked to the correct configuration.
- Each Rentals United service must be connected to the correct entity manager.
- Each Rentals United service must be inte... | businessrules/Qwen-base-br-qlora_exp15 |
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 Line Breakdowns
- Only breakdowns associated with addons for a specific booking may be retrieved for a booking.
## 2. Date Range Breakdowns
- Breakdowns may only be retrieved for a booking if the breakdown's date falls within the specified date range.
##... | businessrules/Qwen-base-br-qlora_exp15 |
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 unique message ID.
- Each message must be associated with the correct booking channel if the booking exists.
- Each message must include any attached files.
- Each message must specify the message body.
- Each message must spe... | businessrules/Qwen-base-br-qlora_exp15 |
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 be associated with its owner by default when created.
- Only users with the appropriate permissions may view or edit Key Place Profiles.
- A Key Place Profile may only be created or updated if all required information is valid and complete... | businessrules/Qwen-base-br-qlora_exp15 |
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.
| - Each payment or refund collection must have a unique identifier.
- The total number of items in each payment or refund collection must be known.
- The number of items per page in each payment or refund collection must be known.
- The total number of items in each payment or refund collection must be retrievable.
- Th... | businessrules/Qwen-base-br-qlora_exp15 |
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
- No business rules apply for bookings not covered by search or read permissions.
## Booking Details Rules
- Each booking must include its booking number, status, total price, and all relevant attachments.
- If the booking has a guest, the system must record... | businessrules/Qwen-base-br-qlora_exp15 |
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 authenticated users may execute this process.
- Only properties connected to Google may be included in transaction data synchronization.
- All relevant property contents (property, promotions, taxes, and fees) must be sent to Google for synchronization. | businessrules/Qwen-base-br-qlora_exp15 |
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**
... | - Each booking must be associated with a unit type.
- Each booking must be dated between the specified start and end dates.
- Each booking must belong to the same organization as required. | businessrules/Qwen-base-br-qlora_exp15 |
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 Overview
- The description or name of a property must be provided. If no description is available, the property's name must be used.
## 2. Property Owner
- The property must have an associated owner, which is determined by the brand's register... | businessrules/Qwen-base-br-qlora_exp15 |
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 retrieval must be restricted to availabilities associated with an existing property.
2. Availability must be retrieved for a specified date range, defined by "after" and "before" dates.
3. The number of guests must be restricted to the ... | businessrules/Qwen-base-br-qlora_exp15 |
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 Setup
- Each nightly detail report must be calculated using the default currency set for the organization.
- If the organization's default currency is not specified, it must use the organization's default currency.
## 2. Data Aggregation
- The... | businessrules/Qwen-base-br-qlora_exp15 |
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 reference an accommodation price, property, unit, and rate plan.
-... | businessrules/Qwen-base-br-qlora_exp15 |
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 type's associated property is enabled for SU and has a valid SU station identifier.
- If SU synchronization is enabled for the property type and the SU station identifier is valid and non-emp... | businessrules/Qwen-base-br-qlora_exp15 |
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
- Each new message (including SMS, email, and body content) must be associated with a valid sender and recipient.
- When a message is received, a new conversation must be created if one does not already exist between the sender and rece... | businessrules/Qwen-base-br-qlora_exp15 |
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
## 1. Unallocated Payments and Mismatched Guest Payments
- Only payments with a threeD state of "OK" and a guest booking must be considered.
- Payments with a guest booking but no payment allocation must be identified.
## 2. Guest Mismatch Rule
- For ea... | businessrules/Qwen-base-br-qlora_exp15 |
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
- When a batch expense is created, all associated bookings for the batch expense must be identified and their cost allocations must be created or updated accordingly.
## 2. Unit-Based Allocation
- For a bill allocated based on the number of unit... | businessrules/Qwen-base-br-qlora_exp15 |
195 | # Business Rules for Unit Type Deletion
- A unit type must be validated for removal before it can be deleted.
- If a unit type cannot be removed due to business constraints, the deletion must be rejected with an appropriate error message. | # Business Rules for Unit Type Deletion
- Only unit types that exist in the system may be deleted.
- Before a unit type can be deleted, it must be validated to ensure it can be removed without violating any constraints or policies. | businessrules/Qwen-base-br-qlora_exp15 |
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 user must be able to authenticate with Xero using the provided authentication URL.
- If the user denies access to Xero, the authentication process must be aborted.
## Integration Setup and Connection
- When the user authoriz... | businessrules/Qwen-base-br-qlora_exp15 |
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
- Each booking must have a defined bedding configuration.
- The bedding configuration for a booking must be available and valid when required.
- The bedding configuration for a booking must reflect the configured bedding for the... | businessrules/Qwen-base-br-qlora_exp15 |
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 a list of associated rate log lines.
- Each rate log line must inherit the override rate rules from its parent unit type rate log.
- When a rate log line is added to a unit type rate log, its overr... | businessrules/Qwen-base-br-qlora_exp15 |
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 booking it is linked to.
- If a review does not have a property assigned, its property must be set to the booking's property.
- If a review does not have a unit type assigned, its unit type ... | businessrules/Qwen-base-br-qlora_exp15 |
215 | # Business Rules for Accounting Schema Defaults
- The default accounting schema **cannot be deleted**. | - A default accounting schema cannot be removed; all other accounting schemas must be removed before the default one can be deleted. | businessrules/Qwen-base-br-qlora_exp15 |
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 involved.
- The new departure date for the booking must be defined as the earliest available date after the old departure date.
- The old departure date for the booking must be recorded.
- The new depart... | businessrules/Qwen-base-br-qlora_exp15 |
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 Plan Rules
- Each tax rate may have one or more associated rate plans.
- A tax rate’s rate plans must be determined based on the tax rate itself, not on any other rate plan or data access.
- When a tax rate’s rate plans are to be deleted and archived, all related r... | businessrules/Qwen-base-br-qlora_exp15 |
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 Rules
1. Each cancellation policy term must be defined with a condition and an action.
2. The condition for a cancellation policy term must specify the criteria that must be met before the action applies.
3. The action for a cancellation policy term must describe the resu... | businessrules/Qwen-base-br-qlora_exp15 |
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 **KeySafe** or **Code Entry**, the access code must be set to the code associated with the check-in backup type of the booking if one exists and a code is defined.
- If no code is ... | businessrules/Qwen-base-br-qlora_exp15 |
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 ... | - Each room whose bed configuration has not been converted must be processed to convert its bed configuration.
- The conversion process must not persist or flush changes when the dry option is enabled. | businessrules/Qwen-base-br-qlora_exp15 |
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 dictionaries subscribed to for synchronization must be synchronized according to their defined sync status.
- If a dictionary is marked as subscribed for synchronization, its last synced timestamp must be updated whe... | businessrules/Qwen-base-br-qlora_exp15 |
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 ... | - Each booking must have a corresponding booking order.
- Each payment made via Worldpay must be associated with the correct booking and booking order.
- The payment token required for a Worldpay payment must be provided by the booking’s organization and investor deal service.
- Each payment must be linked to the appro... | businessrules/Qwen-base-br-qlora_exp15 |
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 "OK" (i.e., with state "PAYMENT_STATE_OK") and not of type "Channel Payment" or "OTA Credit" may be considered for allocating payments for a booking cancellation penalty.
... | businessrules/Qwen-base-br-qlora_exp15 |
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 be uniquely identifiable within its organization.
- A cost element must be able to be retrieved and identified by its name and organization.
## 2. Accommodation Cost Elements
- Each accommodation cost el... | businessrules/Qwen-base-br-qlora_exp15 |
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
- No business rules are defined at the business policy level for this component. All logic pertains to form configuration and presentation details. | businessrules/Qwen-base-br-qlora_exp15 |
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 Query Generation
## 1. Data Selection and Filtering
- Only bookings belonging to the specified organization may be included in queries.
- All queries must be filtered to include only bookings that have been created after the current date.
## 2. Join Categories and Relationships
- When gen... | businessrules/Qwen-base-br-qlora_exp15 |
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 its assigned channel manager.
- For bookings managed by the "Rents Unit", the booking must be created directly by the system.
- For bookings managed by the "SU", a booking must be created by transferring data ... | businessrules/Qwen-base-br-qlora_exp15 |
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 optionally include the method used for the sync operation.
- Each sync history record may optionally include the URL of the resource being synced.
- Each sync history record may optionally include... | businessrules/Qwen-base-br-qlora_exp15 |
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 booking must have corresponding check-in ready settings for all relevant brands and guests.
## 2. Guest Information and Verification
- Each check-in ready setting must include guest information and verification details.
- E... | businessrules/Qwen-base-br-qlora_exp15 |
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 Creation
- A booking may be split into multiple bookings, each with its own arrival, departure, and other booking details.
- Each split booking must inherit the property, unit type, and unit from the original booking.
- Each split booking must have a distinct book... | businessrules/Qwen-base-br-qlora_exp15 |
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. Guest Association
- Each booking must be associated with the correct guest if provided.
- If no guest is specified, the booking must be linked to the guest who initiated the creation process.
## 2. Booking Date and Unit/Type Selection
- The arrival date and departure date f... | businessrules/Qwen-base-br-qlora_exp15 |
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 change must specify the new arrival and departure dates.
- Each booking change must reflect the old arrival and departure dates.
- The arrival and departure dates allowed for a booking must be determined by the business policy or system con... | businessrules/Qwen-base-br-qlora_exp15 |
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
## Notification Creation and Update Rules
1. When a notification is **updated**:
- Only notifications associated with an automated message that exists in the system may be updated.
- Notifications must be updated if at least one matching notification exis... | businessrules/Qwen-base-br-qlora_exp15 |
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.
- A channel may or may not be set up to collect payments.
- A channel may or may not have an alias associated with it.
- A channel may or may not be named using an alias.
- A channel may or may not ha... | businessrules/Qwen-base-br-qlora_exp15 |
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. Fee Inclusion
Any fee that is explicitly included in the system's fee map must be used to determine the fee amount.
- For example, if a fee is listed under "Resort F... | businessrules/Qwen-base-br-qlora_exp15 |
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 be associated with at least one upsell from another property.
- Each upsell must be linked to the correct purchase price for the property.
- Each upsell must have a sales price calculated in the property's default currency. | businessrules/Qwen-base-br-qlora_exp15 |
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:**
- The first step must be determined based on whether the booking can be finalized.
- If the booking can be finalized, the step must advance to the confirmation step; otherwise, the step must remain at initial.... | businessrules/Qwen-base-br-qlora_exp15 |
336 | # Business Rules for Deal Collection Metadata Normalization
1. Each deal collection response must include a unique identifier representing the collection.
2. If the deal collection is paginated, the response must include metadata specifying the total number of items, current page, last page, and items per page.
3. If ... | # Business Rules for Deal Meta Normalization
- Each deal collection must include a unique identifier in its metadata.
- When the collection is paginated, metadata must include the total number of items, the current page, the last page, and the number of items per page.
- When the collection is not paginated, metadata ... | businessrules/Qwen-base-br-qlora_exp15 |
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 must include one or more service line items.
- Each service line item must specify the cost element, the entity to which the cost is allocated, and the profit sharing percentages between the host investor and the other investors. | businessrules/Qwen-base-br-qlora_exp15 |
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
The following business rules apply to CSV response handling:
1. CSV responses must be generated only for actions that do not correspond to predefined API endpoints.
2. CSV responses must use a file name format that includes the date and time of generation, followed by the ap... | businessrules/Qwen-base-br-qlora_exp15 |
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. A rate log must be created for a unit type only if all required parameters are provided.
2. The required parameters for a unit type rate log are:
- A valid unit type identifier (mandatory);
- A from date (mandatory);
- A to date (mandatory);
3. If a p... | businessrules/Qwen-base-br-qlora_exp15 |
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. Address Information
- The address information used to set the customer's payment details must be derived from either the guest's provided address or the organization's configured address, whichever is available and valid.
- If the guest's address is unavailabl... | businessrules/Qwen-base-br-qlora_exp15 |
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 ... | - Each guest booking must be associated with a valid guest record.
- Only bookings where the guest matches the specified guest ID may be retrieved.
- Bookings may be filtered by searching for a booking code that matches the provided search term.
- Only bookings, guests, properties, unit types, and unit guests that are ... | businessrules/Qwen-base-br-qlora_exp15 |
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’s phone number must use the correct country code when available.
- Each guest’s address and zip code may be provided for more detailed record-keeping.
- Each guest may be associated with an ... | businessrules/Qwen-base-br-qlora_exp15 |
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 booking must be linked to the correct property, unit type, channel, check-in type, and booking status.
2. If a property is specified, the booking must be assigned to that property.
3. If a unit type is specified and the unit is active, the booking must... | businessrules/Qwen-base-br-qlora_exp15 |
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. 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:
- Calculate the channel tota... | businessrules/Qwen-base-br-qlora_exp15 |
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. Change Detection and Event Triggers
- Any change in arrival or departure date, accommodation price, OTA commission, tax, number of nights, unit type, unit, check-in type, channel, booking status, deposit amount, or booking purpose must trigger an event to update th... | businessrules/Qwen-base-br-qlora_exp15 |
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 Management
## Rule 1: Ownership and Organization Assignment on Creation
When a new Unit Type Rate is created, its owner and organization must be set to match those of its associated Rate Plan.
## Rule 2: Restoration of Original Ownership and Organization on Update
When a Unit Type ... | businessrules/Qwen-base-br-qlora_exp15 |
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
## Access Code Rules
- If an access code is included in the booking data, the booking must be marked as having an access code override.
## Auto-Addon Rules
- If either arrival time or departure time is specified for a booking, the booking must be marked as having automatic a... | businessrules/Qwen-base-br-qlora_exp15 |
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 Promotion Applications
## Booking Rules
1. Each booking must have an associated arrival date and a departure date.
2. The arrival date of a booking must be set to the departure date if the booking does not have an arrival date.
3. A booking's status must be updated to "Checked In" whe... | businessrules/Qwen-base-br-qlora_exp15 |
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 may have one of the following payment states:
- OK
- Pending
- Not Authed
- Rejected
- Malformed
- Invalid
- Error
- 3D Auth
- Void
- Each payment may have one of the following payment types: ... | businessrules/Qwen-base-br-qlora_exp15 |
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 Conditions
- Each payment term must include one or more payment term conditions.
- Each payment term condition must have a name and a description (if applicable).
- The currency used for payment term calculations must be specified and valid. | businessrules/Qwen-base-br-qlora_exp15 |
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. | - Each account name provided must correspond to a valid Google Hotel Account.
- Only accounts that exist in the system and have a valid XML last update must be considered for synchronization.
- Synchronization of accounts must be performed only for accounts that have not been recently synchronized.
- Synchronization of... | businessrules/Qwen-base-br-qlora_exp15 |
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 Types
- Each parking type must be associated with the correct owner and organization.
- Each parking type must be created and managed by an authorized user. | businessrules/Qwen-base-br-qlora_exp15 |
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
## Stripe Payment Rules
1. Each payment made through Stripe must be associated with the correct booking order.
2. The payment method key for Stripe must be derived from the booking’s organization and investor deal service.
3. A payment made via Stripe must in... | businessrules/Qwen-base-br-qlora_exp15 |
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 Modification
## 1. Booking Access Control
- Only users with edit access permission may modify a booking’s date.
## 2. Unit Availability Verification
- The system must verify unit availability for the proposed date change.
- The selected unit must be available for the requested dates ... | businessrules/Qwen-base-br-qlora_exp15 |
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, basis, period, amount, minimum length of stay, maximum length of stay, and optional rate addon.
- The length of stay range for a tax fee must be defined by its minimum and maximum values. | businessrules/Qwen-base-br-qlora_exp15 |
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 property's storage code must be displayed if the property has storage and is not in draft mode.
- The property's amenities must be displayed if the property has at least one amenity.
- The application URL must be provided for the property.
- The property... | businessrules/Qwen-base-br-qlora_exp15 |
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, active unit may have their unit-level amenities migrated to the property level.
- Amenities associated with the unit type of each active, active single-unit must be migrated to the property level before any further processing may occur. | businessrules/Qwen-base-br-qlora_exp15 |
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 valid before it can be saved. | businessrules/Qwen-base-br-qlora_exp15 |
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... | - Only channels that are viewable may be accessed or viewed.
- Only channels that are creatable may be created.
- Only channels that are valid may be persisted and saved.
- A channel must be associated with a channel deal after it is created. | businessrules/Qwen-base-br-qlora_exp15 |
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 Meta Normalization
1. When retrieving a property collection, the total number of items in the collection must be determined and included in the metadata.
2. The metadata must include the identifier for the collection, whether the collection is a subresource or not.
3. If the collection is... | businessrules/Qwen-base-br-qlora_exp15 |
459 | # Business Rules for Property Data Persistence and Removal
## Mid-Stay Housekeeping Rules
- If the mid-stay housekeeping frequency is overridden and a new frequency is provided, the mid-stay housekeeping period for the property must be updated.
## Property Removal Rules
- A property cannot be removed if it has any fu... | # Business Rules for Property Data Persistence
## 1. Property Deletion and Removal
- A property may be deleted only if it has no future bookings, no past bookings, no active units, no mapped rate plans, and no expenses.
- When a property is deleted, all associated bookings, units, mapped rate plans, and expenses must ... | businessrules/Qwen-base-br-qlora_exp15 |
460 | # Business Rules for Availability Logging and Overbooking
## Overbooking Detection and Notification
1. **Overbooking Identification**
- Each new availability log entry with a negative availability value must be identified as an overbooking.
2. **Overbooking Notification**
- A notification must be generated for... | # Business Rules for Availability Booking Notifications
## 1. Overbooking Detection
- Any availability log with a negative availability value must be identified for further processing.
## 2. Notification Eligibility
- Only notifications related to overbookings (i.e., those with a negative availability value) may trig... | businessrules/Qwen-base-br-qlora_exp15 |
468 | # Business Rules for Payment Integration Configuration
## Integration Type Rules
- Each payment integration type must have a unique name and description.
- Each payment integration type must be assigned an owner.
- Each payment integration type must be associated with an organization.
## Integration Parameter Rules
-... | # Business Rules for Payment Integration Configuration
## Integration Restrictions
- Each payment integration must be associated with an organization.
## Integration Parameters
- Each integration must have parameters specifying the following integration details:
- Integration Key
- Integration Password
- URL
... | businessrules/Qwen-base-br-qlora_exp15 |
473 | # Business Rules for Chart of Accounts List
## Account Listing Rules
1. Each account list must include only accounts belonging to the specified organization.
2. Each account in the list must display its identifier, name, code, type, and description.
3. The account list must support export in both CSV and XLSX formats... | # Business Rules for Account Listing
1. Only accounts belonging to the specified organization may be included in the account list.
2. Only accounts with a defined name, code, type, and description may be included in the account list.
3. The account list must be accessible in CSV and Excel formats.
4. Only users with t... | businessrules/Qwen-base-br-qlora_exp15 |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 31