I am using activiti bpm engine to control my workflow. Is it posible to step back if I made mistake in chioce? if no, what should be done? Must I complete the workflow and start a new one?
There is no such thing as 'going back' in workflow, it's well against.. the flow ;) If you wan't to give user the possibility to 'step back' you can model additional flows again to the same task which has been just completed.
Related
I actually moved to Jira and to be honest, it is really helpful and effective tool. I wonder everything has limitations, What are the limitations in jira when an active workflow is being edited?
There has to be some things that the user should be careful about. Any guidance would be highly appreciated :)
Wel, I got this from a link.
If a workflow is active, you cannot edit the workflow name (only the description)
You cannot delete the workflow steps
A step associated status cannot be edited
You cannot add any new outgoing transition if a step has no outgoing transitions (Global transitions are not considered).
A step’s Step ID cannot be changed.
If any one can add anything on this, please go ahead
Currently I am working on a Jira project and in that project I have built a workflow. The workflow runs with a single issue and runs successfully.
This workflow mainly consists of 2 parts. In the 1st part, the authorizations are set and approved. In the 2nd part some assignments are being conducted according to the authorizations that have been set in the first part.
This workflow works well but I have been asked to implement this project with 2 different workflows which will be run by 2 different issues.
So my question is, how can I migrate data from the first issue to the second issue? Somehow I need to transfer the authorization info to the second issue so that the second workflow will be able to run.
Thanks a lot.
Once the authorization is complete you could change the issue type to a type which uses the second workflow. If you want to retain the authorization record, you could clone the first issue and then change the issue type of the clone.
A late respond: I achieved this by using the sub-task mechanism. I also used post-functions in the workflow which made me able to get the authorization data from the first issue.
In TFS 2010, when we reassign a task with a state of "in process" back to someone else, we want the state to change back to "active" with a reason of "reassigned".
I'm pretty familiar with the Process Editor and have been able to muddle my way through customizing workflows and fields, but I'm not a coder by any means so I'm looking for a "dummies guide to automating state changes" approach.
Thoughts?
Thanks!
an alternate approach would be to write a tfsplugin that catches the workItemChanged event, and then alter the state when the reassigning happens.
see: http://nakedalm.com/team-foundation-server-2010-event-handling-with-subscribers/
You can either create a Server side plugin with ISubscribe or you can handle a SOAP event separately with TFS on-premises. If you are using VSO you can use Service Hooks.
I've been looking for a way to have a user acknowledge a
ticket after it has been assigned to them. I don't know if
this is a built in feature or if there is a plugin that
will create a state/button for a user to accept a ticket
after it has been put in there queue. I would expect to
see something like this from the ticket window around
workflow or start progress but no amounts of digging
through configuration settings has turned anything
relevant up.
Does anyone know about this added functionality in JIRA?
Much thanks.
I did this by a custom workflow step. After an issue arrived to an assignee (with status New) he/she should move it to another step (with status Open). Until he/she does it, the issue is considered as not noticed/reached the assignee. Also I have had a report showing issues with New status for more than a predefined period of time.
I'm not aware of a ready-made plugin which performs similar task (perhaps, I should dig into my posts on Atlassian answers to discover some clues for other solutions).
As #Stan says above, a custom workflow is the way to implement this. The workflow functionality in JIRA is very flexible and as a result has a bit of a learning curve, but Atlassian's documentation is pretty good. Post back here if you need help.
I would like to make an emailing in my symfony project.
The user admin log-in in the backend and click on the button "start emailing", then 8000 emails is sending (2 per second). The admin user can close his page and go back a few moment later to see the emailing's progression. (10%...., then 20%... etc).
How can i do ? I think a have to use CRON TASK, but i'm not sure...
Maybe there is a better/other solution ?
Can you explain me the best way to program my emailing ?
Thanks, and sorry for my english!
The best way to rate the sending would be setting your MTA to do that for you. If it's a application requirement then go for Gearman. There is this awesome wrapper for the PHP interface (http://www.symfony-project.org/plugins/sfGearmanPlugin). It works really well.
Cron tasks do not know if the previous running instance has finished the job. It really messes thing easily up. For those cases, like yours, that you need to back processing, the best choice is a solution like Gearman.