- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
we're planning to user Document management for managing and approving Documentation for individual Projects, but the Approval Process in module allowes only set user to be specified as approver.
I'd expect there should be option to use dynamic approver - i.e. asignee or manager of parent record, where the Document is being created. Is there an OOTB way how to achieve this?
If not, what would be the option with minimal customisations to achieve that?
Thanks for help
Best regards
Pavel
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The Document Management module, as a platform feature, is deliberately built with simple concepts in mind so that it can easily be incorporated in many processes across different products in the platform.
The easier, less messy way to achieve your requirement would be to create a simple flow or a business rule on the document record that "On-Insert" adds the assignee of the parent task, project manager or whichever persona you have in your process as a reviewer/approver automatically (these are related records to each document).
The OOTB flow looks at the users in these lists and trigger approvals for them. This way, you don't customize any OOTB logic - you simply "feed" the reviewer/approver persona for documents against specific task types (e.g. project tasks) based on your business process/logic.
You can even remove these tabs from the related list view, so that the user that submits/manages the document doesn't see these or has control over the reviewers and approvers associated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The Document Management module, as a platform feature, is deliberately built with simple concepts in mind so that it can easily be incorporated in many processes across different products in the platform.
The easier, less messy way to achieve your requirement would be to create a simple flow or a business rule on the document record that "On-Insert" adds the assignee of the parent task, project manager or whichever persona you have in your process as a reviewer/approver automatically (these are related records to each document).
The OOTB flow looks at the users in these lists and trigger approvals for them. This way, you don't customize any OOTB logic - you simply "feed" the reviewer/approver persona for documents against specific task types (e.g. project tasks) based on your business process/logic.
You can even remove these tabs from the related list view, so that the user that submits/manages the document doesn't see these or has control over the reviewers and approvers associated.
