Applications & Junctures

The breadth of Abacus 21 Software Modules is internally structured into Applications with (perhaps) Application Junctions (Junctures) defined at specific points in a respective Application's flow -- for the purpose of allowing System Administrators to take advantage of these 'trigger points' to optionally invoke User-defined actions.

 

An example would be to have the Generalized Comment Routine for the specific Comment Type 'Allergies':

 

 

See Narrative Comments.

 

Applications are defined by Abacus 21.

 

Application Examples:

 

  • A/R Minimums

  • A/R Transactions Entry

  • Access Management

  • Cash Receipt Entry

  • Dining Reservations

  • Events

  • F&B Point-of-Sale

  • General

  • General Ledger

 

  • Golf TeeTimes

  • Member Check-In

  • Member-Guest Check-In

  • Member-Client

  • No Section Required

  • Periodic Billing

  • P/O Receiving

  • Purchasing

  • Retail Point-of-Sale

  • Room Accommodations

  • Room Deposit Entry

  • Room Phone Charges

  • Room Special Requests

  • Spa Module

  • Tennis

  • Vendors

 

Junctions (or Junctures) within Applications are also defined by Abacus 21.

 

Application Junction Examples for several of the Applications are:

 

Application

Junctures

Membership-Client

  • Client-Membership (Maintenance)

  • Client-Membership Inquiry Mode

  • Client Preferences

  • Client Service Type Preferences

F&B Point-of-Sale

  • Comet F/B Header (Legacy System)

  • Point-of-Sale Header Input

  • Point-of-Sale Payment Input

Spa Module

  • Spa Booking

  • Spa Client Preferences

  • Spa Service Type Preferences

  • Spa Staff Comments

  • Therapist Screen Client Notes

  • Therapist Screen Client Service Notes

  • Therapist Screen Staff Service Notes

 

It is sometimes the case that one Abacus 21 Application 'style' (such as 'Spa Module') is used for more than one actual type of applicational treatment -- for example, the Spa Module being used for: