Changes

NOTE: Focus here is on basic Submit Logic validation using Submit Buttons. Details on how Submit Buttons interact with SmartCheck validation will be covered in the [[SmartCheck_Validation#Add_SmartCheck_Validation_to_Submit_Button|SmartCheck Validation article.]]  ==Accessing the Submit Logic Function==

* Click the '''Settings''' tab within the UTA, then access the Level 1, 2 or 3 settings page as appropriate. * Click on the [[Statuses]] '''Submit & Save Buttons''' link in either the Level 1 settings section, or Level 2 settings sectionpage.[[Image:SubmitLogic1.png|800px]]

 * The '''Submit Button& Save Buttons''' tab page is displayed next to . It should list all existing Submit buttons, and have a option for [[Submit_buttons#Creating_A_Save_.26_Submit_Button|creating new submit buttons]] at the '''Status Trigger''' tab. Click on this or scroll down to top of the Submit Button sectionscreen.

[[Image:SubmitButton1SubmitLogic2.png|800px]]  * Click on the Edit icon for one of the listed Submit & Save Button options. You will be brought to the Submit Button configuration screen.  [[Image:SubmitLogic3.png|800px]]  

* Click on the hyperlink in Submit Logic tab. You will be brought to the Label column Submit Logic configuration screen, which should list all existing Submit logic, and have a option for creating new Submit Logic at the Submit Button that you intend to add logic againsttop of the screen.

In [[Image:SubmitLogic4.png|800px]]   * Click the resulting window scroll down New button to the '''begin adding new Submit Logic''' section. [[Image:SubmitLogic5.png|800px]]

 * '''Order''' - the order in which the condition can be executed. Each condition is executed in sequence based on the order. When all conditions have executed, any failed conditions will stop the submission process and all messages for failed conditions will be displayed in a consolidated fashion.* '''Name''' - a narrative name for the condition. * '''Description''' - narrative description of the condition. * '''Condition''' - stores the expression that represents the condition. [[Entity]] does not change status when condition evaluates as false.* '''Message''' - stores the message to be displayed if the condition is not met.  

'''''Conditions '' should be constructed so that they evaluate as TRUE when you want the record to be submitted.'''

'''The ''messageMessage'' will display when the condition evaluates as FALSE, and the record will not be submitted.'''

 1. '''Criteria''': The '''Reviewer Comments''' field at level 2 must not be left blank. '''"@level2.Reviewer Comments.length@"*1 > 0''' ''OR'' '''CONVERT("@level2.Reviewer Comments.length@",SIGNED INTEGER) > 0'''1<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Note that the above is the best practice for testing for empty fields, as opposed to using "@level2.Reviewer Comments@"!=""</pre> 2. '''Criteria''': a '''minimum of three''' level 2 items (''of any type'') are required to submit the level 1 item.

23. '''Criteria''': a '''minimum of three''' level 2 items '''where the type is email''' are required to submit the level 1 item.

34. '''Criteria''': a '''minimum of three''' level 2 items '''where the type is email''' and the '''status is closed''' (''for both items'').

45. '''Criteria''': the '''submission cut-off date and time has not passed''' now"@datetime(currentdate) @"< '"@systemdatetime(level1.closedateContract Start Date)@'"

  6. '''Criteria''': an '''XML table node is not blank''' "<ssEscape>@level1.xml.Budget.comment-section.row.comment.nodevalue@</ssEscape>" != "" 

* '''@level2.sum(cf_23232#12345#)@ > 5''' - same as previous example but using the [[Custom Field|custom field]] ID.* '''"@level1.Anticipated Project End Date@" BETWEEN "@rootcompany.Project Start Date@" AND "@rootcompany.Project End Date@"''' - the date entered into the ''Anticipated Project End Date'' field is between the system-wide Project Start and End Dates (see [[Root Company Variable]]s)* '''"@opportunity.peopleid@'"!='"0'"''' - Ensure that a contact has been added to the Level 1 Person standard field.* ''''"@contacts.count(*):rolename='Supervisor'@"="1'"''' - Ensure there is exactly 1 contact at Level 1 with the role of Supervisor.* ''''"@companies.count(*):rolename='Funding Agency'@"<"3'"''' - Ensures there are less than 3 Funding Agencies in the Companies section.* ''''"@contact.supervisor.email@'"!='"@contact.referee.email@'"''' - Ensure that the contact assigned at Level 1 with the role of Supervisor is not also assigned with the role Referee.

* '''"@level1.Plan Details.numofpages@"<=6''' - Ensures the number of pages for a multi-PDF file upload field is not more than six pages* '''"@level1.Multiple File Uploads.numoffiles@">0''' - Ensures the number of files uploaded to a Multiple Files upload field is greater than 0* '''"@level1.type@"!="New Grant"||"@level1.xml.ExternalPeers.peer.peer.nodecount@">2''' - Ensures that the level 1 type is 'New Grant' and number of nodes/ items entered in the XML worksheet is greater than 2 items.* '''"@level1.Amount Awarded.value@" <= 500000''' - Ensures that the ''Amount Awarded'' field is under $500,000. The ''.value'' is necessary when the ''Amount Awarded'' field is stored in currency format.* ''' INSTR("@level1.[#(?object=activity::criteria=typename='Referee Form' and statusname='Submitted' and eownerid=@me.userid@)~index~#]@","1")=0''' - Ensures the current user can't submit more than 1 review* ''' @level1.Grant Amount@>=@level1.level2.sum(#1478912.value#)@+@level2.#1478912.value#@''' - Confirms the payment total does not exceed the approved total.* ''' LENGTH("@level1.Check Boxes@")-LENGTH(REPLACE("@level1.Check Boxes@",";",""))+1>=3 ''' - Confirms that at least 3 checkboxes have been selected in a [[Custom Field Type: Select Many – Check Boxes|Select Many - Check Boxes]] field. <pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Note that semicolons cannot be included in submit logic criteria. If using list syntax, employ double colons ("::") to separate arguments.</pre>

[[Category:Universal Tracking Application]][[Category:Validation]][[Category:Process Flow]]