Latest Contributions by JohnFannon

A customer of ours is using an ArcGIS Server (11.5) print service with custom templates with their ArcGIS Online apps. They are having an issue where graphics (created by the Draw widget) within Experience Builder do not print when using a custom layout within the Print Widget connected to this ArcGIS Server Print Service. The graphics do print when using the Esri default print service (with standard templates) and also when selecting the MAP_ONLY option with the ArcGIS Server print service.    I've taken a look this morning and can reproduce the issue and have confirmed that:   The web_map_as_json parameter sent to the print service from the Print Widget contains the drawn graphics (as a featureCollection) and is identical whether using the ArcGIS Server print service or the Esri default. This means it is probably not an issue with the Print Widget or Experience Builder, as it's sending the right info in the request to the print service.  When I use the ArcGIS Server print service and set the layout at MAP_ONLY, the graphics appear on the print. This suggests the print service is capable of printing the graphics.  When I use a custom template with the ArcGIS Server print service, the graphics don't appear. This suggests the issue could be something to do with the template.  It's not to do with the Pro version that the layout was saved with. I tried saving a copy of one of the templates used in the service, opening in the latest version of Pro and then saving over the top of the existing layout (pagx) file. This makes no difference as it still doesn't print the graphics.  Printing from Map Viewer (with graphics) also has the same issue. The graphics are printed with the MAP_ONLY option, but not with a custom template.    I have also: Published a completely new test print service with the latest version of Pro and the newly saved template above, but this also makes no difference.  Checked settings of the template in Pro and can see no settings relating to display of graphics.  Is anyone else able to print graphics from the Experience Builder print widget when using a custom template via an ArcGIS Server print service? We are using ArcGIS Pro 3.6.2 and ArcGIS Server 11.5 (with all patches installed) all on a windows server.  ... View more

We are are looking at implementing a reporting service in ArcGIS Server (11.5) that can be used through the Experience Builder Print Widget.  We've configured this as a report, as per the customer's requirements, with 4 sections in Pro as follows: 1) A details section to include a few basic attributes (approx 6) of a selected site polygon. 2) A details section to include summary attributes (approx 7) from each selected tree survey (point) feature in a tabular format.  3) A details section to include detailed attributes (approx 10) from each selected tree survey (point) feature in a paged format (i.e. 1 feature per page) 4) A details section to include attachments from each selected tree survey (point) feature in a paged format (1 feature per page.  This report has been published as a print/report service using pro that also includes a basic A4 landscape map template. We've then configured the print widget in Experience Builder to use this service and set it to use the selected features for the relevant layer in each section of the report.  This is all working as expected (except when there are no features selected - but that is a different issue!) and producing a report. However, it is taking approximately 60 seconds to print the full report, including the map. This seems pretty poor performance considering that in our tests we have been using 1 selected site polygon and 3 selected tree survey features.  Doing a few more detailed tests by removing the map and sections in turn, we have found that: The map is taking approx 22 seconds. The attachments section is taking approx 5 seconds. The detailed (paged) tree survey attributes section is taking 14 seconds.  The summary (tabular) tree survey attributes section is taking approx 6 seconds The single details section for the site polygon is taking approx 14 seconds.  Again, the above is for 1 site polygon (with approx 6 attributes) and 3 tree survey features (with approx 7 attributes), so the data quantity feeding into the report is minimal. The data for the report is also sent in the print request (in the web_map_as_json parameter) so the reporting service is not having to query any data, just present it by injecting it into the report template. So why is it taking so long to generate a pretty basic report? ... View more

An important customer of ours has recently been experiencing 504 gateway timeout errors when using a secure print service that we host for them in ArcGIS Server (v11.5). We have raised a support case and have already posted in the community on this here: https://community.esri.com/t5/arcgis-online-questions/504-gateway-timeout-when-printing-through-utility/m-p/1658735 To summarise, the solution was previously working (for approx 2 years) and involves: - A standard print service published in ArcGIS Server (v11.5) - this is secured with standard ArcGIS authentication. This service is set as Synchronous as this is required for printing in Web App Builder. - So that users do not have to enter credentials each time they use the service in apps, the the service has been added as an item in their ArcGIS Online organisation with the credentials stored. This item is shared with the organisation. This is a standard approach for accessing secured services.  - The URL for the above item (starting https://utility.arcgis.com/usrsvcs/servers...) is then used when configuring the Print Widget in Experience Builder and Web App Builder (the customer still has some older apps they are yet to migrate).  - When end users print from within apps in ArcGIS Online, the request goes via the utility.arcgis.com proxy, which handles the credentials and forwards the request on to the ArcGIS Server.  For the last few months users have been getting errors when printing larger/more complex prints and this is due to 504 gateway timeout errors that also state "Error from CloudFront". We have tested extensively and found that any print that takes more than 30 seconds to complete results in a gateway timeout. The prints are still successfully generated on the ArcGIS Server and there are no errors or timeouts in server. My conclusions from investigations is that there is a timeout setting somewhere in CloudFront, which I assume is used as part of the utility.arcgis.com proxy, that is set to 30 seconds. This is incompatible with Synchronous tasks (geoprocessing / print etc) that may take longer than 30 seconds.  The timeout should be increased to something more reasonable and perhaps to match the default usage timeout (maximum time a client can use a service) in ArcGIS Server.  I strongly feel this is not an "enhancement" but a requirement and should be fixed as soon as possible. ... View more