At long last..

So for those of you following my blog or checking to see if I have the app finished yet... I do. I've had it done for a while, but haven't had a chance to publish it just yet. 

It still needs some testing outside of my environment, so I'm gonna leave that to you. If you'd like to test, please leave a comment to let me know. I'm trying to find some online storage space at the moment, but until then I'll email it those who request it.

WoW Code Monkey

A little fun... love this video...

Contact Syncronization

Syncing contacts in any version of Servicedesk has been an inherit problem. A search of contacts in my company's current Servicedesk environment would yield a good number of duplicates, active records for employees no longer with the company, and stale contact information. Reasons such is this is why my company decided to start fresh, moving no data from R6 to R11.

Our solution to syncing contact data? A little console app I wrote that is aptly named 'Servicedesk Contact Sync'. The app features...

• Initial load of contacts from an LDAP source.
  The search to LDAP can be pointed to a specific OU or to the RootDSE. Also supports nested OU's.
• Updates contacts already in Servicedesk.
  The app can be run as a background service that will compare information in Servicedesk to LDAP users and update where needed. This includes users that are disabled in LDAP, it will set the contact to inactive in Servicedesk.
  
• Exclusions list.
  Allows for exclusion of users in LDAP. This is handy if you have service accounts that need to be excluded from addition/sync in servicedesk.
• Supports multiple versions of Servicedesk.
  Supports R6, R11, and soon to support R12.
• Extensive logging

Again, I will be posting the app for beta use and am open to suggestions.

Servicedesk Data Loader

Recently I have been working on some new web applications that will be using the Servicedesk R11 web services to interact with the system. I ran into an issue while creating a Forward Schedule of Change of sorts for our Change/Release Management teams.

The problem?
No ticket data to show on the schedule/calendar. Since this is a new system we are upgrading to, there was no date/time information to use in the calendar.

The solution?
An automated ticket creator! I created a very dynamic app that will create as many Incident, Request, Change, etc.. that you specify. It will allow the input of specific users OR allow you to totally randomize the data.

For lack for a better name, I called it 'Servicedesk Dataloader'. Right now, its only functionality is creating tickets. Anyone have other suggestions?

Screenshots and public beta version to come soon!