You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've some user feedback for the CreateJob widget.
We're using the widget with Web AppBuilder Developer Edition (2.8)/ArcGIS Enterprise 10.5.1 and have made no changes to the code except for projection changes recommended here: #5.
While using the Select Features option in the CreateJob widget, the behaviour of the selection on the map could be more intuitive for users.
(All replicable in Chrome, Firefox and IE 11)
Example 1:
a. Launch CreateJob widget
b. Select a job type
c. Choose Select Features
d. Select an annotation shape from the menu
e. Draw a shape on the map (drawing where a Selected map/feature service feature does not exist)
f. Click Submit and the widget returns with an error message ‘No features were returned from selection’
g. The shape on the map remains
Because the shape remains on the map and uses a passive colour, it suggests that there's nothing wrong with the selection and the user expects to be able to proceed to create a job.
Example 2:
a. Launch CreateJob widget
b. Choose Select Features
c. Select an annotation shape from the menu
d. Select an existing feature on the map (based upon the feature service specified in the widget configuration)
e. Nothing appears on the map to suggest anything has been selected.
f. The user could proceed in 3 ways:
1. Click Submit and a job would be created with an AOI
2. The user could select another feature on a map, click Submit and potentially a job with a multipart AOI is created
3. The user didn't actually select a legitimate feature on the map, clicks Submit and a job is created with no AOI.
When a legitimate feature is selected on the map, the annotation shape appears and disappears quickly leaving no indication of what has been selected, or if anything has been selected at all.
Users expected that the shape selected would be highlighted to them.
Example 3:
a. Launch CreateJob widget
b. Select a job type
c. Choose Select Features
d. Select an annotation shape from the menu
e. Draw a shape on the map (drawing where a Selected map/feature service feature does not exist)
f. Click Submit and the widget returns with an error message ‘No features were returned from selection’
g. Select an existing feature on the map (based upon the feature service specified in the widget configuration)
h. The error message ‘No features were returned from selection’ remains visible in the widget even though the user can click Submit.
Having the error message continue to be visible when not relevant is confusing for users.
Example 4.
In the CreateJob widget configuration, we have disabled attachments, removed Add Attachment and Max Attachment Filesize (MB).
We also have 3 job types defined for High, Medium and Low.
When a job is first selected from the CreateJob menu, it appears as expected:
Click Back and select the same or a different job, and attachments option appears:
An attachment can be submitted with the job requested even though it's been disabled.
Attachments also appear if:
The widget is opened, closed, reopened and a job is selected
The widget is opened, a job is submitted and a new one is started
Example 5:
This example could be a user/configuration error!
A job can be created if no AOI is created/selected on the map.
a. Launch CreateJob widget
b. Select a job type
c. Click Submit
In our WFM workflow, a job cannot be progress unless an AOI is defined. Is it possible for the widget to have this incorporated, or include a warning if an AOI does not exist?
If you require any further information on the above (screen recordings, screenshots etc.) just let me know!
Carmel
The text was updated successfully, but these errors were encountered:
Hi there,
We've some user feedback for the CreateJob widget.
We're using the widget with Web AppBuilder Developer Edition (2.8)/ArcGIS Enterprise 10.5.1 and have made no changes to the code except for projection changes recommended here: #5.
While using the Select Features option in the CreateJob widget, the behaviour of the selection on the map could be more intuitive for users.
(All replicable in Chrome, Firefox and IE 11)
Example 1:
a. Launch CreateJob widget
b. Select a job type
c. Choose Select Features
d. Select an annotation shape from the menu
e. Draw a shape on the map (drawing where a Selected map/feature service feature does not exist)
f. Click Submit and the widget returns with an error message ‘No features were returned from selection’
g. The shape on the map remains
Because the shape remains on the map and uses a passive colour, it suggests that there's nothing wrong with the selection and the user expects to be able to proceed to create a job.
Example 2:
a. Launch CreateJob widget
b. Choose Select Features
c. Select an annotation shape from the menu
d. Select an existing feature on the map (based upon the feature service specified in the widget configuration)
e. Nothing appears on the map to suggest anything has been selected.
f. The user could proceed in 3 ways:
1. Click Submit and a job would be created with an AOI
2. The user could select another feature on a map, click Submit and potentially a job with a multipart AOI is created
3. The user didn't actually select a legitimate feature on the map, clicks Submit and a job is created with no AOI.
When a legitimate feature is selected on the map, the annotation shape appears and disappears quickly leaving no indication of what has been selected, or if anything has been selected at all.
Users expected that the shape selected would be highlighted to them.
Example 3:
a. Launch CreateJob widget
b. Select a job type
c. Choose Select Features
d. Select an annotation shape from the menu
e. Draw a shape on the map (drawing where a Selected map/feature service feature does not exist)
f. Click Submit and the widget returns with an error message ‘No features were returned from selection’
g. Select an existing feature on the map (based upon the feature service specified in the widget configuration)
h. The error message ‘No features were returned from selection’ remains visible in the widget even though the user can click Submit.
Having the error message continue to be visible when not relevant is confusing for users.
Example 4.
In the CreateJob widget configuration, we have disabled attachments, removed Add Attachment and Max Attachment Filesize (MB).
We also have 3 job types defined for High, Medium and Low.
When a job is first selected from the CreateJob menu, it appears as expected:
Click Back and select the same or a different job, and attachments option appears:
An attachment can be submitted with the job requested even though it's been disabled.
Attachments also appear if:
Example 5:
This example could be a user/configuration error!
A job can be created if no AOI is created/selected on the map.
a. Launch CreateJob widget
b. Select a job type
c. Click Submit
In our WFM workflow, a job cannot be progress unless an AOI is defined. Is it possible for the widget to have this incorporated, or include a warning if an AOI does not exist?
If you require any further information on the above (screen recordings, screenshots etc.) just let me know!
Carmel
The text was updated successfully, but these errors were encountered: