|
1. Creates a file containing deliverable application data of "Application" by exporting from "Database account" to the \appdata folder of the current release folder. The resulting file is called "application.xml".
2. If a value for the optional "Custom XSL" parameter is passed, applies the XSL transformation identified as the value of "Custom XSL" to the result of Step 1.
3. Creates, in the same \appdata folder written to in Step 1, a diff file that compares the export file created in Step 1 with the export file of the same name found in the \appdata folder of the previous release frame. The output file name is "application.diff.xml". For more details on this file, see the "Diff file format" section below.
To read the data, this action automatically opens the application from Repository, except when Application = USERVICE (the Service Definer application delivered by USoft), in which case the application is automatically opened from Flat Files.
Parameters
Name
|
Type
|
Optional?
|
Application
|
Application
|
No
|
Database account
|
Database account
|
No
|
Custom XSL
|
Custom XSL
|
Yes
|
 | Initial comparison (Step 3) |
If the current release has Initial = Yes, an initialization file is created in addition. The name of this file is "application.initial.xml". The initialization file contains only the following nodes of the XML export file created in step 1:
•the <MultiExport> document node. •its immediate child elements. These are elements based on Object Name Plural values. They have a documentName attribute. If the current release has Initial = Yes, the diff file created in Step 3 is a comparison with the initialization file rather than with previously released appdata, since no such appdata was previously released.
|
USoft has a standard XML format for expressing changes between data sets. In this format, <Insert/> tags express that a record has been added, <Update/> tags express changes in existing records, and <Delete/> tags express that records have been removed. For details, look for "USoft XML format" in the USoft Definer Help.
For technical reasons, there are differences between this standard format and the format of the diff file produced by Step 3. In the diff file:
•<Insert/> tags have been dropped. This prevents unique-key conflicts during import of supertype and subtype records if you decide to re-import the diff file. •The usoft-xml processing instruction has "verify-original-values" = "no-check-on-pk", rather than "no". This prevents problems with child Deletes already executed as a result of cascading delete rules if you decide to re-import the diff file. |
When you call this action, if the current release has "Include attachments" = Yes, attachments for the "appdata" section (if any are defined) are copied to the specified subfolder of the "appdata" section folder. This happens only to attachments that have Blocked = No (the default). If a Custom XSL transformation is defined for the attachment, this transformation is applied to the output.
If the current release frame has Include Packing Slip = Yes:
•Last Used for the current release frame is set to the current date and time, •a packing slip is compiled and registered for the current release frame, •a copy of this packing slip (XML file) is placed in the release directory. |
To export deliverable appdata to a destination folder of your choice, instead of to the release folder, you can call "Export deliverable appdata".
To export all appdata for "Application" and "Database account" to a folder of your choice, you can call "Export all appdata".
|
|
