Skip to main content
Solved

Workflow Configuration for mWO

  • January 14, 2025
  • 5 replies
  • 147 views

Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • 3 replies

We are currently in the process to drive different eforms being presented to technicians based on specific criteria.  All of these workfows are “Work Task” configuration type.  This is currently working as intended.  However, we have come up with certain scenarios that require some items be mandatory that cannot be properly made mandatory utilizing current system capabilities.

 

Workflow Configuration: We tried to trigger a survey for a specific work task (with Work Stage ID "H-2"), see the workflow configuration in the attached screenshot. However, we tested this and the outcome is that for all the work tasks created from the work task template, the survey was triggered (instead of only 1 with work stage id "H-2"). 

 

 

 

Best answer by ANQLeon

Hi ​@Alexander Heinze & ​@skullk ,

I’ve created a case for having Work Task Stage as a filter in Work Task Type workflow configurations. This filter is already working for the request task workflow configurations.

This discrepancy exists because R&D introduced Request Work Task Type Configuration from 24R1 onwards, whereas Work Task Types are older configurations, and no changes were made to their workflow configurations at that time.

However, R&D has agreed to implement the necessary changes for Work Task as well.

 

This is to inform you and others that this is now planned to be resolved in the following updates:

25.1E.0 - 25R1 EA
 

View original
Did this topic help you find an answer to your question?

5 replies

Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

In MWO, can you check if the desired workflow configuration is actually applied? There was an issue in a previous release where the combination of multiple filter criteria didn't always work. 


Forum|alt.badge.img+2
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • January 14, 2025

Hi Alexander,

Thanks for the response. In mWO we can see that the desired workflow configuration is applied, however for Work Stage “H-1” the survey gets triggered as well.

 

 


Alexander Heinze
Superhero (Employee)
Forum|alt.badge.img+23

@skullk - this looks like a bug? 


skullk
Hero (Employee)
Forum|alt.badge.img+11
  • Hero (Employee)
  • 256 replies
  • January 15, 2025

@Alexander Heinze yes, looks like a defect in the system.

Please report a support issue to do further investigations. 


Forum|alt.badge.img+2
  • Author
  • Do Gooder (Customer)
  • 3 replies
  • Answer
  • March 19, 2025

Hi ​@Alexander Heinze & ​@skullk ,

I’ve created a case for having Work Task Stage as a filter in Work Task Type workflow configurations. This filter is already working for the request task workflow configurations.

This discrepancy exists because R&D introduced Request Work Task Type Configuration from 24R1 onwards, whereas Work Task Types are older configurations, and no changes were made to their workflow configurations at that time.

However, R&D has agreed to implement the necessary changes for Work Task as well.

 

This is to inform you and others that this is now planned to be resolved in the following updates:

25.1E.0 - 25R1 EA
 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings