Not sure if I’m missing the option, but is it possible to assign a converted request back to the requestor in the approval process of the converted object?
For example, if I convert a request (issue) to a task or even a project, can I have the approval process within the new task/project automatically route to the requestor of the origianl request?
Thanks,
Vinay
Views
Replies
Total Likes
Got it, thank you for the quick reply!
Views
Replies
Total Likes
Hi @VinayPa1
reply here since Adobe doesn't allow me to reply to your DM
Hi Vinay,
Some thoughts:
Scenario 1:
Approval process: Change the status to something different from the current status once 'approved,' and not only change it if it's 'not approved.'
That's doable - you check whether status just moved from {STATUS}:A to {STATUS} and then set the status to the desired value.
Scenario 2:A free user requestor submits a request with a pre-defined approval process in the request.
The request converts to a task in a different project.
When you convert the request to a task, it loses the approval process, so I want to retain the approval process and ensure it remains assigned to the original requestor.
If possible, I’d like the free user to be able to see any documents attached to the task they are approving—not just in the approval email but also on their home screen in Workfront, next to the item they are approving. Currently, free users only seem to see the detail page or custom form of the task, but not the documents tab.
This process is entirely new, so we're open to how it gets implemented. However, the basic idea is to keep it as simple as possible for both the free requestor and the user who is requesting the approval. At the same time, we want to ensure that the system captures the approval in a reliable way (for example, an update saying 'I approve the document' or sending a link to the document wouldn’t be ideal).
You can't retain the approval through conversion - either you add an update to the task with the approval info, or maybe you can put the approval on the task you just created?
I don't know about requesters not seeing docs on the task the approve - check layout template and access level. If that's the case, you could try creating a custom dashboard (report).
If that fails, Fusion won't help because it's an access issue.
Scenario 3:If a change is made to the custom form, notify the assignees on that object. For example, if the custom form is on a request or task, notify whoever is assigned to that issue or task.
Definitely doable. May not need Fusion - check the Notification settings in WF.
Otherwise, note that notification will to be an Update posted e.g. on the modified task, tagging people you want to receive the update. Without update there is not "custom notification"
Remember that Fusion doesn't do anything you couldn't also do manually in WF. If you can't do it manually - Fusion can't do it either (e.g. trigger a notification without Update).
Views
Replies
Total Likes
Thank you for the information on these, really appreciate it!
Views
Replies
Total Likes
Hi Vinay,
You will need to have a fusion scenario set up for that particular automation.
thanks Sujatha
Thank you, will give this a try!
Views
Replies
Total Likes
Views
Likes
Replies