Table of Contents
Namespace: http://pos.whentomanage.com/updx/configuration
Table 1. Element: UPDX_CONFIGURATION
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
top level of the Universal POS DataXchange format: Configuration preferred date format is YYYY-MM-DD. Impossible dates, such as 2000-02-34, will not validate. preferred dateTime format is YYYY-MM-DDThh:mm:ss Year,month,dayThour,minute,second for dateTime datatypes. Impossible values, such as 2000-02-34T66:32:19, will not validate. Date Times/Times should all be in store local time. They do not include a timezone. Dates and times that are all zeros will cause an odd validation error "Code: 12, Description: Extra element [parent_element_name] in interleave" Preferred boolean values are 1 and 0, but acceptable boolean values are 1, 0, true, false |
Content Model |
VERSION ( EMPLOYEE )* , ( JOB )* , ( TENDER_TYPE )* , ( REVENUE_CENTER )* , ( COMP )* , ( PROMO )* , ( VOID )* , ( ACCOUNT )* , ( PAYMENT_REASON )* , ( VOUCHER )* , ( MENU_ITEM_CATEGORY )* , ( MENU_ITEM )* |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="UPDX_CONFIGURATION"> <element name="VERSION"> <choice> <value>1.1</value> </choice> </element> <a:documentation>top level of the Universal POS DataXchange format: Configuration</a:documentation> <a:documentation>preferred date format is YYYY-MM-DD. Impossible dates, such as 2000-02-34, will not validate.</a:documentation> <a:documentation>preferred dateTime format is YYYY-MM-DDThh:mm:ss Year,month,dayThour,minute,second for dateTime datatypes. Impossible values, such as 2000-02-34T66:32:19, will not validate.</a:documentation> <a:documentation>Date Times/Times should all be in store local time. They do not include a timezone.</a:documentation> <a:documentation>Dates and times that are all zeros will cause an odd validation error "Code: 12, Description: Extra element [parent_element_name] in interleave"</a:documentation> <a:documentation>Preferred boolean values are 1 and 0, but acceptable boolean values are 1, 0, true, false</a:documentation> <interleave> <zeroOrMore> <element name="EMPLOYEE"> <a:documentation>EMPLOYEE ID is the POS assigned, unique ID of the employee</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="EMPLOYEE_NUMBER"> <a:documentation>EMPLOYEE NUMBER is the Manager asssigned ID of the employee</a:documentation> <data type="string"/> </element> <element name="FIRST_NAME"> <data type="string"/> </element> <optional> <element name="MIDDLE_NAME"> <data type="string"/> </element> </optional> <element name="LAST_NAME"> <data type="string"/> </element> <optional> <element name="EMAIL"> <data type="string"/> </element> </optional> <optional> <element name="PHONE_HOME"> <data type="string"/> </element> </optional> <optional> <element name="PHONE_MOBILE"> <a:documentation>while any PHONEs may be populated with any phone number for this person, only PHONE_MOBILE will be used when sending SMS about schedules, messages, etc.</a:documentation> <data type="string"/> </element> </optional> <optional> <element name="PHONE_ALT"> <data type="string"/> </element> </optional> <optional> <element name="BIRTH_DATE"> <data type="date"/> </element> </optional> <optional> <element name="INACTIVE_DATE"> <a:documentation>Date at which employee was set to inactive or terminated, this may be de-populated later to reactivate the employee on the WTM side</a:documentation> <data type="date"/> </element> </optional> <optional> <element name="HIRE_DATE"> <data type="date"/> </element> </optional> <optional> <element name="ADDRESS"> <data type="string"/> </element> </optional> <optional> <element name="ADDRESS2"> <data type="string"/> </element> </optional> <optional> <element name="CITY"> <data type="string"/> </element> </optional> <optional> <element name="POSTAL_CODE"> <data type="string"/> </element> </optional> <optional> <element name="STATE_PROVINCE"> <data type="string"/> </element> </optional> <optional> <element name="COUNTRY"> <data type="string"/> </element> </optional> <zeroOrMore> <element name="EMPLOYEE_JOB"> <a:documentation>Each Job this employee may work</a:documentation> <interleave> <element name="JOB_ID"> <a:documentation>use POS assigned, unique ID for the job. This is the same ID which identifies the <JOB></a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="WAGE"> <a:documentation>Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="OT_WAGE"> <a:documentation>Overtime Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="IS_PRIMARY"> <a:documentation>in some systems a user may be assigned a primary job, which is their default job in cases where a job is not listed</a:documentation> <data type="boolean"/> </element> </interleave> </element> </zeroOrMore> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="JOB"> <a:documentation>Each job has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <optional> <element name="IS_SALARIED"> <a:documentation>Whether this job is a salaried position. Affects WTM schedule forecasting and reporting</a:documentation> <data type="boolean"/> </element> </optional> <optional> <element name="WAGE"> <a:documentation>Wage any employee may earn for this job, overridden in the employee if the employees themselves have wages for the job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> </optional> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="TENDER_TYPE"> <a:documentation>Each tender type has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="PAYMENT_TYPE"> <a:documentation>General category of this tender type</a:documentation> <choice> <value>CASH</value> <value>CREDIT_CARD</value> <value>GIFT_CARD</value> <value>ACCOUNT</value> <value>COUPON</value> <value>VOUCHER</value> <value>MISC</value> </choice> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="REVENUE_CENTER"> <a:documentation>Each revenue center has a POS assigned, unique ID </a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="COMP"> <a:documentation>Each complimentary reason has a POS assigned, unique ID </a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="PROMO"> <a:documentation>Each promotion reason has a POS assigned, unique ID</a:documentation> <a:documentation>promotions is also expected to include coupons, so even if the POS has a separate Coupon setup, they go into PROMO</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="VOID"> <a:documentation>Each void reason has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="ACCOUNT"> <a:documentation>Each house account has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="PAYMENT_REASON"> <a:documentation>Reasons for Paid Ins/Outs should include the default "direction" (in or out)</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="IN_OUT"> <a:documentation>IN = money into cash. OUT = money out of cash. Show the default for this reason. Individual paid ins/outs may differ in direction that the default for their Reason.</a:documentation> <choice> <value>IN</value> <value>OUT</value> </choice> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="VOUCHER"> <a:documentation>Each voucher type has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="MENU_ITEM_CATEGORY"> <a:documentation>Each menu category has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="PARENT_CATEGORY_ID"> <a:documentation>if there is a hierarchy, this should be the id of the category directly above this one</a:documentation> <a:documentation>if there is no hierarchy in the POS, this should be 0</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <optional> <element name="INCLUDED_IN_NET_SALES"> <a:documentation>should the sales of this category be included in net sales reported numbers? This will default to True if not present.</a:documentation> <data type="boolean"/> </element> </optional> </interleave> </element> </zeroOrMore> <zeroOrMore> <element name="MENU_ITEM"> <a:documentation>Each menu item has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="CATEGORY_ID"> <a:documentation>ID of the Category containing this menu item</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="IS_MODIFIER"> <data type="boolean"/> </element> <element name="PRICE"> <a:documentation>Nominal price of menu item</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> </data> </element> <optional> <element name="SKU"> <a:documentation>Unique SKU to identify menu item, if this is kept consistent across stores it could be used to identify matching items, even when the POS IDs differ</a:documentation> <data type="string"/> </element> </optional> </interleave> </element> </zeroOrMore> </interleave> </element> |
Table 2. Element: VERSION
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
( "1.1" ) |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="VERSION"> <choice> <value>1.1</value> </choice> </element> |
Table 3. Element: EMPLOYEE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
EMPLOYEE ID is the POS assigned, unique ID of the employee |
Content Model |
ID, EMPLOYEE_NUMBER, FIRST_NAME, MIDDLE_NAME ? , LAST_NAME, EMAIL ? , PHONE_HOME ? , PHONE_MOBILE ? , PHONE_ALT ? , BIRTH_DATE ? , INACTIVE_DATE ? , HIRE_DATE ? , ADDRESS ? , ADDRESS2 ? , CITY ? , POSTAL_CODE ? , STATE_PROVINCE ? , COUNTRY ? , ( EMPLOYEE_JOB )* |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="EMPLOYEE"> <a:documentation>EMPLOYEE ID is the POS assigned, unique ID of the employee</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="EMPLOYEE_NUMBER"> <a:documentation>EMPLOYEE NUMBER is the Manager asssigned ID of the employee</a:documentation> <data type="string"/> </element> <element name="FIRST_NAME"> <data type="string"/> </element> <optional> <element name="MIDDLE_NAME"> <data type="string"/> </element> </optional> <element name="LAST_NAME"> <data type="string"/> </element> <optional> <element name="EMAIL"> <data type="string"/> </element> </optional> <optional> <element name="PHONE_HOME"> <data type="string"/> </element> </optional> <optional> <element name="PHONE_MOBILE"> <a:documentation>while any PHONEs may be populated with any phone number for this person, only PHONE_MOBILE will be used when sending SMS about schedules, messages, etc.</a:documentation> <data type="string"/> </element> </optional> <optional> <element name="PHONE_ALT"> <data type="string"/> </element> </optional> <optional> <element name="BIRTH_DATE"> <data type="date"/> </element> </optional> <optional> <element name="INACTIVE_DATE"> <a:documentation>Date at which employee was set to inactive or terminated, this may be de-populated later to reactivate the employee on the WTM side</a:documentation> <data type="date"/> </element> </optional> <optional> <element name="HIRE_DATE"> <data type="date"/> </element> </optional> <optional> <element name="ADDRESS"> <data type="string"/> </element> </optional> <optional> <element name="ADDRESS2"> <data type="string"/> </element> </optional> <optional> <element name="CITY"> <data type="string"/> </element> </optional> <optional> <element name="POSTAL_CODE"> <data type="string"/> </element> </optional> <optional> <element name="STATE_PROVINCE"> <data type="string"/> </element> </optional> <optional> <element name="COUNTRY"> <data type="string"/> </element> </optional> <zeroOrMore> <element name="EMPLOYEE_JOB"> <a:documentation>Each Job this employee may work</a:documentation> <interleave> <element name="JOB_ID"> <a:documentation>use POS assigned, unique ID for the job. This is the same ID which identifies the <JOB></a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="WAGE"> <a:documentation>Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="OT_WAGE"> <a:documentation>Overtime Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="IS_PRIMARY"> <a:documentation>in some systems a user may be assigned a primary job, which is their default job in cases where a job is not listed</a:documentation> <data type="boolean"/> </element> </interleave> </element> </zeroOrMore> </interleave> </element> |
Table 4. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 5. Element: EMPLOYEE_NUMBER
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
EMPLOYEE NUMBER is the Manager asssigned ID of the employee |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="EMPLOYEE_NUMBER"> <a:documentation>EMPLOYEE NUMBER is the Manager asssigned ID of the employee</a:documentation> <data type="string"/> </element> |
Table 6. Element: FIRST_NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="FIRST_NAME"> <data type="string"/> </element> |
Table 7. Element: MIDDLE_NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="MIDDLE_NAME"> <data type="string"/> </element> |
Table 8. Element: LAST_NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="LAST_NAME"> <data type="string"/> </element> |
Table 9. Element: EMAIL
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="EMAIL"> <data type="string"/> </element> |
Table 10. Element: PHONE_HOME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PHONE_HOME"> <data type="string"/> </element> |
Table 11. Element: PHONE_MOBILE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
while any PHONEs may be populated with any phone number for this person, only PHONE_MOBILE will be used when sending SMS about schedules, messages, etc. |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PHONE_MOBILE"> <a:documentation>while any PHONEs may be populated with any phone number for this person, only PHONE_MOBILE will be used when sending SMS about schedules, messages, etc.</a:documentation> <data type="string"/> </element> |
Table 12. Element: PHONE_ALT
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PHONE_ALT"> <data type="string"/> </element> |
Table 13. Element: BIRTH_DATE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:date |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="BIRTH_DATE"> <data type="date"/> </element> |
Table 14. Element: INACTIVE_DATE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Date at which employee was set to inactive or terminated, this may be de-populated later to reactivate the employee on the WTM side |
Content Model |
xsd:date |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="INACTIVE_DATE"> <a:documentation>Date at which employee was set to inactive or terminated, this may be de-populated later to reactivate the employee on the WTM side</a:documentation> <data type="date"/> </element> |
Table 15. Element: HIRE_DATE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:date |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="HIRE_DATE"> <data type="date"/> </element> |
Table 16. Element: ADDRESS
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ADDRESS"> <data type="string"/> </element> |
Table 17. Element: ADDRESS2
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ADDRESS2"> <data type="string"/> </element> |
Table 18. Element: CITY
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="CITY"> <data type="string"/> </element> |
Table 19. Element: POSTAL_CODE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="POSTAL_CODE"> <data type="string"/> </element> |
Table 20. Element: STATE_PROVINCE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="STATE_PROVINCE"> <data type="string"/> </element> |
Table 21. Element: COUNTRY
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="COUNTRY"> <data type="string"/> </element> |
Table 22. Element: EMPLOYEE_JOB
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each Job this employee may work |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="EMPLOYEE_JOB"> <a:documentation>Each Job this employee may work</a:documentation> <interleave> <element name="JOB_ID"> <a:documentation>use POS assigned, unique ID for the job. This is the same ID which identifies the <JOB></a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="WAGE"> <a:documentation>Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="OT_WAGE"> <a:documentation>Overtime Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> <element name="IS_PRIMARY"> <a:documentation>in some systems a user may be assigned a primary job, which is their default job in cases where a job is not listed</a:documentation> <data type="boolean"/> </element> </interleave> </element> |
Table 23. Element: JOB_ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
use POS assigned, unique ID for the job. This is the same ID which identifies the <JOB> |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="JOB_ID"> <a:documentation>use POS assigned, unique ID for the job. This is the same ID which identifies the <JOB></a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 24. Element: WAGE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Wage Employee earns for this job |
Content Model |
xsd:decimal |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="WAGE"> <a:documentation>Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> |
Table 25. Element: OT_WAGE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Overtime Wage Employee earns for this job |
Content Model |
xsd:decimal |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="OT_WAGE"> <a:documentation>Overtime Wage Employee earns for this job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> |
Table 26. Element: IS_PRIMARY
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
in some systems a user may be assigned a primary job, which is their default job in cases where a job is not listed |
Content Model |
xsd:boolean |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="IS_PRIMARY"> <a:documentation>in some systems a user may be assigned a primary job, which is their default job in cases where a job is not listed</a:documentation> <data type="boolean"/> </element> |
Table 27. Element: JOB
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each job has a POS assigned, unique ID |
Content Model |
ID, NAME, IS_SALARIED ? , WAGE ? |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="JOB"> <a:documentation>Each job has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <optional> <element name="IS_SALARIED"> <a:documentation>Whether this job is a salaried position. Affects WTM schedule forecasting and reporting</a:documentation> <data type="boolean"/> </element> </optional> <optional> <element name="WAGE"> <a:documentation>Wage any employee may earn for this job, overridden in the employee if the employees themselves have wages for the job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> </optional> </interleave> </element> |
Table 28. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 29. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 30. Element: IS_SALARIED
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Whether this job is a salaried position. Affects WTM schedule forecasting and reporting |
Content Model |
xsd:boolean |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="IS_SALARIED"> <a:documentation>Whether this job is a salaried position. Affects WTM schedule forecasting and reporting</a:documentation> <data type="boolean"/> </element> |
Table 31. Element: WAGE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Wage any employee may earn for this job, overridden in the employee if the employees themselves have wages for the job |
Content Model |
xsd:decimal |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="WAGE"> <a:documentation>Wage any employee may earn for this job, overridden in the employee if the employees themselves have wages for the job</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> <param name="minInclusive">0</param> </data> </element> |
Table 32. Element: TENDER_TYPE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each tender type has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="TENDER_TYPE"> <a:documentation>Each tender type has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="PAYMENT_TYPE"> <a:documentation>General category of this tender type</a:documentation> <choice> <value>CASH</value> <value>CREDIT_CARD</value> <value>GIFT_CARD</value> <value>ACCOUNT</value> <value>COUPON</value> <value>VOUCHER</value> <value>MISC</value> </choice> </element> </interleave> </element> |
Table 33. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 34. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 35. Element: PAYMENT_TYPE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
General category of this tender type |
Content Model |
( "CASH" | "CREDIT_CARD" | "GIFT_CARD" | "ACCOUNT" | "COUPON" | "VOUCHER" | "MISC" ) |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PAYMENT_TYPE"> <a:documentation>General category of this tender type</a:documentation> <choice> <value>CASH</value> <value>CREDIT_CARD</value> <value>GIFT_CARD</value> <value>ACCOUNT</value> <value>COUPON</value> <value>VOUCHER</value> <value>MISC</value> </choice> </element> |
Table 36. Element: REVENUE_CENTER
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each revenue center has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="REVENUE_CENTER"> <a:documentation>Each revenue center has a POS assigned, unique ID </a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 37. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 38. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 39. Element: COMP
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each complimentary reason has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="COMP"> <a:documentation>Each complimentary reason has a POS assigned, unique ID </a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 40. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 41. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 42. Element: PROMO
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each promotion reason has a POS assigned, unique ID promotions is also expected to include coupons, so even if the POS has a separate Coupon setup, they go into PROMO |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PROMO"> <a:documentation>Each promotion reason has a POS assigned, unique ID</a:documentation> <a:documentation>promotions is also expected to include coupons, so even if the POS has a separate Coupon setup, they go into PROMO</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 43. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 44. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 45. Element: VOID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each void reason has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="VOID"> <a:documentation>Each void reason has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 46. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 47. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 48. Element: ACCOUNT
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each house account has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ACCOUNT"> <a:documentation>Each house account has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 49. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 50. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 51. Element: PAYMENT_REASON
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Reasons for Paid Ins/Outs should include the default "direction" (in or out) |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PAYMENT_REASON"> <a:documentation>Reasons for Paid Ins/Outs should include the default "direction" (in or out)</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="IN_OUT"> <a:documentation>IN = money into cash. OUT = money out of cash. Show the default for this reason. Individual paid ins/outs may differ in direction that the default for their Reason.</a:documentation> <choice> <value>IN</value> <value>OUT</value> </choice> </element> </interleave> </element> |
Table 52. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 53. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 54. Element: IN_OUT
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
IN = money into cash. OUT = money out of cash. Show the default for this reason. Individual paid ins/outs may differ in direction that the default for their Reason. |
Content Model |
( "IN" | "OUT" ) |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="IN_OUT"> <a:documentation>IN = money into cash. OUT = money out of cash. Show the default for this reason. Individual paid ins/outs may differ in direction that the default for their Reason.</a:documentation> <choice> <value>IN</value> <value>OUT</value> </choice> </element> |
Table 55. Element: VOUCHER
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each voucher type has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="VOUCHER"> <a:documentation>Each voucher type has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> </interleave> </element> |
Table 56. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 57. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 58. Element: MENU_ITEM_CATEGORY
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each menu category has a POS assigned, unique ID |
Content Model | |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="MENU_ITEM_CATEGORY"> <a:documentation>Each menu category has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="PARENT_CATEGORY_ID"> <a:documentation>if there is a hierarchy, this should be the id of the category directly above this one</a:documentation> <a:documentation>if there is no hierarchy in the POS, this should be 0</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <optional> <element name="INCLUDED_IN_NET_SALES"> <a:documentation>should the sales of this category be included in net sales reported numbers? This will default to True if not present.</a:documentation> <data type="boolean"/> </element> </optional> </interleave> </element> |
Table 59. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 60. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 61. Element: PARENT_CATEGORY_ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
if there is a hierarchy, this should be the id of the category directly above this one if there is no hierarchy in the POS, this should be 0 |
Content Model |
xsd:nonNegativeInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PARENT_CATEGORY_ID"> <a:documentation>if there is a hierarchy, this should be the id of the category directly above this one</a:documentation> <a:documentation>if there is no hierarchy in the POS, this should be 0</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 62. Element: INCLUDED_IN_NET_SALES
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
should the sales of this category be included in net sales reported numbers? This will default to True if not present. |
Content Model |
xsd:boolean |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="INCLUDED_IN_NET_SALES"> <a:documentation>should the sales of this category be included in net sales reported numbers? This will default to True if not present.</a:documentation> <data type="boolean"/> </element> |
Table 63. Element: MENU_ITEM
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Each menu item has a POS assigned, unique ID |
Content Model |
ID, NAME, CATEGORY_ID, IS_MODIFIER, PRICE, SKU ? |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="MENU_ITEM"> <a:documentation>Each menu item has a POS assigned, unique ID</a:documentation> <interleave> <element name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> <element name="CATEGORY_ID"> <a:documentation>ID of the Category containing this menu item</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> <element name="IS_MODIFIER"> <data type="boolean"/> </element> <element name="PRICE"> <a:documentation>Nominal price of menu item</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> </data> </element> <optional> <element name="SKU"> <a:documentation>Unique SKU to identify menu item, if this is kept consistent across stores it could be used to identify matching items, even when the POS IDs differ</a:documentation> <data type="string"/> </element> </optional> </interleave> </element> |
Table 64. Element: ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
POS assigned, unique ID |
Content Model |
xsd:positiveInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="ID"> <a:documentation>POS assigned, unique ID</a:documentation> <data type="positiveInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 65. Element: NAME
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Text description of item |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="NAME"> <a:documentation>Text description of item</a:documentation> <data type="string"/> </element> |
Table 66. Element: CATEGORY_ID
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
ID of the Category containing this menu item |
Content Model |
xsd:nonNegativeInteger |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="CATEGORY_ID"> <a:documentation>ID of the Category containing this menu item</a:documentation> <data type="nonNegativeInteger"> <param name="maxInclusive">4294967295</param> </data> </element> |
Table 67. Element: IS_MODIFIER
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
None |
Content Model |
xsd:boolean |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="IS_MODIFIER"> <data type="boolean"/> </element> |
Table 68. Element: PRICE
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Nominal price of menu item |
Content Model |
xsd:decimal |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="PRICE"> <a:documentation>Nominal price of menu item</a:documentation> <data type="decimal"> <param name="fractionDigits">2</param> </data> </element> |
Table 69. Element: SKU
Namespace |
http://pos.whentomanage.com/updx/configuration |
Documentation |
Unique SKU to identify menu item, if this is kept consistent across stores it could be used to identify matching items, even when the POS IDs differ |
Content Model |
xsd:string |
Source |
<element xmlns="http://relaxng.org/ns/structure/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" name="SKU"> <a:documentation>Unique SKU to identify menu item, if this is kept consistent across stores it could be used to identify matching items, even when the POS IDs differ</a:documentation> <data type="string"/> </element> |