IDEA
|
@JohnAnderson1, thanks for your suggestion! Is working great in our test environment. We'll be implementing in production soon. Awesome!
... View more
7 hours ago
|
0
|
0
|
8
|
POST
|
We are transitioning to Workflow Manager for Server. Since there is no reports functionality as in classic we are not sure how to access the data to prepared and show information using dashboards, especially in real time. How to include extended properties data and other information from the workflow service so it can be use in dashboards??? Any help is greatly appreciated.
... View more
3 weeks ago
|
0
|
0
|
103
|
POST
|
Hi @RobertKrisher, we have in the Default version... 406,549 records when the tool ran or we open the attributes table. 411,808 records when using querying directly in the database. Don't understand how so many records are still showing in the table since we validated and cleared everything during the weekend and as today just a few dirty areas are displaying when the layer is on. Stats in the tables are updated and indexes are rebuilt recently. As @DiegoLlamasOlivares mentioned performance is very poor for some reason.
... View more
3 weeks ago
|
0
|
0
|
132
|
POST
|
We have an extended properties table to store the geographic area related to a job (ex. regions). Can you configure sending emails based on the value you entered for a job? Users to receive emails are not part of the organization. I don't see if that can be done using an arcade if then expression or by other means. Ex. Job A --> Region 1 --> send email to "emailforregion1" Job B --> Region 3 --> send email to "emailforregion3" Any suggestions are appreciated. Thanks
... View more
3 weeks ago
|
0
|
0
|
118
|
IDEA
|
Hello @JohnAnderson1, sorry for the delay on this reply. I was away for a while. Thanks so much for your suggestion. I will run a few test asap. I
... View more
3 weeks ago
|
0
|
0
|
44
|
IDEA
|
We have a short workflow where all editors have the same privileges for productivity purposes. Once a job is assigned to an editor the workflow will allow to create it's version, do the required edits, post, cleanup the version and close the job. There are no QC steps. Because of that any editor can edit the default version whenever he/she wants using WMX or not since the version must be public. Otherwise post will fail due to privileges missing if Default is protected. I've always saw this as a security concern. Since early days using previous versions of WMX users needed to be configured as SDE in WMX/JTX Administrator to be allowed to post in the workflow but again, once the application opened users were able to change versions to Default and edit. If steps could be configured in the workflow to run as another user this could provide a way to better protect the Default version. A "post" step set to run automatically as the SDE or version administrator will allow the editors to just edit child versions without access to directly update Default.
... View more
02-07-2024
10:49 AM
|
0
|
4
|
172
|
IDEA
|
Correct @JFarmer! That review could happen at several steps once assigned the job.
... View more
02-05-2024
01:33 PM
|
0
|
0
|
106
|
IDEA
|
Hi @JFarmer, thanks for your reply. I'm looking for a combination of both functionalities. I will like to set a manual hold (ex. documentation missing) and based on the hold type (noticed there is a generic type of hold and not able to create several types as in classic) have it configured to release the hold after 30 days. Pending on the hold release then execute cleanup, set "close reason" using extended properties and close the job automatically. User should only be able to set the hold in any corresponding step. If the hold is release before expiration time continue the main workflow (ex. editing). Holds/Releases should send email notifications. Thanks
... View more
02-05-2024
07:58 AM
|
0
|
0
|
116
|
IDEA
|
Holds in WMX should provide functionality to be release depending on time or an action. It will be useful to have a hold on a job and set a timer so when it expires either release the hold and also allows to configure it so the step executes automatically and/or manually or run an action (ex. release the hold after 30 days and continue to next step). Next steps should execute based on "success or failure" so it could allow to configure a workflow with multiple paths (ex close job with "canceled" status or continue running the editing step).
... View more
02-02-2024
03:43 PM
|
0
|
5
|
221
|
POST
|
There should also be a way to dismiss the job as soon as any of the "final status" options are defined. In our workflow an editor can identify that the job should be cancel or return at any time without having to move thru every step (define loi, create a version, edit in pro, etc). We don't want the editors to skip important steps nor prompt the users repeatedly if they can continue or change status. Any suggestions are welcome.
... View more
01-31-2024
12:46 PM
|
0
|
0
|
53
|
IDEA
|
Hi @Bud, Just realized my post was not clear so I apologized for the ambiguity. Attribute rules work fine when defined in my geodatabase but can't be implemented in AGOL or Portal. Thanks for the links; one of them referred to my post. Regards
... View more
01-30-2024
06:22 AM
|
0
|
0
|
172
|
IDEA
|
I noticed (or haven't found how) that field calculation in Enterprise is a one time action that do not persist having to run calculations again as needed. I suggest there is a way to set calculations to be persistent in the table as a way to keep data updated and complete...like using attribute rules in AGOL or Enterprise. Thanks
... View more
01-30-2024
03:53 AM
|
1
|
5
|
266
|
POST
|
Thanks for the feedback @AmirBar-Maor, I contacted our distributor to clarify the issue. We are just a few weeks to migrate to the parcel fabric model and this is a must. We did see that when a parcel is assigned manually to a record it is added to the count no matter an edit operation takes place.
... View more
11-20-2023
08:23 AM
|
0
|
0
|
217
|
POST
|
We noticed that the created parcels count and retired parcels count recorded in a parcel fabric record is not retained in the record because it appears to be dynamic depending on the edits transactions done in the related polygons. We were hoping to use this information for reports and statistics regarding how many parcels were created in a record or during a period of time but these counts varied as subsequent records are created and edits done. A record closed today can show 6 parcels created and 3 retired. A second record with the same parcels assigned can have a count of 5 parcels created and 1 retired. When you query the first record the counts are modified (in our example 3 created parcel and 3 retired). I'm guessing this is because the GUID. Any suggestions on how to retained an static count information in a record is appreciated. Thanks
... View more
11-16-2023
11:15 AM
|
0
|
3
|
274
|
POST
|
Thanks @sirishb, that's basically what we are looking for. Also we noticed that the "percent completed" in the job is not retained neither so we can't use that as an alternative (ex. closed jobs with 50% completion". We implemented the extended properties option as a workaround a few months back but found another limitation for us related to accessing this properties (everyone or no one scenario).
... View more
11-16-2023
10:19 AM
|
0
|
0
|
217
|
Title | Kudos | Posted |
---|---|---|
1 | 01-30-2024 03:53 AM | |
1 | 11-07-2023 10:15 AM | |
1 | 11-07-2023 09:58 AM | |
2 | 02-08-2022 11:36 AM | |
4 | 12-22-2015 08:01 AM |
Online Status |
Online
|
Date Last Visited |
8 hours ago
|