There is an issue with this code while using the current versions of Chrome (Version 92.0.4515.131 (Official Build) (64-bit)) and Firefox (Version 90.0.2 (64-bit)). In the "Create New Job" dialogue, if you use mouse clicks to choose the "User", "Groups", "Unassigned" radio buttons, the "Assignment" dropdown does not populate correctly. If you use arrow keys to cycle through the radio buttons, the dropdown populates correctly. Here is a warning logged in the console of the browser that may have something to do with the issue: "MouseEvent.mozPressure is deprecated. Use PointerEvent.pressure instead."

I'm attempting to setup our Workflow Manager JavaScript site with AD logins. We're currently using SSO for Portal and AGS with no issues. I was able to login with authentication set to 'none'.

I've modified the following lines of code as directed and have also tried the text call-outs to see the variable, but it's not working. It reads back <%= User.Identity.Name %> and not the Windows User.

        var user = "<%= User.Identity.Name.Replace("MyDomain\","") %>";  // user without domain authentication
        //var user = "<%= User.Identity.Name.Replace("\","*") %>";     // user with domain authentication
        Controller.startup( {user: user} );

Has anyone else had this issue? Thank you.

Unable to open job from aoi popup

Please consider adding functionality for people to use non-Web Mercator basemaps and services in the application. Currently, this is not possible. We have tried making changes to the AppConfig.js, EsriMap.js, and BasemapGallery.js files, as well as ensuring that all basemaps and map services are in the same non-Web Mercator spatial reference.

We failed to get success trying to login on Workflow manager viewer with credential from domain user, Enclosed you find the details and the appconfig , index files as well.

thx in advance

Issue with Workflow manager Web Viewer.docx
AppConfig.txt

index.txt

We tried to deploy this at a client site and could not get it to work. It failed during the login. Eventually we realized that it worked with Chrome, IE10 and IE 11, but not with the client's IE9 computers.

The ArcGIS JavaScript API (3.16) supports back to IE 7. There is some code in the index.html to error for IE8.

The requirement is fine since these are old browsers, but would be nice to see it in the doc.

In file Constants.js

StepExecutionType : {
EXECUTABLE : "executable",
FUNCTION : "function",
PROCEDURAL : "procedural",
URL : "url",
QUESTION : "question",
FILE : "file"
},

I think it should be URL:"launch-url" instead, othewise nothing is done when calling a launch url step.

I tried a newer version of the code in case it was version specific but for some reason the date values reported in my query results are way off. Not just the wrong format but the wrong month and year.
e.g. StartDate is reported as "3/8/19, 4:00pm" while in the details (even in Web app) of the job it is actually "8/15/2018" . I tried setting a date format in IIS just in case it was a weird translation of date formats on the server side but no success.
Jeremy

The 'demo' username does not work anymore.

somehow, it stuck at the loading page. I relinked the wfm service and AOI. I replaced “ myserver" with my host name. I am not sure what I have done wrong here. please help.
btw, It was working fine in the previous version.

There is a section in the AppConfig.js that lets you set your own Custom locator but there is no clear documentation on how to set the locatorSources array.

I thought all I would have to do is put in the URL to the locator as type string and it would set up the source for me but that does not seem to be the case. I would get errors saying that addressToLocations() is not a function.

So after doing a little bit of digging, looking at the JS API documentation, it seems that when creating a new source you need to give it an object and then specify the new locator as a new Locator type. In order to get this to work, I needed to add in the Locator class in the define method and then call it LocatorSources like so....

locatorSources: [{
                    locator: new Locator("https://sampleserver6.arcgisonline.com/arcgis/rest/services/Locators/SanDiego/GeocodeServer"),
                    singleLineFieldName: "SingleLine",
                    outFields: ["*"],
                    name: "i18n.widgets.Search.main.esriLocatorName",
                    placeholder: "i18n.widgets.Search.main.placeholder"

                }]

Only then did it work for me. I think it would be helpful if the documentation was updated to reflect this. Or if this is not supposed to work, then it may be a bug with using custom locators.

Are there any plans to release a 10.6.x compatible version?

I'm using JavaScript API 3.19, Workflow manager 10.5.1, SDE database 10.5.1, ArcGIS Server 10.3.1. Not sure if this error is due to Server 10.3.1 needing upgraded or something else?

Could anyone please provide suggestions?

Thanks!

Please add functionality to add feature layers to show features on top of the basemap.

Here is an example of what i did.

In AppConfig.js i added...

                {
                    url: "https://myserver/server/rest/services/layers/MapServer",
                    options: {
                        id: "mapLayer1",
                        imageParameters: {
                             layerIds: [1, 2, 3],
                             layerOption: "show"
                        },
                        opacity: 0.8,
                        showAttribution: false
                    }
                }
            ]

Then in EsriMap.js i added this...

           if (this.mapConfig.customLayers) {
                var customLayers = this.mapConfig.customLayers;
                for (var i = 0; i < customLayers.length; i++) {
                    var customLayer = customLayers[i];
                    var layer;
                    if (customLayer.options && customLayer.options.imageParameters) {
                        var params = new esri.layers.ImageParameters();
                        var keys = Object.keys(customLayer.options.imageParameters);
                        arrayUtil.forEach(keys, function (key) {
                            params[key] = customLayer.options.imageParameters[key];
                        });
                        customLayer.options.imageParameters = params;
                    }
                    layer = new esri.layers.ArcGISDynamicMapServiceLayer(customLayer.url, customLayer.options);
                    if (layer) {
                        this.map.addLayer(layer);
                    }
                }
            }