JULIE Integration for Tasks

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

This feature may not be available in every package. Not sure if you have this feature or you want to learn more about it? Send us a message at support@cartegraph.com.

The JULIE integration interacts with the Tasks recordset.

There are no upgrade instructions necessary for this integration to persist through Cartegraph Software upgrades. JULIE must be set to export the file to a set location accessible to Cartegraph on a regular schedule.

Feature Description

JULIE (Joint Utility Locating Information for Excavators) Inc. is a call before you dig service in Illinois. This integration creates Tasks from JULIE Ticket Data. This process is kicked off by turning on the JULIE Integration automation. Once the automation is complete it pauses for a defined interval as set in the Continuous Trigger block to Delay after processing in seconds, before starting again. During the run of the integration, new JULIE Ticket files are requested from a Google Gmail account. The integration then creates tasks in Cartegraph from the JULIE Data. The original JULIE ticket file, downloaded from the Gmail account, is attached to the Task record. The JULIE tickets are formatted as XML text files. Any files with errors are skipped. The error files are moved to the Other folder within the Gmail account for manually processing. Errors can be reported via email using the standard ‘If an automation fails send a notification’ automation template within Cartegraph. All files not designated as JULIE tickets are skipped but will not produce an error. This integration only adds Task records. Records are never updated. Duplicate records cause an error.

Integrating JULIE ticket data directly into Cartegraph, streamlines workflows, saves time and resources, shorts the time between the request and starting on the task, prevent mistakes made from manually entering the data, and is easier to assign work, including in real-time in the field. Also collect and report on data related to the tasks to track things like average time to complete, costs, and time spent with the Analytics Dashboard and reports.

Field Map

Task Field	JULIE field(s) (XML tag(s))	Comments
Task ID	<delivery>\<ticket> +"-"+ <delivery>\<revision> +"-"+ tickets>\<work_date> (Year)	Year from the <work_date>
Asset Type		Value: Non-Asset
JULIE Ticket Type	<tickets>\<type> +" " + <tickets>\<reason_2ndr> + " " + <tickets>\<priority> + " " + <tickets>\<category> + " " + <tickets>\<meet> + " " + <tickets>\<resend>	See the Ticket Type Mapping Appendix section for more details.
Priority	<tickets>\<priority>	If priority is EMER or SHRT or RUSH the priority is set to Important. In all other cases the default Cartegraph value is used.
Estimated Start Date	<tickets>\<work_date>
Estimated Stop Date	<tickets>\<work_date>
Shape X	<tickets>\<centroid>\<coordinate>\<longitude>
Shape Y	<tickets>\<centroid>\<coordinate>\<latitude>
Activity		Value: Utility Locates
Department		Value: JULIE
Address Number	<tickets>\<st_from_address>
Street	<tickets>\<street>
County	<tickets>\<county>
Intersecting Street	<tickets>\<cross1>
Location Description	"Address: " <tickets>\<st_from_address> + " " <tickets>\<street>" Cross: " <tickets>\<cross1> "Place: "<tickets>\<place> + " County: " <tickets>\<county> "Subdivision: "<tickets>\<subdivision "Grid List: " [<tickets>\<gridlist>\<grid> + " " + <tickets>\<gridlist>\<grid> ....]	There is a list of grids under the grid list tag. Each grid is listed in the Location Description.
JULIE Work Description	"Premarked: "<tickets>\<premarked> " "Directional Boring: "<tickets>\<boring>" "Depth > 7ft: "<tickets>\<depth_7ft> "Location: "<tickets>\<location> "Work Type: "<tickets>\<work_type> "Extent: "<tickets>\<extent> "Remarks: " <tickets>\<remarks>
JULIE Map URL	< tickets>\<map_url>	The value in this field is decoded from the XML escaped value to the non-escaped original value.
JULIE Ticket		Value: True
JULIE Ticket Number	<delivery>\<ticket>
JULIE Received Date	<delivery>\<transmitted>	This value contains both date and time information.
JULIE Phone	<tickets>\<phone>
JULIE Phone Ext	<tickets>\<phone_ext>
JULIE Caller	<tickets>\<caller>
JULIE Caller Type	<tickets>\<caller_type>
JULIE Caller Phone	<tickets>\<caller_phone>
JULIE Caller Phone Ext	<tickets>\<caller_phone_ext>
JULIE Contact	<tickets>\<contact >
JULIE Contact Phone	<tickets>\<contact_phone>
JULIE Contact Phone Ext	<tickets>\<contact_phone_ext>
JULIE Contact Email	<tickets>\<email>
JULIE Place	<tickets>\<place>
JULIE Subdivision	<tickets>\<subdivision>
JULIE Grid List	<tickets>\<gridlist>\<grid>	There is a list of grids under the grid list tag. Each grid is listed out separated by a semicolon.
JULIE Premarked	<tickets>\<premarked>
JULIE Directional Boring	<tickets>\<boring>
JULIE Depth Greater 7ft	<tickets>\<depth_7ft>
JULIE Location	<tickets>\<location>
JULIE Work Type	<tickets>\<work_type>
JULIE Extent	<tickets>\<extent>
JULIE Remarks	<tickets>\<remarks>
JULIE Work Date	<tickets>\<work_date>
JULIE Fax	<tickets>\<fax>

