Added the ability to restrict employees from submitting a custom XML form until they open mandatory policy files that are attached to the form. To support this functionality, a new tag, <DocReviewValidationBinding>, is now available. You can include a <DocReviewValidationBinding> tag and an <AttachedEntityId> tag in an <UploadDownload> control tag to add a read-only checkbox to your form. The checkbox is placed above the list of documents with a label that states that the user opened each document. When an employee opens all of the attached documents, the checkbox is selected and the employee can submit the form. If the employee tries to submit the form without viewing all of the documents, an error message shows that reminds them to view every document. For tag usage information and code samples, see the XML Forms Guide. | |
Updated the Any/All/None/Filter grouping functions in the workflow expression engine to work with the UpdateStatus parameter to provide an additional level of list filtering. UpdateStatus can evaluate the following list item statuses:
UpdateStatus uses the following basic syntax, where the status names must be in quotes: List.Any/All/None(UpdateStatus Equals "None/Insert/Update/Delete") For example, you can use UpdateStatus to evaluate PersonContactPhoneNumber list items that are not deleted: List_PersonContactPhoneNumber.Any(NOT UpdateStatus EQUALS "delete" AND COALESCE(ContactNumber, "NULL") EQUALS "NULL") For usage information and code samples, see the XML Forms Guide. | |
Updated the <RateSelector> tag used in custom and system XML forms to support the user's Numeric Culture field selection in the User Properties section of the Security Settings screen in People. For example, the New Hire form no longer shows a validation error in the form's Base Rate field if a German user enters a comma instead of a period as a decimal separator. | |
Clarified the standard error message that is shown when a user enters a value in a field that’s outside of the regular expression definition in a <RegExp> tag. This standard message is used if you didn’t define a custom <RegExpErrorMessage> tag. | |
Removed the status bar from the bottom of the text editor in the following areas of Dayforce to offer a more simplified user experience:
|