Service Catalog: Using Fields

Service Catalog: Using Fields

Can someone explain when we should use Service Fields (i.e., Add New Field) versus Add Resource.

I need to thoughtfully deploy self service through the portal, but I don't want to deploy only to find out I should have used one method versus the other.  Does ManageEngine have some scenarios or use cases for using one versus the other?

For Example: Thinking of both Service Fields and Add Resource fields,
1. Can the fields be accessed in other parts of SDP through variabled?
2. Are all fields available to be reported on and/or be used in a query report?
3. Do we have access to these fields in the Request view?
4. Can all fields be manipulated in the Field & Form Rules?

I really like the benefits of "Add Resources," but I've never really understood the distinction between the Service Fields and Add Resources. I understand it when the resource is a traditional resource (e.g., laptop, printer, computer). However, my example scenario could be something like employee onboarding/offboarding:

Terminate Software A account:
Domain Name
Full Name
Effective Date (required field)
Effective Time (required field)
Move existing files to manager (Y/N)

Later, I want to perform reporting on my terminated accounts and include the fields in the report.
What if I want to use conditional formation:
Effective Immediately (default Yes)
  If default No Display Effective Date and Effective time and make them required fields

Thanks,
Adam

                  New to ADSelfService Plus?