nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Crowdsource Reporter - Add OBJECTID to Submission Message

MichaelKelly

In the submission message of the Crowdsource Reporter template, it would be great if you could reference the OBJECTID so that users would have a unique reference ID for their submission. That way they have a reference to their submission if they need it at a later stage.

An example use case would be where a local authority wants to give an option for users to submit their contact details. They can't store this in the feature service as it will be public so they want to be able to provide an email address to send on their details if they choose to do so.

Furthermore, if you could reference this in an email hyperlink it would be ideal. Something like this:

<a href="mailto:myemail@email.com?Subject=Crowsource%20Application%20Submission%20${OBJECTID}" target="_top">myemail@email.com</a>

Find more posts tagged with

Status: Open

Comments

MichaelKelly

Thanks very much for your reply Allison, much appreciated. Your comments and suggestions make a lot of sense

AllisonMuise1

Hi Michael Kelly‌,

There are several suggestions above, so I'll try to address each of them separately:

1) Present OBJECTID in the thank-you message: We aren't doing this deliberately because the OBJECTID is fairly useless for identifying a report has been submitted to an app with more than one layer, which most Reporter implementations have, or when that report has been integrated with other systems. If someone calls in to check on issue '2' for example, is that issue 2 from the potholes queue or the animal control queue, adn how does that relate to my workorder system?

I would suggest assigning workorder IDs to each of the reports as they come in (working on a script to automate this right now) and sending a follow-up email to the reporter with that information. This would also provide a way to communicate more information such as anticipated next steps and contact info for further inquiries - info that won't fit in that little 'thank-you' box.

2) Protecting personal information: Personal information collected through reporter can be hidden by using the popup configuration to specify which attributes are present in the form, and which attributes are present when reviewing a submitted report. The editable fields do not need to be visible, and the visible fields do not need to be editable.

3) An option to open Reporter to a specific report: This is definitely on our radar, but it is a challenge to come up with logic that will match what most people will expect. For example, when your location is shared with the app, the app only loads nearby reports. What if the linked report is not nearby? We have a similar item in our backlog for Manager, too.