Latest Contributions by Ulises

‎07-13-2020

Thanks for the feedback Meggie. Job description in Pro says it has LOI Defined, but no LOI shows.

‎07-13-2020

We used WMX in ArcMap in a daily basis and want to establish a migration path to ArcGIS Pro. As part of our evaluation I set a Workflow Connection in AG Pro without major problems but I'm not able to see current AOIs in the Map. Is there any considerations or configuration changes needed for Pro? I haven't found any related documentation about it. Any help is appreciated.

‎10-04-2019

Thanks Jonathan, so it is expected behavior. Individual layers called from a map service will act as with feature access capabilities. Will work on our service configuration to set desired allowed operations.

‎10-04-2019

When you configured a web map to consume a specific layer in a map service by adding the layer using "Add from web" the layer acts as a feature service instead of a map service when adding the web map to ArcGIS Desktop, not honoring the defined capabilities for the service. By doing this the desktop user can select, query and export data, allowing the user to "hack" the data. If the map service is added to AG Desktop as a whole or if the web map opened in the desktop application was configured in the map as a whole (you could remove layers from after), the capabilities are honored and layers behave as expected of a map service, not allowing the users to do the tasks mentioned above. The obvious workaround is to add the service in the web map and then remove any undesired layers from it (not adding from web), but still a user could consume a layer in its own web map by adding it directly and then "hacking" the data in AG Desktop. The publisher can minimized the risk by changing the layer ID for each layer in the service when publishing it so anyone else that may find or know how to call the service from another web map have a hard time trying to figure out which layer is what and how to add it. But still is a risk especially for services that need to be share publicly but keeping the data as secured as possible. Is this expected behavior or a security glitch?

‎10-04-2019

Thought I share this... To overcome the error message above, it was just a matter of opening the tool selecting the OS option to "Run as Administrator". For some reason it doesn't matter the user is in the administrator group, you have to choose this option to be able to be able to change anything without errors. On the other hand, we found that no matter the log level defined we were not able to see any log files when using ArcGIS Pro. Looks like the log files are created just when using the WMX stand alone application.

‎07-31-2019

I'm trying to modify the log level in the WMX Advanced Settings but I received the following message... "Application attempted to perform as operation not allowed by the security policy..." "Requested registry access is not allowed." User is local administrator and have required permissions in the corresponding directories. Any help is appreciated.

‎06-12-2019

Thanks for the feedback!

‎05-10-2019

WMX provides the following LOI overlapping options as system settings: allow disallow disallow by job type In our shop we do not allow overlapping areas but there are special cases (common enough) that require to work on jobs inside other job areas. The "principal" job is mainly created to identify and define the overall LOI of the "mini-jobs" to be work inside that extent. Due to the nature of those jobs and to be able to work more efficiently they need to allow overlapping AOIs so we like to have the option to allow overlapping areas by job type (mini jobs) but allowing to overlap with other job types (main job) so we can still have the main extent delimited or somehow parent and child jobs be able to share an LOI. Right now we have the main LOI created in job type A and corresponding jobs (job type B) as child jobs but either skipping AOI creation (not desired) or creating AOI as they are available in the main extent (which delay our operations). Is it possible to do this configuration now??? Thanks

‎05-10-2019

Thanks Duncan, I'll check it out and let you know how it goes.

‎05-10-2019

I usually schedule a batch file that run the sql command thru the command prompt. Our data is in an enterprise geodatabase.

‎05-07-2019

WMX provides the following LOI overlapping options as system settings: allow disallow disallow by job type In our shop we do not allow overlapping areas but there are special cases that require to work on jobs inside other job areas. The main job is mainly created to identify and define the overall LOI of the "mini-jobs" to be work inside that extent. Due to the nature of those jobs and to be able to work more efficiently they need to allow overlapping AOIs. So we like to have the option to allow overlapping areas by job type but allowing to overlap with other job types so we can still have the main extent delimited or somehow parent and child jobs be able to share an LOI. Right now we have the main LOI created in job type A and corresponding jobs (job type B) as child jobs but either skipping AOI creation (not desired but the application allows it, which is a big data security flaw) or creating AOI as they are available in the main extent (which delay our operations).

‎05-06-2019

Hi, I'm not a developer but we managed to create a python script produced by Model Builder to automate some daily task. There are some sql statements that need to be run between procedures in the model. Is it possible to call an external sql script from our file to secure the whole process from a single execution? Any help is appreciated...thanks

‎03-13-2019

Thanks Michael, couldn't make it to the Devsummit but hopefully will be able to attend UC 2019. We are just on schedule to upgrade to 10.6.1 in the next few days. We are hoping for this security improvement to WMX in the near future. Cheers, Ulises

‎02-13-2018

In WMX we have several users that are assigned to different groups. One of those groups have a job type filter defined as well as privilege to create jobs. The other group does not have that privilege. What we want is that the user that is in both groups can create jobs for the corresponding job type depending on the filter. As confirmed by ESRI the filter just honor the visibility of the jobs by type but not the privileges by group. This is a big security limitation to our daily operations. Privileges should be honor if a job type filter is defined. User Joe is in Group A and Group B Group A (create job) - Job Type 1 Group B (do not have create job) - Job Type 2 Want Joe to create job in Job Type 1 but not in Job Type 2!!! Workflow Manager‌

‎02-13-2018

Thanks Xiaomeng, that was my question and perception of the issue. I believe this is a big limitation in security settings. Can't think of any workaround for this...

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by Ulises

Re: Workflow Manager AOI not showing in ArcGIS Pro

Workflow Manager AOI not showing in ArcGIS Pro

Re: Security glitch or expected behavior of map services?

Security glitch or expected behavior of map services?

Re: Cannot modify log level in Workflow Manager Advanced Settings

Cannot modify log level in Workflow Manager Advanced Settings

Re: Can I configure overlapping areas by job type in Workflow Manager when not allowed in system configuration?

Can I configure overlapping areas by job type in Workflow Manager when not allowed in system configuration?

Re: Call external script from Model Builder or python

Re: Call external script from Model Builder or python

Allow overlapping areas by job type in Workflow Manager

Call external script from Model Builder or python

Re: Filter privileges in workflow manager by job type

Filter privileges in workflow manager by job type

Re: Filter privileges in workflow manager

Persistent attribute field calculation

Setting different status for closed jobs

Extended properties privileges

Parcel Fabric right of way

ArcMap 10.3.1 crashes trying to add control points...

GIS Manager's Group

Web AppBuilder Custom Widgets

Experience Builder Custom Widgets

User Community for Geospatial Authorities (UCG)

LAUG - Usuarios Latinoamericanos de Esri - Latin American User Group