Completely hide “disabled” Services

Posted on April 25, 2012

In OTRS 3.1 and newer, evidently Services that are disabled via ACLs are now only greyed out.  For our users, it’s less confusing to make them disappear completely.  In order to accomplish this, I had to actually go into a couple of files and add some code.  See the description below.
Files Modified:
/opt/otrs/Kernel/Modules/AgentTicketEmail.pm
/opt/otrs/Kernel/Modules/AgentTicketPhone.pm

Modifications:
You need to add an else statement (the push part exists without the else part)down around:
AgentTicketEmail.pm – line 1950-1955.
AgentTicketPhone.pm – line 1875-1885.

[CODE:]
# check if service is disabled
if ( !$Service{$ServiceKey} ) {
$ServiceRegister{Disabled} = 1;
}
##### Else Brackets Added by Jeff #####
 else{
push @ServiceList, \%ServiceRegister;
}
# set service as printed
$AddedServices{$ServiceKey} = 1;

[/CODE:]

Jeff

Show/Hide Dynamic Fields based on Queue

Posted on April 25, 2012

With OTRS 3.1 and higher, you can create dynamic fields (formerly freetext fields) to allow collection of additional information beyond the defaults.  Normally, these fields show up in every ticket that they’ve been setup to show in.  I wanted to be able to hide the fields and then only show them when a particular Service or Services were chosen.  I’ve listed what I did below.
Files Modified:

/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketEmail.dtl
/opt/otrs/Kernel/Output/HTML/Standard/AgentTicketPhone.dtl

Modifications made:

In AgentTicketPhone.dtl and AgentTicketEmail.dtl, I added some code in the section where it checks if the Service is changed:

[CODE:]
<script type=”text/javascript”>//<![CDATA[
$('#ServiceID').bind('change', function (Event) {
Core.AJAX.FormUpdate($('#NewPhoneTicket'), 'AJAXUpdate', 'ServiceID', ['TypeID', 'Dest', 'NewUserID', 'NewResponsibleID', 'NextStateID', 'PriorityID', 'SLAID', 'SignKeyID', 'CryptKeyID', $Data{"DynamicFieldNamesStrg"}, 'To', 'Cc', 'Bcc']);
});
############  Added by Jeff ##############
#Core.Agent.InitFocus();
switch ($(‘#ServiceID’).val() ) {
case  “2″:
document.getElementById(‘id name’).style.display = ‘block’;
break;
case  “3″:
document.getElementById(‘id name’).style.display = ‘block’;
break;
default:
document.getElementById(‘id name’).style.display = ‘none’;
}

#########  End – Added by Jeff ###########
});
//]]></script>
[/CODE:]

 

Then I added the “id name” to the Dynamic Field that I wanted to Show/Hide:

[CODE:]
<!– dtl:block:DynamicField_MyFieldName –>
<div id=”id name” style=”display:none;”Name”}”>
$Data{“Label”}
<div id=“id name”>
$Data{“Field”}
</div>
<div id=”id name” style=”display:none;”></div>
</div>
<!– dtl:block:DynamicField_MyFieldName –>
[/CODE:]

Now, by default, the dynamic field is hidden. When you choose a Service with the ServiceID or 2 or 3, it automagically appears!

Jeff

Adding Templates to OTRS

Posted on February 6, 2012

We’re currently investigating using OTRS, with the ITSM modules, as a possible ticketing system.  In version 3.0, they’ve got the ability to add ticket templates.  Templates are nice in that they allow you to create semi-complete tickets just by choosing a template.  That is one of the features that FrontRange’s ITSM product have in Version 7 that we were really looking forward to having.  Currently, in FRS’s ITSM (version 6) we’re using QuickActions to do basically the same thing.

There is a great Youtube video that describes what to do to get templates working in the default form.   The problem is that the example template code that OTRS has in the AgentTicketPhone.dtl file discussed uses a button to choose the template text.  That’s all well and fine for some browsers, but doesn’t work in all of them, due to using the onclick function.  Seems that Safari and some other browsers just ignore that. Plus, in my opinion, it would be pretty ugly, and reminiscent of a 1990′s webpage, to have a dozen different buttons to click on.  Maybe if they were each a different color and blinked…

Anyway, after some Trial and Error, I was able to get a cleaner method working – in IE, Firefox, Safari, and other browsers.  I replaced the button(s) with a dropdown menu.  This is simply a select tag, with an option representing each template form.  It then uses the onchange function, rather than the onclick function, fire off the appropriate form.  This means that all of the major browsers seem to be all right with it.  I tested it in IE, Firefox, Opera, Safari, and Chrome and they all worked as expected.

What I’ve done is create a custom theme, then copied and altered the AgentTicketPhone.dtl file to add my changes.  This means that during upgrades, my changes won’t be overwritten, since they’re not made in the default file.

Anyway, the way the example is written in the file is:

As you can see, it uses the onclick function and each template would require its own button.

