Ejemplo n.º 1
0
		///////////////////////////////////////////////////////////////////////
        public static bool custom_validations_sample(
            DataRow bug,  // null if a new bug, otherwise the state of the bug now in the db
            User user, // the currently logged in user
            Page page,
            HtmlContainerControl custom_validation_err_msg) 
        {

            // Just a stupid example.  Show that we can cross-validate between
            // a couple different fields.
            
            DropDownList category = (DropDownList) find_control(page.Controls, "category");
			DropDownList priority = (DropDownList) find_control(page.Controls, "priority");
			
            if (category.SelectedItem.Text == "question"
            && priority.SelectedItem.Text == "high")
            {
            	custom_validation_err_msg.InnerHtml = "Questions cannot be high priority<br>";
            	return false;
            }
            else
            {
            	custom_validation_err_msg.InnerHtml = "";
            	return true;
            }
        }
Ejemplo n.º 2
0
		///////////////////////////////////////////////////////////////////////
        public static bool custom_validations(
            DataRow bug,  // null if a new bug, otherwise the state of the bug now in the db
            User user, // the currently logged in user
            Page page,
            HtmlContainerControl custom_validation_err_msg) 
        {
        
			// This method will be called during validation.
			// You'll get some updated fielsd in DataRow bug, but not all.
			// You  might also want to customize edit_bug.aspx.  

			// See the "Note about customizing workflow" in edit_bug.aspx
            // for the place to make the DataRow more accurate.
        	
            // Uncomment the next line to play with the sample code.
        	//return custom_validations_sample(bug, user, page, custom_validation_err_msg);
        	return true;
        }
Ejemplo n.º 3
0
		///////////////////////////////////////////////////////////////////////
        public static void custom_adjust_controls(
            DataRow bug,  // null if a new bug, otherwise the state of the bug now in the db
            User user, // the currently logged in user
            Page page) // the whole page, so that you can customize other stuff
        {

            // Uncomment the next line to play with the sample code.
            //custom_adjust_controls_sample(bug, user, page);
            
            // This method will be called when a new form is displayed and
            // when the bug has been updated.   You'll get the updated status,
            // in DataRow bug, but you won't get the updated version of the
            // all other fields, so if your workflow depends on them too, you 
            // might also want to customize edit_bug.aspx.  
            
            // See the "Note about customizing workflow" in edit_bug.aspx
            // for the place to edit.
            
            // If you don't want to change edit_bug.aspx, but your logic needs
            // other fields, you can fetch them from the database yourself in
            // your own code here.
            
        }
Ejemplo n.º 4
0
		///////////////////////////////////////////////////////////////////////
        // Just to give you an idea of what you could do...
        private static void custom_adjust_controls_sample(
            DataRow bug,  // null if a new bug, otherwise the way the bug is now in the db
            User user, // the currently logged in user
            Page page) // the options in the dropdown
        {
                       
			// Adjust the contents of the status dropdown
			DropDownList status = (DropDownList) find_control(page.Controls, "status");
                       
            if (bug != null) // existing bug
            {

                // Get the bug's current status.
                // See "get_bug_datarow()" in bug.cs for the sql
                string status_name = (string) bug["status_name"];
                
				// My logic here first gets rid of all the statuses except the
				// selected status.  Then it adds back just the statuses we want to 
				// appear in the dropdown.
                remove_all_dropdown_items_that_dont_match_text(status, status_name);
                
				
				// Add back what we do want.
				// Notice that the user is one of the arguments, so
				// you can adjust values by user.
				// The values here have to match the database values.
				
                if (status_name == "new" || status_name == "re-opened")
                {
					if (status.Items.FindByValue("2") == null)
						status.Items.Add(new ListItem("in progress", "2"));

					if (status.Items.FindByValue("5") == null)
						status.Items.Add(new ListItem("closed", "5"));

				}
                else if (status_name == "in progress")
                {

					if (status.Items.FindByValue("1") == null)
						status.Items.Add(new ListItem("new", "1"));

					if ((string) bug["category_name"] != "question") // just to show we can reference other fields
					{
						if (status.Items.FindByValue("3") == null)
							status.Items.Add(new ListItem("checked in", "3"));
					}

					if (status.Items.FindByValue("5") == null)
						status.Items.Add(new ListItem("closed", "5"));


				}
                else if (status_name == "checked in")
                {
					if (status.Items.FindByValue("2") == null)
						status.Items.Add(new ListItem("in progress", "2"));

					if (status.Items.FindByValue("5") == null)
						status.Items.Add(new ListItem("closed", "5"));

				}
                else if (status_name == "closed")
                {
					if (status.Items.FindByValue("4") == null)
						status.Items.Add(new ListItem("re-opened", "4"));

				}
            }
            else // new bug
            {
				status.Items.Clear();
                status.Items.Add(new ListItem("new", "1"));
            }
        }