The following actions should trigger a review by Park Management:
a new feature is created with PUBLICDISPLAY = "Yes"
an existing feature has PUBLICDISPLAY changed
an existing feature has a change to its public properties (MAPLABEL, SHAPE, POITYPE, ??) when PUBLICDISPLAY = "Yes"
These changes should not be posted to default until/unless approved by the park, because once posted to default, the changes will appear on the public park maps. It would be nice if there were an automated query to identify all of the "review required" changes in a version before posting it to default.
However, this turns out to be too complicated to implement in the time I have. It will require reading the add/delete tables to see if the feature is new since the parent (or default?) version (I do not know how to do that).
However, there is a workaround. The data manager should be reviewing the changes in the version (using ArcMap or Pro). The changes can be reviewed against the criteria above and summarized for park review.
The following actions should trigger a review by Park Management:
These changes should not be posted to default until/unless approved by the park, because once posted to default, the changes will appear on the public park maps. It would be nice if there were an automated query to identify all of the "review required" changes in a version before posting it to default.
However, this turns out to be too complicated to implement in the time I have. It will require reading the add/delete tables to see if the feature is new since the parent (or default?) version (I do not know how to do that).
However, there is a workaround. The data manager should be reviewing the changes in the version (using ArcMap or Pro). The changes can be reviewed against the criteria above and summarized for park review.