What I’ve done, is add a dropdown via the select tag and its options and used the onchange function:

Things to note are:

1> Make sure to add the id=”some_name” to your select tag, or the GetElementByID() won’t work, since there won’t be an ID to get.

2> The option values are actually the names of each form that I’ve added at the bottom of the page.  That means that there’s a form at the bottom with id=”PassReset” and one with id=”VirusMalware”.   These forms contain the fields and values that you want to use to automagically populate the ticket.  Changing the fields and values is covered in the video.

 

Installing/Configuring the OTRS Ticketing System

Posted on January 24, 2012

I’ve been tasked with installing/configuring the open-source version of the OTRS ticketing system, with the ITSM modules, for evaluation here at work.  So far, I’m really happy with it.  I have the basics setup and ready to go and I must say that it seems easier to configure than FrontRange’s ITSM.  Another nice thing – IT’S FREE!  From my experimentation, it appears that since it’s completely web-based, it works on virtually any device with a browser and network access.  On top of that, there’s an iPhone app available too.  FRS’s ITSM product is .Net-based.   That means that it doesn’t really work with non-Windows devices.  ITSM Version 6 had a fairly robust web client available that could be used by the Mac people.  ITSM Version 7, on the other hand, drops that web client.  That means that Mac users are basically SOL, unless they use the free iPhone app.  “Ah”, you say,  “that’s simple enough.  Just download it and go!”.  Well, if only it was that easy.  To use the mobile client, you have to purchase the Mobile server module(s) – and the licenses to go with it.

OTRS Pros so far:
IT’S FREE!
Initial install was straightforward.
A lot of configuration options.
Very flexible, due to the above.
Good support in the forums.
Totally web-based, so it works with virtually any browser.
Has an iPhone app available.

OTRS Cons so far:
A lot of configuration options = A LOT of configuration options.
Looks slightly “clunky” compared to FRS’s ITSM.  A certain amount of that can probably be corrected fairly easily – somewhere within the configuration options.
No tech support number to call – without paying for support.
No true Workflow engine to assist with ticket routing, etc.

We’ll see what else comes up as I move forward.

 

Installing/Configuring Evision’s Argos Report Server

Posted on January 24, 2012

Installed Evision’s Argos Report Server.  It was a pretty easy, lightweight install.  I put it on a virtual server and encountered no problems with the install.  The initial setup went smoothly, outside of problems getting an Oracle connection successfully setup.  Most of that was probably due to my inexperience in dealing with Oracle products.  Once I figured out how to get the ODBC driver successfully installed, along with a working tnsnames.ora file, it was pretty easy.

The person that is actually creating reports, etc. says that he’s really impressed with it so far.  Only time will tell how it works out.

New Project – UPDATE

Posted on January 24, 2012

MS System Center is dead.  The cost savings just didn’t warrant all of the work necessary to switch.  Basically, we wouldn’t save any real money, but would have to do a whole lot of work.

On to the next project.

New Project

Posted on October 26, 2011

I’m on a team that’s starting to assess whether to move away from our current products to the Microsoft System Center suite of products.  I’m in the process of gathering numbers for what we currently spend.  Then, we move on to see what the equivalent would cost with System Center.  It should be an interesting investigation.

ITSM 6.3.2 and IMAP/SSL

Posted on October 20, 2011

Found out that the email listener in FrontRange ITSM 6.3.2 doesn’t work with IMAP over SSL.  There is evidently something buggy about FSMTService.exe.  I was able to get a hotfix from FRS that was basically just a fixed version of FSMTservice, and it solved the problem.  What I was getting originally were errors like:

“Error occured while connecting to the email server. Reason: NO Logon failure: account currently disabled. ”

and

“Error occured while connecting to the email server. Reason: NO The parameter is incorrect.”

and

“Error occured while connecting to the email server. Reason: NO The referenced account is currently locked out and may not be logged on to.”

After it would throw some errors, FSMT would crash.  You could restart FSMT and it would work for a minute, throw errors, then crash again.  The fact that there were multiple different errors made it harder to track down.  Eventually the Support Tech was able to find a Knowledge Base (KB) article in their system that described a different error with IMAP/SSL, but we decided to give it a try and see if it solved my issue.  Lo and behold, it did!

Evidently, the issue is fixed in ITSM 3.6.4, but the hotfix will fix older versions.

Original 6.3.2 version of FSMT: 6.0.1001.811

Fixed version of FSMT: 6.3.1001.913

ITSM and Checking IMAP over SSL

Posted on October 12, 2011

Adding PHP to IIS 7.5

Posted on October 4, 2011

Got php up and running successfully on IIS 7.5 (Windows Server 2008R2) today.  Will post the step-by-step instructions shortly.  I’m hoping that this will allow me add the ability to create web forms that can submit tickets directly ITSM.  We’ll see how it pans out.

© Copyright Jeff's Musings • Powered by Wordpress • Using Detour theme created by Brian Gardner.