Latest Contributions by ChelseaDuncan1

This answered my question fully. Thank you. ... View more

Hi Tope, I didn't see the screenshot you provided. I believe you're referring to the "Require procedural steps to be marked as started" option in the Workflow tab of the Workflow Manager System Settings. I disabled this option and now have full functionality with the toolbar button to mark steps complete. This setting affected each kind of step in our workflows, procedural, executable, launch URL and question steps. Why does a requirement for procedural steps affect other step types in the workflows? Thank you for providing this solution for us! Chelsea ... View more

Hi Tope, We had actually investigated using question steps in the WMX Web Application as a workaround for displaying pop up notifications as part of a step. We have found that we have lost considerable functionality between the desktop and web WMX applications, in this case because pop up messages are not supported. We had hoped that by creating question steps and using tokens to enhance them, we could provide the user informative messages. The example provided above was more for clarification of my meaning. A true example of how we would want to use this would be to have a question step following the step creating a data reviewer session. The data reviewer session would be created and named according to job information (using tokens). In the question step we would have liked to provide the user a pop up with the data reviewer session id that was just created for the job. This way, the user would know their session id and could use that information to more easily enter a filter on their data reviewer table inside of the Road Characteristics Editor. This example would use the [REVSESSION:ID] token Without this, the current process is to have to search through a long list of session unique values (not sortable) from within RCE and seek out the session name (based on the job id and job name). The more critical requirement my organization has is to support pop up messages from within the WMX Web Application. That said, we have managed to design around these limitations thus far. Thank you for your response. Chelsea ... View more

Hi Tope, This issue occurs for all step types in the workflow. The following two example show simple workflow samples. These steps are all out of the box JTX Custom Steps, procedural and open url. The current step is set to Create Job Version. The create version step is an out of the box custom step in the JTXSteps category. In this workflow, it is configured to "can be skipped". I am able to right click on this step and "Check Step (Mark as Done)" without issue and the workflow proceeds to the second step. In the following workflow, the same issue is experienced with a open url step and a procedural step: For the Launch DCG RCE step (Launch URL step type), the step cannot be skipped. When this step is right clicked and "Check Step (Mark as Done)" WMX presents the "Step cannot be skipped and has not been executed." message as expected. The toolbar button is unavailable. For the Test Case Edits step (Procedural step type), the step can be skipped. When this step is right clicked and "Check Step (Mark as Done)" without issue and the workflow proceeds to the next step. Oftentimes, my organization assigns steps to groups or leaves them unassigned as so many users in different groups will be executing them. I reconfigured one of the steps above to be assigned to my user (currently logged in) to see if that would make the toolbar button usable. This configuration did not change the availability of the toolbar button and I was still able to successfully perform the right click "Check Step (Mark as Done)" operation. Thank you for looking into this. Chelsea ... View more

I am experiencing the same issue where the launch gp tool launches with the invalid input workspace. Did you ever find a resolution for this issue apart from manually navigating to the location? ... View more