external.schematron.timecard.1.4.xslt.RTE-v1.4-TimeCard.xslt Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of phive-rules-setu Show documentation
Show all versions of phive-rules-setu Show documentation
SETU Standards validation rules for phive
/
[
*[local-name()='
']
[
/
@
@*[local-name()='
' and namespace-uri()='
']
/
[
]
/
[
]
.
U
U
U.
n
U.
_
_
Business rules voor het controleren van een timecard bericht (SETU Standard for Reporting Time & Expenses versie 1.4).
A timecard should have exactly one Id element, with exactly one idOwner attribuut and one IdValue element.
The idOwner attribute of Id should have the value 'StaffingCustomer'.
The Person/Id element should have exactly one idOwner attribute, with the value 'StaffingCustomer' or 'StaffingCompany'.
Currently '
The Person/Id element should contain exactly one IdValue element.
The PersonName element should contain exactly one non-empty FormattedName element.
The ReportedTime element must exist exactly once.
The status of a ReportedTime element must be empty or contain 'rejected'.
The attribute actionCode of TimeInterval must contain one of the following values:
The TimeInterval/Id element should have exactly one idOwner attribute.
The TimeInterval/Id element may have at most one IdValue element.
For a TimeInterval the EndDateTime element must be present if no Duration element is provided.
For a TimeInterval the Duration element must be present if no EndDateTime element is provided.
The attribute type of the element RateOrAmount must contain one of the following values:
The attribute multiplier of the element RateOrAmount must be present exactly once and contain a value greater of equal to 100.
The attribute actionCode of Allowance must contain one of the following values:
The Allowance/Id element should have exactly one idOwner attribute.
The Allowance/Id element should have exactly one IdValue element.
The name attribute of the Allowance/Id/IdValue element should exist exactly once and must have the value 'expense' or 'allowance'.
Currently '
An Allowance must contain exactly one Amount element.
The element CustomerReportingRequirements contains (a) subelement(s) that is/are not allowed.
For each AdditionalRequirement the attribute requirementTitle must exist exactly once and may not be empty .
The idOwner attributes of the StaffingSupplierId elements are not unique.
The attribute idOwner of the element StaffingSupplierId must exist exactly once and should have a valid value:
The subelement IdValue of the element StaffingSupplierId must exist exactly once.
The idOwner attributes of the StaffingCustomerId elements are not unique.
The attribute idOwner of the element StaffingCustomerId must exist exactly once and should have a valid value:
The subelement IdValue of the element StaffingCustomerId must exist exactly once.
The attribute idOwner of the element AssignmentId must exist exactly once and should have the valid value 'StaffingCompany'.
Currently '
The subelement IdValue of the element AssignmentId must exist exactly once.
The idOwner attributes of the StaffingSupplierOrgUnitId elements are not unique.
The attribute idOwner of the element StaffingSupplierOrgUnitId must exist exactly once and should have a valid value:
The subelement IdValue of the element StaffingSupplierOrgUnitId must exist exactly once.
The idOwner attributes of the StaffingCustomerOrgUnitId elements are not unique.
The attribute idOwner of the element StaffingCustomerOrgUnitId must exist exactly once and should have a valid value:
The subelement IdValue of the element StaffingCustomerOrgUnitId must exist exactly once.
A negative Duration is provided: '
Each AdditionalData element must have exactly one StaffingAdditionalData element as a child.
Value '
Value '