We've been using Clarizen for leave requests, and while it was working OK we did encounter many validation rules problems. Many issues came up, and in some cases it took many attempts by Clarizen to fix. So in most cases I do believe you can fix technical issues you have, you just need to consult with their experts and consider developments where needed.
Workflow approvals for Requests
Seeking advice from existing Clarizen Customers. We have just gone live with Clarizen and our implementation consultant helped us to create a workflow for approving Requests. After a Request is approved for a Project, we use the custom action to Convert the Request into a Project.
We are currently facing pushback from our users. No one likes the way that Request approvals work inside of Clarizen. The validation rules written seem to be causing problems. The permissions are not what we designed. Has anyone successfully created a Request approval process that works for your organization and would be willing to share ideas?
Please sign in to leave a comment.
Thanks for you comment, Guy. If you're willing to discuss your particular case with me, please email me directly at email@example.com
Dave, Let me first qualify that I am not a developer, do not know HTML programming and we have been using Clarizen for only a year. We are still learning but I'm happy to share what we have run into around workflow approvals.
Likewise, our implementation consultant assisted us in building a workflow approval process via interact and warned me that it would be a challenge to maintain since it was more advanced than a new users experience. I am using this process with a combination of full and social licensed users. He was right on. I tried to tweak it on my own and hosed our environment for almost two weeks while my executive team debated approval of a few more PS hours and to pay for a sandbox environment. The benefit was that I learned some valuable lessons in the process. Since then, I have been able to replicate the programming to develop another workflow approval path for a second application. Works great. My problem is that this is built by profile and adding a second application forced me to expand the approval panel populated in the task (it is designed at the task level) to include approvers that are different for each application. This became a training issue to teach users how to select the proper approvers for each application. Our process sends an email when an approver is selected to that approver, the approver can hyperlink into the task or approve/decline from the email. I just completed our renewal and added the ESP to our renewal specifically to help me with enhancing this and other processes. The bank I work for produces volume in the 10's of billions but is primarily outsourced so number of employees is small and we do not have a developer on staff. Unless you have a developer that attended the Clarizen Admin school and stayed for the couple days dedicated to developers, I suggest you pay the cost of PS and use Clarizen experts to help you.
Thanks for your reply, Kevin. I'd love to discuss more details with you. If you're up for it, shoot me an email at firstname.lastname@example.org