Post

2 followers Follow
0
Avatar

Custom Fields For Multiple Department Use

We have multiple department using Clarizen, each with their own needs of Custom Fields, i.e, IT department needs different Custom Fields, and Marketing needs different Custom Fields.

We are using Clarizen as a central ticketing system where ALL requests will go to, and once the requested has been approved, we will convert the Request to  Project(s) or Programs, and then assign the proper resources.

What is the best way to handle ALL these different custom fields?

We don't want a Request with 100 custom fields on it, it would be unusable.

Do we create multiple Form/ Request or whatever objects needed to store those custom fields and Attached / Linked them to the project?

Any help would be greatly appreciate.

Michael Pham Answered

Please sign in to leave a comment.

2 comments

1
Avatar

I would suggest using both custom fields and different profiles to alter the views of each department.

Using the custom fields as required you can then show or hide as needed for each departments profile and view.  I would also use custom actions to generate department specific forms for creation of the request using the fields required for that department.  In a similar way I would have a request type field that you can use to designate which department the request has come from.  This could also help with filtering views for each department so they only see their own requests.

Phil Smith 1 vote
0
Avatar

Hi Phil, Could you expand on custom action - "  I would also use custom actions to generate department specific forms for creation of the request using the fields required for that department.  In a similar way I would have a request type field that you can use to designate which department the request has come from.  This could also help with filtering views for each department so they only see their own requests."...

Could you give some samples/examples? How do attach the form to the request?

Michael Pham 0 votes