On 28-Dec-2012, at 10:38 PM, Gowrav <go...@gmail.com> wrote:
SO here is my test case:
On Any sales finalisation 1) HR assigns project to available 'Project Team Leader', Project created, editable by superuser, HR and Project Team Leader 2) Project team leader designs the tasks and assigns them to employee, employee should only edit its status 3) On each task completed should go to project team leader for verification. 4) If verified our companies senior (Superuser/HR head/Project Manager) verifies the task for Quality 5) Lastly the work is sent to client and superuser/project manager enters the response from client as approved or rejected. 6) If task is approved by client it is considered to be final, otherwise it again goes to open state. 7) Not all the tasks requires this verification process.
Now that's the case.. what kind of new permissions I have to make, or roles and how to manage this work flow.
Actually our company wants to implement new system from next year start, and only a few points are remaining in that. like the above mentioned and a better support/communication system ...
On Friday, 28 December 2012 21:44:51 UTC+5:30, rushabh wrote:
Workflow can be used to assign states to any transaction and will help in situations where you want a transaction pass through multiple users.
If there are use-cases where you want workflow to behave in a certain manner - please share!
On 28-Dec-2012, at 10:38 PM, Gowrav <go...@gmail.com> wrote:
SO here is my test case:
On Any sales finalisation 1) HR assigns project to available 'Project Team Leader', Project created, editable by superuser, HR and Project Team Leader
2) Project team leader designs the tasks and assigns them to employee, employee should only edit its status 3) On each task completed should go to project team leader for verification. 4) If verified our companies senior (Superuser/HR head/Project Manager) verifies the task for Quality
5) Lastly the work is sent to client and superuser/project manager enters the response from client as approved or rejected. 6) If task is approved by client it is considered to be final, otherwise it again goes to open state.
7) Not all the tasks requires this verification process.
Now that's the case.. what kind of new permissions I have to make, or roles and how to manage this work flow.
Actually our company wants to implement new system from next year start, and only a few points are remaining in that.
like the above mentioned and a better support/communication system ...
On Friday, 28 December 2012 21:44:51 UTC+5:30, rushabh wrote:
Workflow can be used to assign states to any transaction and will help in situations where you want a transaction pass through multiple users.
If there are use-cases where you want workflow to behave in a certain manner - please share!
On 28-Dec-2012, at 10:38 PM, Gowrav <go...@gmail.com> wrote:
SO here is my test case:
On Any sales finalisation 1) HR assigns project to available 'Project Team Leader', Project created, editable by superuser, HR and Project Team Leader
2) Project team leader designs the tasks and assigns them to employee, employee should only edit its status 3) On each task completed should go to project team leader for verification. 4) If verified our companies senior (Superuser/HR head/Project Manager) verifies the task for Quality
5) Lastly the work is sent to client and superuser/project manager enters the response from client as approved or rejected. 6) If task is approved by client it is considered to be final, otherwise it again goes to open state.
7) Not all the tasks requires this verification process.
Now that's the case.. what kind of new permissions I have to make, or roles and how to manage this work flow.
Actually our company wants to implement new system from next year start, and only a few points are remaining in that.
like the above mentioned and a better support/communication system ...
On Friday, 28 December 2012 21:44:51 UTC+5:30, rushabh wrote:
Workflow can be used to assign states to any transaction and will help in situations where you want a transaction pass through multiple users.
If there are use-cases where you want workflow to behave in a certain manner - please share!
If i manually enters ‘Running’ (my status defined) in workflow_status in projects then I am able to see the button … but its all disabled … no matter whct permission my current user have (I have logged in with administrator with all permissions)…
On Monday, 31 December 2012 22:10:38 UTC+5:30, Gowrav wrote:
Is this setup okey … see attached two files
On Friday, 28 December 2012 16:18:59 UTC+5:30, rushabh wrote:
Dear all,
Just released a new system to set multi-level permissions before Submission.
I am trying to build the workflow as demonstrated in the video for leave management.
But couldn't see the Approve/Reject selection top once I save the leave neither it is being assigned to HR User after saving but to Leave Approver.
Can you point out if I have missed anything while configuring the workflow.
None of us were around when you were configuring the workflow so I have no idea how you have configured it.
A screenshot of your Workflow doctype will help us in understanding.
As a general comment to everyone: We should be able to replicate your issue, so please give us as much information as you can. Please see it from the point of view of the person receiving the communication.
Thanks and Regards,
On Friday, December 28, 2012 4:18:59 PM UTC+5:30, rushabh wrote:
Dear all,
Just released a new system to set multi-level permissions before Submission.