The revised mass e-mail application was successfully implemented last Friday, March 24, as planned. Users have already submitted more than 30 messages for distribution.
The Hub asked Josh Tewell in Enterprise Applications how the revision came about.
The revised mass e-mail application was successfully implemented last Friday, March 24, as planned. Users have already submitted more than 30 messages for distribution.
The Hub asked Josh Tewell in Enterprise Applications how the revision came about.
“We run many applications, but our focus isn’t usually application development,” Tewell said of himself and his colleagues in the messaging group. They inherited the application in the reorganization. Many of the programmers previously responsible for the interface moved to Technology Assessment and Planning. At the same time, responsibility for approving employee messages was transferred to ITS Communications. The two groups used the learning curve to reflect on how the system worked and whether it could be updated.
“I liked a lot of the Web interface, so I kept its look,” Tewell recalls. “But the system was using WebFocus to build its address list, and it wasn’t scaling well. Combined with our knowledge that the S3 cluster was going away and that there were some other changes we wanted to make on the back end, it seemed best to just start over with the coding.”
Tewell had experience with PHP from working with the UNC listserver and had taken a class in programming with Perl. “That’s what I like about this job,” he said. “We have lots of interesting projects that let me learn things I have a lot of interest in, but don’t always find much time outside of work to play with.” He also appreciates being able to draw on other employees’ experience. “Stephen Braswell was my Perl consultant,” Tewell said. “Whenever I got stuck, he helped me out.” The revision effort began in earnest about a year ago, but was interwoven with other projects. The big push came with the beginning of 2006.
The Web interface of the new version is constructed using PHP with the Smarty Template Engine, HTML and some Javascript, while the back end is written in Perl. Data for the application is stored in ITS Oracle databases. “We’re using a Perl bulk mailer module to manage sending the messages,” Tewell observed. “It gives us lots of control–we can fine tune the sending process to work with our mail complex, so we can get these messages out efficiently. One nice part about this is being able to easily assign custom headers to each message. It gives us better reporting of actual recipients, not just sending attempts.”
Kathy Bryant, director of communications for UNC–Chapel Hill’s Office of Human Resources, is very pleased with the revisions. “The feature that lets the sender know that the message has gone out successfully is excellent!” she said.