Task & SLA Configuration requirement for a catalog item request

[Suneel9]

We have a catalog item that is used for automating an activity through 3rd party application integration. There is no human involvement required and the result is either success or failure, and the request item is closed with status "Closed Complete" or "Closed Incomplete" with is few minutes of request submission based on automation activity status.

My questions related to best practices:

Do I really need to create and associate Catalog Task (even though no one is involved to complete the activity)?

Similarly, do I need to associate SLA? As of now I don't have Catalog Tasks and associated SLAs configured. 

Thanks in advance.

-Suneel

[Tony Chatfield1]

Hi, I would say no to both your questions, if there is no human involvement the business will derive no benefit from a sub\catalog task as it will not be assigned to anyone to complete and so is not required. Similarly, unless your organization has a contracted SLA deliverable that needs to be tracked and reported on, then there is no benefit to using SLA to monitor your compliance for this requirement as it is delivered by automation and so can be safely assumed to be complete when logged (or within XX seconds of being logged).

[Robbie]

Hi @Suneel9,

Did you see my earlier response?

A task is simply a record that can be assigned to someone in order to complete an activity. The fact this is not needed or required tells us that we should not over complicate the process. Therefore I would not create one.

Similarly, it’s seems an SLA would also be redundant as any reporting or measurement could be based on the Catalog Item itself including the final state (Closed Complete or Closed Incomplete), duration and any other data point.

Therefore, I would again advise an SLA. Is not required.

@Suneel9 - To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.

Thanks, Robbie