Question:  An emPath user recently asked 

• "Is anybody using the applicant tracking module of emPath? We want to know how Volunteer applicants are handled? How do you collect some of the information that Empath does not contain such as Availability, Emergency contact, Education, and Background check?"

Response:  There are several valid responses to this question.  This article focuses on the use of Page Description XML (PDX) to maintain custom data.

The emPath application is delivered with a feature called "Page Description XML (PDX)" which can be used to create custom pages to maintain custom or client specific data.

Following is an example page created using PDX.   This example attempts to address the emPath users detail questions.



A detailed article is available, for registered members, which shows how to create a PDX page.  Also, this information will be explained at the NOW Solutions User Conference.

In summary:

(1) Create a custom table using SQL statements.  Set AP_APPLICANT_ID as the key.  Add custom columns as needed. 

(2) Create a SQL trigger to insert a record into the custom table when an applicant is added to the AP1 table.

(3) Create or modify an XML file called site_ComponentMetadata.  This file will define the custom table such that emPath PDX pages can access and maintain the data.

(4) Create an emPath PDX page using XML statements to define the data to be presented and maintained.

(5) Create or modify an XML file called site_website to let emPath know about the new PDX page.

(6) Create or modify an XML file called site_nav to let emPath know where in the menu the new PDX page should appear.

(7) Update emPath security tables letting emPath know which user classes can used the new PDX page.

(8) Update emPath metadata tables to provide lable descriptions and help text for the new PDX page.  

Please register to view details on how this custom was accomplished.  The registered user article is, Registered users - Using Page Description XML (PDX) to maintain custom data.