Scheduled Tasks are designed to push data back and forth between the feature class layer and the Lucity database. It can push inventory data from the feature class layer to Lucity or push inspection data from Lucity to the feature class layer.
Lucity to GIS- Currently this is only available for inspection feature classes
GIS to Lucity- This is supported for all GIS enabled modules (inventory and inspection).
Scheduled Tasks can be configured to run automatically. The GIS Task Runner will process any Scheduled Task that is due based upon the user defined frequency and other criteria. This functionality greatly expands the Lucity and GIS integration capabilities with use of feature services. Edits to the feature service, regardless of who did it and what environment they did it in, can be picked up by Lucity. Some potential examples:
Collector for ArcGIS (iOS & Android)- including disconnected editing
Merges, Splits, Renumbers, and Deletes must still be done in an ArcMap editing environment with the Lucity extension enabled in order for the related Lucity inspection, construction, and work history to be properly updated.
Features must meet the Lucity module requirements in order for them to be synchronized. For example, required fields such as the Lucity common ID must be populated with a unique value.
Scheduled Tasks interact with the feature class via the feature services. Before setting up a Scheduled Task you should make sure there is a feature service defined at either the feature class or geodatabase level.
Primary Uses
Import Inspection records into Lucity that were created in an inspection feature class layer.
Update Lucity with edits made to feature classes layers in the Lucity web map.
Update Lucity with edits made to Lucity linked feature class layers using editing environments that aren't integrated with Lucity.
Prerequisites
Your feature service must have all the fields that you want linked to Lucity.
Considerations
Which inspections should show up in the feature class?
Click the Add New GIS Task button. A new record appears in the grid.
Select the record in the grid and complete the GIS Task Info section at the bottom.
Under General Info, select the desired Task Type:
Sync - Lucity to GIS - Pushes Inspection data from Lucity to an Inspection feature class layer.
Sync - GIS to Lucity - Pushes any data from the feature class layer to Lucity.
Under Filter Options, select which records to task will process when it runs:
None - Directs the task to consider all records when syncing.
Filter Set - Directs the task to consider only records that meet the criteria of a particular filter.
Select Filter - Choose an existing Lucity filter from the related module.
Under Scheduling Info, indicate how often the task should run.
Units - Indicate the number of minutes, hours, days, or months that will pass between runs.
Frequency - Select whether the units represent minutes, hours, days, or months.
Last Run - Displays the last date that the task was run. (The system automatically completes this field.)
Override - Allows the user to manually modify the Last run date.
Next Run - Displays the next date/time the task will run. (The system automatically calculates this field based on the Last Run, Units, and Frequency.)
Click the Recalc button to calculate the Next Run date using the Units, Frequency and today's date.
Under Options. set how the scheduled task should behave when populating the feature class:
Only process records modified since last run - Directs the Task to check the records' Last Modified dates. Only records (in the filter set) that were modified since the Last Run date are synced.
Last Edited DateTime Field - Directs the Task to store the date/time that the record was last edited (typically the Esri Editor Tracking field). This is only enabled when the Only Process records modified since last run option is checked and the Task Type is Sync- GIS to Lucity.
Insert record if it doesn't already exist - Tells the Task to add any new records to the destination.
Enable number generator for imports - Directs the Task to assign numbers to assets using a Lucity GIS Number Generator related to the feature class.
Update existing record - Tells the Task to update existing records with new attribute data.
Delete previous inspection(s) for asset. (Only keep most recent inspections) - Directs the Task to delete any Inspection in the feature class that is not the most recent Inspection for an asset. The option is helpful if an agency wants the feature class to contain only the most recent Inspection for each feature. (Enabled only when the Task Type is Sync- Lucity to GIS.)
Click on a different part of the tool to save changes.
Note:History section - This section contains information about the last time the GIS Task ran.
How to Add a GIS Task