Hi Laurent,

I am sorry for the delay in answering your question.

Find below the answers to your questions. The code samples are adjustments to the original taskcompletionsdk.js file.

1. Is it possible to limit the customization to one task step (e.g. based on its name) or it can only be applied to all steps in the workflow?

You can achieve this is two ways:

• You can implement your own logic for applying changes only to a task step (based on transition name or any other information). In the example below we made some adjustments only for the “Translate” transition:

• Depending on your needs, you can use custom servlets, these are configured in workflow on specific steps: docs.rws.com/.../configuring-human-action-servlets-on-------------the-worldserver-11-interface

2. The okButton seems to run the complete step by choosing the first transition. Is there a way of changing this or is this a default?

WorldServer will select the first transition by default. You can override this behavior with custom code that will change the selection based on your needs. In the example below, we are selecting the second transition when available:

3. Is there a way to display all transitions as the standard dialog does or do we need to implement a custom code to reproduce what the application does out of the box?

Sure, you can just comment out this line of code:

I hope the provided information helps you achieve the customization you need.

Best regards,

Anca

Dear Anca Gicoveanu ,

One more question: how should I proceed to apply additional logic to the OK button so that it completes the task (native behaviour) and does another action (e.g. set an attribute)? Do I need to create a new function which will implement again the complete task or can I have a function which is executed at the same time as the complete task?

Thank you in advance for your help.

Regards,

Laurent

Hi Laurent Pierret ,

The implementation depends on what you want to achieve.
I would call any action (like set attributes) before completing the task to ensure there is no paralelization issue or undesired behavior, like complete task execution hapenning before setting up the attributes.

You can do this in several ways:
1. New button that calls set attributes API + Complete API - if you wish to do it yourself, hide OK button.
2. New button that calls  set attributes API + the complete function from OK button, hide OK button (as in the screenshot, for the 'Fly' button).

Thank you,

Anca

Dear Anca,

Thank you for your reply. I have achieved exactly the same with custom button, but I clicked the hidden OK button by getting the button object and clicking it. Your solution is probably cleaner and I will test it.

One last question: I don't see any property for this but is it possible to color a custom button?

Thank you and have a nice week-end.

Laurent

Hi Laurent,

Sure, you can customize the popup as you wish. You can either define a cssClass for the button when you load it and add the desired customizations on that class, or you can identify your button by other properties and apply the desired styles.

Thank you,

Anca

Thanks Anca Gicoveanu , it works!

I have one more question, sorry :-) Would it be possible to open the project attribute dialog from the task view?

Thank you

Laurent

Hi Laurent Pierret ,

You can try to "catch" the project attributes dialog in the same manner as the Complete button event and see if you have everything that is required for the popup to work properly. Otherwise, you will have to implement a custom popup with the desired functionality.


Thank you,
Anca

Hi Laurent Pierret ,

You can try to "catch" the project attributes dialog in the same manner as the Complete button event and see if you have everything that is required for the popup to work properly. Otherwise, you will have to implement a custom popup with the desired functionality.


Thank you,
Anca