Open GoogleCodeExporter opened 9 years ago
Actually, what we need to do is allow global and incident admins to create
their own HTML versions of the work order form, and just create code snippets
that the system will replace. E.g. Some of the codes may be:
* [[CLICKMAP]]: Add a checkbox which says, "Click this box to add a map," and which will then add a map to the printer friendly version.
* [[WORKDESCRIPTION]]: A combined sentence description of the work that needs to be accomplished, broken out by phase. This is similar to the sentences in the InfoBox.
* [[SPECIALINSTRUCTIONS]] Field instructions set by each organization in their Settings panel, e.g. "When finished, report the case #, volunteers, hours worked, and initials of resident present during work."
* [[LOGOURL]]: An optional customizable logo for the organization.
* [[WORKORDERNUMBER]]: Work Order Number (Incident-specific, Alpha+Number)
* [[DBWORKORDERNUMBER]]: Work Order Number in the database (Global, large number)
* [[ENTEREDBYORG]]: Organization responsible for the assessment
* [[ENTEREDBYPERSON]]: Name of individual responsible for the assessment
* [[CLAIMEDBYORG]]: Organization currently claiming the work order, for the current phase.
* [[DATETODAY]]: Date the Work Order was printed (Today)
* [[DATEREQUESTED]]: Date on which the Work Order was entered into the system
* [[DATA-*]]: For each field in the database (such as a name, address, phone number, etc, the field may be included with DATA-UPPERCASEFIELDNAME.
* [[CURRENTSTATUS]]: Status of current phase.
* [[LOGGEDINORG]]: Name of the organization that printed the work order
* [[LOGGEDINPERSON]]: Name of person logged in at the time the work order form was created.
These fields may be embedded into HTML, and are replaced by the system each
time a printer friendly version of the work order form is created.
Original comment by v...@aarontitus.net
on 22 Jan 2013 at 5:32
Original issue reported on code.google.com by
v...@aarontitus.net
on 14 Jan 2013 at 11:31