- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 09:00 AM
Hello
We have a customized table that is used to track leases for our clients. Recently a request has come to me to automate the termination of leases. According to the proposed process, they want approvals to terminate sent out to the appropriate managers, and approval would kick off the process.
The problem is that the Lease table we are using is not extended from Task, and that I am aware that approvals are used on the Task table. My immediate thought was to create a new table that would work in sync with the Lease table, but be extended from Task so that we can leverage the Approval Engine. That got shot down by our project manager, as per our company policy, any modifications or extensions to the Task table must be handled by the CAB and that could take upwards of 3-4 months as there is a backlog of requests for modifications or extensions to the Task Table.
It has been suggested that we create our own approval engine specifically for Lease so that we can get around the CAB restriction and it was also suggested that it would take a couple of weeks to create a standalone approval engine. I however do not want to do such a thing as this poses a maintenance nightmare and duplication of methodology. However, CAB is refusing to fast track this approval for us to extend Task.
Is there any other way to hook approvals to a table not extended from Task?
thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 11:28 AM
The workflow approval activity will work on non-task tables. But its important to note that only user approvals will work, group approvals require a table that extends task.
You are correct that "Approval For" references task, but you will also find a Document ID type field called Approving that will show up when the approval is for a non-task.
Edit: Here is an approval for a Knowledge article that I found in my demo instance. The kb_knowledge table does NOT extend task.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 11:48 AM
Useful information, Michael. I assume that if an approval is built in this fashion, if one approves, then it can proceed with the workflow, correct?
If the other approvals need to be cancelled afterwards, I am ok with doing so via code. Just as long as we don't have to create new forms and stuff.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 11:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2017 12:02 PM
Awesome!!! Thanks. Will look into this.
Thanks for your help!!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2018 04:02 PM
I have successfully put group approvals on a non-task table. I am on Jakarta so I don't know if this is new in there or not. I do know that the approval_coordinator is not available on non-task tables. But I did get around that by doing a branch to all the different approvals from the different groups (because some required all some required one) and then was able to do a join upon them all being done. Hope this helps someone.