That's interesting, I have never seen anyone use XSL files in UCCX scripting. Could you explain how it works?
I'd wager most people just use the Keyword Transform Document step, which uses a very simple find/replace model to change documents. However, this requires you to either split up the states into separate files, or to juggle all of the data each time you read/write to the file (probably something the XSL handles well, but I don't know anyone who has got that to work).
E.g.,
Template File
<?xml version="1.0" encoding="utf-8"?>
<SevereWeather>
<FlagState_AL>%FlagState_AL%</FlagState_AL>
<FlagState_GA>%FlagState_GA%</FlagState_GA>
</SevereWeather>
Pseudo Script
Set xml = doc[weather.xml]
Set template = doc[weather-template.xml]
Create XML Document (xml)
/* Read status of all states */
al_status = Get XML Document Data (xml, "//FlagState_AL")
ga_status =Get XML Document Data (xml, "//FlagState_GA")
/* Inform caller of current status for chosen state */
/* Get new status from caller for chosen state */
Set al_status = "emergency"
/* Update all statuses using keyword transform */
xml = Keyword Transform Document (template)
/* Change file in repo */
Upload Document (xml to l[], "weather.xml")
You might find it easier to avoid XML all together, and just have different files for the different locations, and have the contents be plain text.
E.g.,
File
state-of-al.txt
Content
normal
Pseudo Script
/* Use a menu to get state choice */
Set target = "al"
/* Construct the filename for target state */
Set filename = "state-of-" + target + ".txt"
/* Get current status of target state, and inform caller */
Set current_status = doc[filename]
/* Use a menu to get new state choice */
Set new_status = "emergency"
/* Change the document in the repo */
Upload Document (text[new_status] to l[], filename)
