See also:

How the Helpfile came to be

Evolving the ESG's people and processes

All articles

By Erin Bardua

Perhaps you've been hearing about XML for a while. Perhaps developers or other I.T. staff have just started making noises about it. What do you need to know, and how does it relate to FundSERV?

"XML is a means of structuring data and communicating with a trading partner," sums up Dominic Ionadi, FundSERV senior business systems analyst. FundSERV began using XML for its non-financial update system years ago, eventually converting major order-entry files in 2004 with ESG v15.

Why build applications that read XML? "XML enables greater flexibility and automation," says Ionadi. Compared to the "flat file" standard, used for order entry files prior to v15 and still used in some parts of the FundSERV system today, XML lets you send only the information that's important to the receiver in the context of the business process you're transacting. Older flat files were rigid, meaning you always send the same amount and type of information. Even if you have to add customized information to the XML files for today's increasingly complex transactions, you can still omit other unnecessary information.

Ionadi points out other benefits of XML: "From a technology perspective, it's much easier to build applications that read XML than proprietary standards. XML is pervasive and used by virtually everyone in every industry, so it's easy to find people and tools to support it. XML is a widely accepted means of communicating."

Machines that think like people: Reading XML in the Helpfile

When FundSERV's XML layouts are translated into the Helpfile for users, they are structured in a similar way to the actual code your systems read. It's a visual representation of the XML Schema. Related information is grouped together logically and includes all validation rules and edits, allowing an analyst to take a big picture approach. For instance, look at the Client Info section:

This particular section appears in eight different messages. Using the define once principle, it can be transplanted in whole or in part as a recognizable unit wherever Client Info is needed. Looking more closely, you'll see that within this large section are smaller sections that can be treated the same way, such as the Organization section. This leads to a more understandable file structure.

This structure also has a cost-savings benefit, says Ionadi. "One of the big drivers from the technology side is that XML enables a lot of re-use of components, making it easier to leverage existing resources to build new processes and substantially reduce maintenance effort."

Table of Contents