Hi, Well, this is not the same thing as the old macros that could prompt for input...
You are right about the $xxx$. In the SYS:Predefined Queries the fields say External, which to me sound like it is used in an EXTERNAL() search possibly in a table field. I was guessing that the EXTERNAL() would support something like $536871913$ or $Enter Date$ if you have such a field on the current form. So if you add these fields in there you might get this to work. Or maybe you should create your own display-only-form instead with a table-field and the prompt functionality you need. This way you need not change anything in existing ITSM forms and workflow. Best Regards - Misi, RRR AB, http://www.rrr.se (http://www.rrr.se) (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13) * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs Find these products, and many free tools and utilities, at http://rrr.se (http://rrr.se) January 31, 2017 9:46 PM, "Brian Pancia" wrote: Misi - $Enter Date$ is just the parameter wording. So if you use 'Submit Date' >= "$Enter Date$" in the advanced search bar it will prompt you for a date and the results will return anything created after that date. You can save this search and run it as your own search. You could also put this in the defined searches and I believe it will work fine. However, if you try do build a search qualification on the Incident Management Console using the SYS:Predefined Queries form it gives you an invalid date format. I know with keywords like $NULL$ you need to put $NULL$ for it to take it. I've played around with quotes and single tics around the parameter but I keep getting invalid date format. This form essentially builds the external qualification for the table. I don't recall ever trying to use parameters on external qualifications. I'm trying to limit the amount of customizations and put as much control into the end users hands as possible. Using SYS:Predefined Queries would work well. I could have users build their own queries and the ones they deemed worthy I could make accessible to a group of people by setting restricted access on SYS:Predefined Queries. Brian ------------------------------------ From: Action Request System discussion list(ARSList) on behalf of Jason Miller Sent: Tuesday, January 31, 2017 12:30 PM To: [email protected] (mailto:[email protected]) Subject: Re: Defined Searches **Reading this again I might have answer the wrong question. I was talking about saving a keyword in a record but I think you are looking how to save a parameter prompt as in https://docs.bmc.com/docs/display/public/ars91/Including+parameters+in+saved+or+defined+searches (https://docs.bmc.com/docs/display/public/ars91/Including+parameters+in+saved+or+defined+searches) On Tue, Jan 31, 2017 at 9:20 AM, Jason Miller wrote: After the first dollar sign is correct. At least that is how I have always done it and am doing here: https://communities.bmc.com/message/547542 (https://communities.bmc.com/message/547542) On Tue, Jan 31, 2017 at 8:46 AM, Misi Mladoniczky wrote:** Hi, I thought the backslash was before the last $, but I might be wrong... And does the $Enter Date$ field exist on the form? You might need to add it. Best Regards - Misi, RRR AB, http://www.rrr.se (http://www.rrr.se) (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13) * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs Find these products, and many free tools and utilities, at http://rrr.se (http://rrr.se) January 31, 2017 3:22 PM, "Brian Pancia" wrote: I'm thinking for this requirement I may have to utilize SYS:Predefined Queries on the Incident Management console and then add the ability to select all and print to csv file. I'm trying to find the right syntax to utilize parameters in SYS:Predefined Queries though. I tried "$Enter Date$" and "$Enter Date$" but nether one of those worked. Have you guys used parameters in setting up these searches? Brian ------------------------------------ From: Brian Pancia Sent: Monday, January 30, 2017 12:46 PM To: [email protected] (mailto:[email protected]) Subject: Re: Defined Searches Well that's not good. I have multiple companies using the system and was hoping to use a backend form to control the searches without doing a whole lot of customization. I was hoping it pulled off the AR System Search Preferences. They want to run a bunch of searches based on an start/end date. I want to set this based on permissions. They also want to be able to export this data as needed to a csv file. Just doing reports won't work because they may only want to drill into the individual ticket data, in which they would only need the search and not need the report. Back to the drawing board. Brian. ------------------------------------ From: Action Request System discussion list(ARSList) on behalf of Grooms, Frederick W Sent: Monday, January 30, 2017 11:21 AM To: [email protected] (mailto:[email protected]) Subject: Re: Defined Searches ** Defined searches are created on the form itself. In the properties of the view. Fred From: Action Request System discussion list(ARSList) [mailto:[email protected] (mailto:mailto:[email protected])] On Behalf Of Brian Pancia Sent: Monday, January 30, 2017 9:51 AM To: [email protected] (mailto:[email protected]) Subject: Defined Searches ** It has been awhile since I messed with this feature. Trying to setup defined searches on HPD:Help Desk. I setup a search and went into AR System Searches Preferences and set the search type to Admin-Defined. The option to Run Defined searches is greyed out on HPD:Help Desk. What am I missing? Version 9.1. Brian _ARSlist: "Where the Answers Are" and have been for 20 years_ DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ DISCLAIMER: The information contained in this e-mail and its attachments contain confidential information belonging to the sender, which is legally privileged. The information is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are notified that any disclosure, copying, distribution or action in reliance upon the contents of the information transmitted is strictly prohibited. If you have received this information in error, please delete it immediately. _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
