Glossary: A

Generally this refers to a specific type of work.  Most organizations define a list of activities that cover all of the work performed by their staff, organized by category, department, etc. This may also refer to a 3-digit code that references such an activity. In some cases it also refers to a block of work that defines the activity\, worker\, location\, start time\, end time\, duration (may include deducted time for breaks)\, and other data pertaining to the activity.  This is also sometimes referred to as an "activity block" or a "punch" in some instances.
An allocation rule is used to help apply a portion of a worker's time to different areas where that 'allocation' can be more specfic than an idividual punch or activity block. For example\, a person may drive a forklift for the day\, but a portion of their time needs to be allocated to greenhouse work and a portion needs to be allocated to grading work. An allocation rule is used to help define the business logic explicitly for those hours or costs to be allocated in that way.
Generally this refers to an error that has been encountered while using any of the Oasis applications. Sometimes the error is actually a bug in the program where something unexpected has occurred that it cannot recover from. At other times\, it may be that an invalid date or number has been entered\, and needs to be corrected before continuing. This is almost always accompanied by a more detailed explanation of what has happened and what actions\, if any\, need to be taken to prevent the error from appearing again.
The Oasis Authenticator is just a tool used to help make it easier to login to the Oasis Desktop app or the Oasis Tablet app by presenting a QR Code with encrypted authentication information. For example\, after logging into the Oasis Desktop app\, the Oasis Authenticator can be displayed. The Oasis Tablet app can then read the QR Code and login using the same credentials.
Any time an application exception or other critical error is encountered by any of the Oasis applications\, an error report is automatically created and logged with the 500 Foods bug tracking database\, and appropriate notification emails are sent to developers responsible for each application. This entire process is automated\, and typically includes more than enough information to figure out what has gone wrong. In some instances\, a developer may need to find out more about what was happening immediately prior to the error.