As part of the initial process of setting up your eaDirect application, you published the original design files that present an application’s statements and generate email notifications.
A version set is a dated set of design files which eaDirect uses to present a user with an online view of a statement. "Publishing" a version set using the eaDirect Publisher tool identifies each design file belonging to a particular view, and moves the files from the design environment to your application server. You give the view a name, and Publisher timestamps the version set for further identification.
Your organization might occasionally find it necessary to modify application design files to apply new business logic, text messages, logos, advertisements, other elements of an online statement, or to accommodate a new data input file format. To implement the new design files in your production environment, you must publish the files, creating new version sets.
It is only necessary to publish design files again for an application if you update the files for any reason. You cannot update or overwrite an existing version set; you must create and publish a new one.
If you create a new version set to accommodate changes in the application data input file, you must also publish a new Indexer DDF.
When you publish a new version set for the view, eaDirect proceeds to use the new version set with Indexer jobs until you publish another one. Publishing a new version set on the same day you run the Indexer job makes it easier to keep track of when design changes take effect.
It is possible to publish multiple version sets on the same day an Indexer job is run, or on subsequent days.
Each time you publish a new version set, eaDirect:
· Creates a timestamp version directory called AppName/ViewType/ViewName/Timestamp
· Adds each file in the version set to the directory
· Creates a reference in the database for the version set
For details on what files you must publish for each type of job, see What Files Do I Need to Publish?.
· See Publishing Your Application's Dynamic Web Views (Version Sets) for instructions.
Caution: Do NOT attempt to edit the XML DDF directly, or the resulting DDF may be unusable. If you receive the error message "Error in reading XML DDF, please see the Error Log File!" when publishing a DDF, the internal validation failed and the DDF may have been altered.