nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Usage of resets element

santoshrt

Hi,

I have follwing sequence in workflow
1)Task A (User task)
2)Task B (External task for Email Notification)

After completing task B I need to revert back to Task A i.e activate user task A again.
I used the resets element in Task B as follows
< resets >
<reset v="Task A"/>
</resets>
I also set the successor of task B to Task A and predecessor of task A to task B.But the email task does not complete i.e workflow gets stuck at the email task.
The email script does not have any errors as notifications were being generated earlier,when the successor of Task B was another task say Task C.

How can I use reset element to re-activate the Task A which has become inactive,after Task B(which is an external task for email notification)

Any clue/suggestions would be very helpful
Thanks,
Santosh.

Find more posts tagged with

Comments

kaalraa

There are some misconceptions about reset element. It is mainly being used while dealing with parellel tasks, so no need to use the reset element.

However as per your requirement, you have done the right thing mentioning the successor and predecsssor. Also you have to mention within the activation element of task A as task B and the another task as well which could make task A as active.

[HTML]

[/HTML]

Still... if you have any issues.... please attach you workflow as a separate text file.

Hi,

I have follwing sequence in workflow
1)Task A (User task)
2)Task B (External task for Email Notification)

After completing task B I need to revert back to Task A i.e activate user task A again.
I used the resets element in Task B as follows
< resets >

I also set the successor of task B to Task A and predecessor of task A to task B.But the email task does not complete i.e workflow gets stuck at the email task.
The email script does not have any errors as notifications were being generated earlier,when the successor of Task B was another task say Task C.

How can I use reset element to re-activate the Task A which has become inactive,after Task B(which is an external task for email notification)

Any clue/suggestions would be very helpful
Thanks,
Santosh.

Adam Stoller

... But the email task does not complete i.e workflow gets stuck at the email task.

This is usually an indication that the script used to send email encountered an error that it was not coded to deal with and thus never performed the callback to the workflow engine.

You need to do more debugging on your end to resolve this, or post everything here (wft code, script code, etc.) and hope someone here feels like spending their time to help you debug your code for free.

santoshrt

Thanks for your suggestions,there was a problem in paramters passed to the email script.Now transitition does happen back to Task A successfully.

I had not mentioned that Task A has a timeout element,which inactivates task A after specified time limit.Is there any way(like any attribute) by which timeout happens only for the first time.If the task is activated for the second time then timeout will not apply.
Is this achievable in workflow tasks.

Thanks for your help in advance,
Santosh.

kaalraa

Is there any way(like any attribute) by which timeout happens only for the first time.If the task is activated for the second time then timeout will not apply.

Santosh,

Workflow is a series of tasks, it is not an interpreted code which would do the job as per programming. However if you have a requirement it would be taken care with the help of an user task having options with user as "Inactivate Now" or "Skip Task".

Adam Stoller

Thanks for your suggestions,there was a problem in paramters passed to the email script.Now transitition does happen back to Task A successfully.

I had not mentioned that Task A has a timeout element,which inactivates task A after specified time limit.Is there any way(like any attribute) by which timeout happens only for the first time.If the task is activated for the second time then timeout will not apply.
Is this achievable in workflow tasks.

Thanks for your help in advance,
Santosh.

If a task is designed with a timeout element - it is possible, from another task or even completely outside of the particular instantiated job itself, to adjust the value of the timeout associated with that task (read the perldoc for TeamSite::WFtask for more details) - however, I believe it is usually implemented in such a way that it is the task transitioned to upon the timeout that checks status of some sort and either transitions back to the timedout task or forward to some other task.

You can do a lot of different things here - it depends on your skills as a programmer and your ability to design / figure out what you actually want to do within the confines of what is actually possible with the workflow engine.

santoshrt

Hi,

I have been able to figure out the solution to the problem.
I wrote an external perl script that dynamically sets the timeout value of the required task.
However I do not know what should be specified in in timeout tag i.e v ="" so that timeout becomes infinity for the user task,which can again be set dynamically based on the flow of workflow process.

Thanks in advance.
Santosh.

kaalraa

Hi,

I have been able to figure out the solution to the problem.
I wrote an external perl script that dynamically sets the timeout value of the required task.
However I do not know what should be specified in in timeout tag i.e v ="" so that timeout becomes infinity for the user task,which can again be set dynamically based on the flow of workflow process.

Thanks in advance.
Santosh.

There is nothing as infinity in the timeout value. Either it would a number of hours and minutes OR would be a definite datetime. My suggestion to you is to put approx time in hours which a user at a max can use to complete one process cycle of your application.

Also keep in mind the timeout value can only be set dynamically when the task is in INACTIVE state.

santoshrt

Thanks for your inputs,I used a parallel dummy task with required timeout value.On timeout an external task is used to notify and transition is made back to the User task.(with no timeout value).
This solution meets my requirement that timeout should happen only once.