• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vish

  • Rank
    Level 5 Contributor
  • Birthday

Contact Methods

  • ICQ

Profile Information

  • Gender
  • Location

Recent Profile Visitors

349 profile views
  1. Hi cdtj, This requirement changed internally and now this functionality was enforced for specific SD analysts only. I wasn't sure of updating your conditional macro, so I managed to accomplish using spel code which is working at the moment. Thank you!!
  2. Hi cdtj, I have managed using below spel and looks working at the moment. I will try your code using conditional macro and let you know how it goes. Thank You!! cr::z_solution_log( ... ) { if (soln_log.length == 0) { string z_soln_msg; z_soln_msg = format(" Please browse for knowledge and accept knowledge doc as Solution before setting the Status to close"); set_error(1); set_return_data(z_soln_msg); return; } }
  3. It looks feasible using spel by checking the length of solution log attribute and if it equals 0 then restrict the ticket status to closed.
  4. I'm looking for a feasible solution to require Knowledge doc on closure of an incident in Service Desk. Any suggestions from experts?
  5. The problem is with my current customized list form. After applying this code on a clean list form, it worked like a charm. Thank You so much for your help.
  6. Hi cdtj, I'm not sure if your update to previous code was saved, as I'm still running into same problem after reapplying the code from above post.
  7. hi cdtj, I have tried your code and looks like there is a missing syntax in the URL construction, as seen from below screenshot. I have tried appending the missing syntax manually to test the code further but running into other problems, see below screenshot for reference.
  8. Is there a way that when we click on a ticket it just goes straight into “Edit” mode? Is this possible to customize in Service Desk 14.1 cp3??
  9. Would it be possible to enforce KB search through Analyst front end before submitting a request ticket in SDM? If someone had a success in accomplishing such requirement and willing to share this customization solution, would be greatly helpful for us. Thank You!!
  10. Please see detail alg form attached for your review. Thank You! detail_alg.htmpl
  11. Hi cdtj, It's overridden after form submit and not on category change. At the moment, we would like to have category field for all ticket types and it's great to know about splitting up based on ticket types. I appreciate for sharing the code.
  12. Hi cdtj, I didn't changed any on the User description attributes on detail_alg.htmpl form. As the category field needs to be displayed on LOG SOLUTION form, so I added the following condition. I was wondering if this logic is correct? <PDM_IF "$args.alg.type" == "SOLN"> <PDM_MACRO name=dtlStartRow> <PDM_MACRO name=dtlReadonly hdr="Current Request Area" attr=category> <PDM_MACRO name=dtlHier hdr="New Request Area" attr=category autofill=no evt="onChange=\\\"change_category_func('cr',null,'pcat_cr')\\\" factory=pcat_cr> </PDM_IF> And another line for read only category field on view Log Solution form. <PDM_IF "$args.alg.type" == "SOLN"> <PDM_MACRO name=dtlStartRow> <PDM_MACRO name=dtlReadonly hdr="Current Request Area" attr=category>
  13. Hi, Have a requirement for adding category field on the solution log activity (detail_alg.htmpl) form. When selecting or changing a category on the solution log form, the text in the user description field is overwritten with a constant text "Log solution text". I was wondering of what other code changes that I need to do in order to retain the analyst description in the user description field on this customized form?
  14. Yes, hopefully there is some workaround for exporting the activity logs as well.