...
The following screencast also demonstrates order failures when the PDF printer driver is missing.
...
Orders fail to create/succeed due to malformed XML
During the order creation workflow, ClinSpark crafts a message for Rscribe Lite that contains order number and subject information. This information is comprised of data from ClinSpark such as Study Event, Study, Subject ID, etc. All of this is delivered to the ClinSpark Agent structured as JSON. The Agent converts this JSON into object code, and correspondingly generates an XML file that contains the ClinSpark subject information and a unique order number. From there, RScribe Lite uses this as input.
However, if the XML file contains any characters that are not accepted by RSL, the order process fails immediately. Symptoms of this manifest in the user interface where the Invoke workflow will notify the user that an order has been created, but RSL does not start or display waveforms to users.
...
In ClinSpark log files, the following message is displayed:
...
And within RScribe logs:
...
This suggests that the order did not complete successfully due to malformed XML. RScribe logs will reveal the row and column within the XML document where the issue is.
Certain characters that are acceptable in the ClinSpark UI, such as dashes, long dashes, em dashes, en dashses, etc. are NOT acceptable characters for input into the RSL order process. Additionally, other non ascii characters (such as no-break space) can create malformed XML.
The most common modality of these erroneous characters being put into the ClinSpark interfaces are when they are cut and paste from external sources like Microsoft Word documents. Standard keyboard inputs would rarely ever produce a non-acceptable value in the order workflow.