Building Scenario to Remove Custom Forms from Tasks | Community
Skip to main content
ConnorO2
ConnorO2
Level 4
March 28, 2025
Solved

Building Scenario to Remove Custom Forms from Tasks

  • March 28, 2025
  • 1 reply
  • 727 views

I'm trying to figure out which module works best for removing the custom form attached to a Task. 

I don't necessarily what to delete the task so I know it's not the Delete Record Module. 

 

But when I go to the Update Module, it doesn't really show a way for me to remove the Category ID. 

Gives me the ability to update the form or ID but not a way to delete it. 

 

Is there a function that works for this? 

Best answer by ConnorO2

Because of how forms (categories) are connected to tasks

 

and because I don't know of a "removeCategory" method, I get the collection objectCategories

Then I modify the collection and replace it on the task object. 

 

In your case it's pretty simple: 
We get a list of existing objectCategories, and collect all but those that point tot he forms we want to remove. 
So if your task has forms A B and C, and you want to remove B, we keep all objectCategories except the one that points to B. we then overwrite the property objectCategories with the new list

 

Since you're not doing anything to the actual forms/fields values, we can simply give WF the new list og objectCategoryIDs - we don't need to pass anything else:

 

Example: I want to remove the 3 marked forms

 

 

 


Wasn't able to successfully setup your scenario but I have a ticket in with Support regarding this. They sent me over this template (see attached zip file) and the probably I'm running into is that these projects are closed or cancelled so I have to reopen every single project. 

However, there are several tasks within each of these projects that I'm trying to navigate and remove the form from to then turn back into the original status of either canceled or closed. 

 

Waiting for a response from Support but this is super frustrating, there should be an easier way to bulk remove all of these templates. I might just end up having them remove the form at this point. 

 

Appreciate your assistance though! 

 

1 reply

Sven-iX
Community Advisor
Sven-iXCommunity Advisor
Community Advisor
March 29, 2025

Custom forms are linked to a business object with a "linking object" called objectCategory

 

see https://developersupport.workfront.com/page-api-explorer.html

 

You'll have to get the object (TASK) and it's objectCategories:categoryID (maybe :name as well) . This gives you the array of object categories, each of which has a category object. 
then you iterate throug the object categories with a filter that excludes the one you need to remove. Collect the remaining categories in an array, convert to JSON and update the object. 

 

If it's a single form, just set the objectCategories to null. 

 

You'll have to use the customAPI module. 

 

does that help? 

    ConnorO2
    ConnorO2Author
    Level 4
    March 31, 2025

    I was able to get the objectCategories but how do I delete it on the object? That's the part I'm confused by. Sorry if my initial message was unclear. 

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    March 31, 2025

    Because of how forms (categories) are connected to tasks

     

    and because I don't know of a "removeCategory" method, I get the collection objectCategories

    Then I modify the collection and replace it on the task object. 

     

    In your case it's pretty simple: 
    We get a list of existing objectCategories, and collect all but those that point tot he forms we want to remove. 
    So if your task has forms A B and C, and you want to remove B, we keep all objectCategories except the one that points to B. we then overwrite the property objectCategories with the new list

     

    Since you're not doing anything to the actual forms/fields values, we can simply give WF the new list og objectCategoryIDs - we don't need to pass anything else:

     

    Example: I want to remove the 3 marked forms

     

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...