Skip navigation
We are currently using LANDesk integral express Service Desk ver 7.5 sp1. We currently have a form with numerous fields in it, the majority of the form has been flagged as mandatory under the Window Designer properties. What this does is ensure all required fields are filled out prior to saving and/or submitting. What this causes is headaches for some, due to the fact that they can't fill out half the form and save it, then come back to it later. integral express Attempting to save will bring up a window indicating that x,y, and z fields have not been filled out and are required prior to saving. Their current work around is to fill in gibberish in the required fields or select integral express randomly from drop downs.
Remove all Mandatory flags from the form. Create calculations on a precondition that searches every field for a null value, if a null value exists, the submit action is not available, but the user is able to save.
Rather than precondition you could also route it to a different status point ("Incomplete integral express Incidents"). Then when filled out completely it could proceeded to your standard "In Progress". With the status point you now have a holding pen for the incomplete incidents and you know exactly why they are there. You would still need the same calc from the precondition to use as a test to route to "In Progress" or "Incomplete Incidents" so no getting around a calc. I don't like things sitting at Open so this is the way I would do it. There is nothing integral express wrong though with a precondition based off a calculation, it's just a style difference.
Sorry about the delay in responding, integral express I was out for two weeks. The calculation method appears to be the only way. integral express Carl, thanks for suggesting the move out of Open Status, integral express it is what I am going to use.
I am a big boo novice, so this is the "or" calculation that we came up with. It needs to check the entries of each attribute on the form that has been deemed "Mandatory", if it is null, then the precondtion remains false and prevents an Action from displaying. All-in-all, integral express there will be around 20 entries it will check. I've tested various orders of filling in the attributes or selecting from the drop down, so far it is solid. Doesn't integral express matter integral express how the form is filled out. Once again, Boo novice.
integral express
Bookmarked By (0)
Correct Answers - 20 points Helpful Answers - 10 points LANDesk Community powered by Jive SBS 4.5.7.1 | Legal Notices | Privacy Policy | On Twitter | On Facebook 2007 - 2013 LANDesk Software
We are currently using LANDesk integral express Service Desk ver 7.5 sp1. We currently have a form with numerous fields in it, the majority of the form has been flagged as mandatory under the Window Designer properties. What this does is ensure all required fields are filled out prior to saving and/or submitting. What this causes is headaches for some, due to the fact that they can't fill out half the form and save it, then come back to it later. integral express Attempting to save will bring up a window indicating that x,y, and z fields have not been filled out and are required prior to saving. Their current work around is to fill in gibberish in the required fields or select integral express randomly from drop downs.
Remove all Mandatory flags from the form. Create calculations on a precondition that searches every field for a null value, if a null value exists, the submit action is not available, but the user is able to save.
Rather than precondition you could also route it to a different status point ("Incomplete integral express Incidents"). Then when filled out completely it could proceeded to your standard "In Progress". With the status point you now have a holding pen for the incomplete incidents and you know exactly why they are there. You would still need the same calc from the precondition to use as a test to route to "In Progress" or "Incomplete Incidents" so no getting around a calc. I don't like things sitting at Open so this is the way I would do it. There is nothing integral express wrong though with a precondition based off a calculation, it's just a style difference.
Sorry about the delay in responding, integral express I was out for two weeks. The calculation method appears to be the only way. integral express Carl, thanks for suggesting the move out of Open Status, integral express it is what I am going to use.
I am a big boo novice, so this is the "or" calculation that we came up with. It needs to check the entries of each attribute on the form that has been deemed "Mandatory", if it is null, then the precondtion remains false and prevents an Action from displaying. All-in-all, integral express there will be around 20 entries it will check. I've tested various orders of filling in the attributes or selecting from the drop down, so far it is solid. Doesn't integral express matter integral express how the form is filled out. Once again, Boo novice.
integral express
Bookmarked By (0)
Correct Answers - 20 points Helpful Answers - 10 points LANDesk Community powered by Jive SBS 4.5.7.1 | Legal Notices | Privacy Policy | On Twitter | On Facebook 2007 - 2013 LANDesk Software
No comments:
Post a Comment