Bug 5903: Slot Value rwSettings with DateTime values not completely functional when read from model file
Bug Number: 5903
Release notes (y/n): Yes
For Release Nums: 7.0.3 or 7.0.4

Gnats 5903:  Set Table Slot Value Script Action clears Value if Allow Editing 
  is set and does not use the Value (for dates) set for the Action.

At the time of the introduction of the "Set Slot Value" Script Actions, the 
slot value setting supported basic DateTime values and "partial" DateTimes 
(i.e. periodic, not fully qualified, e.g. "January 15").  Subsequent to that, 
in May 2016 for USACE-ABQ Task 5.7, slot value settings were enhanced to 
support also RPL Symbolic DateTimes.  

See notes: 
http://cadswes2.colorado.edu/~philw/2016/Scripts/FeatureNotes-May2016.html 
and GIT commit "e32eabdf8bc82dda1630fbe6e54054e2dc73253d" (5-23-2016).

With this enhancement, it was no longer possible to _always_ internally 
represent all DateTime Slot Values as numeric values.  A new QString field 
was introduced.  The intention was that this would be used only when it was 
not possible to represent the Date_Time value as a numeric value:

   // Special Symbolic Datetime String field, for DATETIME values.
   // This is empty if not last edited as a Symbolic Datetime Formula.
   QString _symbDateTimeStr;

This state was correctly reflected after editing a Slot Value rwSetting for 
a DateTime-units slot.  However, when reloading such an rwSetting from a model 
file (from an XML encoding) that policy wasn't correctly implemented.  That 
is, DateTime values which _could be_ represented with a numeric value where 
not being converted to its numeric value (e.g. "January 15" ... representable 
as a numeric Partial DateTime).  Such a DateTime slot value rwSetting did 
appear correct when viewed in the rwSettingTree (i.e. in an rwSetting-based 
configuration dialog), but didn't function correctly in certain uses of the 
actual DateTime value.

See the fix in method: okstat rwSlotValSetting::setFromXML (QDomElement, 
 bool debugCase).

---