Integration Data Structure

This matrix shows most of the data structure of the integration.

Table Name	Column Name
wdTaskMainGeneral	ID
wdTaskMainGeneral	cgAssetType
wdTaskMainGeneral	JULIETicketType
wdTaskMainGeneral	Priority
wdTaskMainGeneral	StartDateEstimated
wdTaskMainGeneral	cgShape
wdTaskMainGeneral	Activity
wdTaskMainGeneral	Department
wdTaskMainGeneral	AddressNumber
wdTaskMainGeneral	Street
wdTaskMainGeneral	County
wdTaskMainGeneral	IntersectingStreet
wdTaskMainGeneral	LocationDescription
wdTaskMainGeneral	JULIEWorkDescription
wdTaskMainGeneral	JULIEMapURL
wdTaskMainGeneral	JULIETicket
wdTaskMainGeneral	JULIETicketNumber
wdTaskMainGeneral	JULIEReceivedDate
wdTaskMainGeneral	JULIEPhone
wdTaskMainGeneral	JULIEPhoneExt
wdTaskMainGeneral	JULIECaller
wdTaskMainGeneral	JULIECallerType
wdTaskMainGeneral	JULIECallerPhone
wdTaskMainGeneral	JULIECallerPhoneExt
wdTaskMainGeneral	JULIEContact
wdTaskMainGeneral	JULIEContactPhone
wdTaskMainGeneral	JULIEContactPhoneExt
wdTaskMainGeneral	JULIEContactEmail
wdTaskMainGeneral	JULIEPlace
wdTaskMainGeneral	JULIESubdivision
wdTaskMainGeneral	JULIEGridList
wdTaskMainGeneral	JULIEPremarked
wdTaskMainGeneral	JULIEDirectionalBoring
wdTaskMainGeneral	JULIEDepthGreater7ft
wdTaskMainGeneral	JULIELocation
wdTaskMainGeneral	JULIEWorkType
wdTaskMainGeneral	JULIEExtent
wdTaskMainGeneral	JULIERemarks
wdTaskMainGeneral	JULIEWorkDate
wdTaskMainGeneral	JULIEFax
wdTaskAttachments	Attachment
NotificationMessages	Message
NotificationMessages	Source

Value Translation for Ticket Type

The JULIE Ticket Type field is a concatenation of several values from the Ticket data. The Values in XML tags need to be translated to use in the JULIE Ticket Type field.

Tag: <tickets>\<type>

Tag Value	Translated Value
NEW	NEW
2NDR	2NDR
UPDT	EXTEND
RXMT	RETRAN
CNCL	CANCEL
Any Other Value	(The value of the XML tag)

Tag: <tickets>\<reason_2ndr>

Tag Value	Translated Value
NOSHOW	NOSHOW
INCOMPLETE	INCOMPLETE
REMARK	REMARK
Any Other Value	(The value of the XML tag)

Tag: <tickets>\<priority>

Tag Value	Translated Value
NORM	NORMAL NOTICE
EMER	EMERGENCY NOW
RUSH	EMERGENCY RUSH
SHRT	EMERGENCY SHORT
Any Other Value	(The value of the XML tag)

Tag: <tickets>\<category>

Tag Value	Translated Value
LREQ	(blank)
DAMG	DAMAGE
EXPS	EXPOSED
DSGN	DESIGN
Any Other Value	(The value of the XML tag)

Tag: <tickets>\<meet>

Tag Value	Translated Value
Y	MEET
N	(blank)
Any Other Value	(blank)

Tag: <tickets>\<resend>

Tag Value	Translated Value
Y	RSEND
N	(blank)
Any Other Value	(blank)

Library Data Lists

Fields used in the integration that are lookups are validated before the Task is saved. If the value from the integration is not available in the field’s target library an empty value or the Cartegraph field’s default value is used.

Cartegraph Field Name	Cartegraph Lookup Target
Asset Type	Asset Types\Asset Type
Priority	Priorities\Priority
Activity	Activities\Activity
Department	Departments\Department
Street	Streets\Street
County	Counties\County
Intersecting Street	Streets\Street