Understanding the catalog item request flow

[Sanjay Rallapal]

Hello all

I am looking for pointers on how the catalog item request process works. If this already covered in docs, I'd appreciate a pointer to the same.

When a user requests an item (and they can only do so OOTB for either themselves or for one other person),

1. first the service catalog request is triggered, then

2. the service catalog item request is triggered for each item in the cart

At least this is my understanding. 

What is not clear to me

1. What indicates that the sc catalog item workflow has been successfully completed. 
2. What indicates completion of the sc catalog workflow

[Dr Atul G- LNG · Accepted solution]

Hi @Sanjay Rallapal 

When a user requests an item (and they can only do so OOTB for either themselves or for one other person),

1. first the service catalog request is triggered, then

2. the service catalog item request is triggered for each item in the cart

Atul:

Yes, here's how it works:

An end user visits the catalog page, selects the desired item, and submits it. (This is part of catalog management.)

After submission, the system creates at least two records: a REQ (Request) and a RITM (Request Item). (This is part of request management.)

At least this is my understanding. 

What is not clear to me

1. What indicates that the sc catalog item workflow has been successfully completed. 

Atul: Each catalog item is linked to a flow or workflow, where the execution steps are defined. These steps include actions such as approval, catalog task creation, and more. Once all tasks are completed and closed, the RITM and REQ are moved to a "closed" state, indicating that the flow/workflow has been successfully completed.

2. What indicates completion of the sc catalog workflow

Atul: Once all defined tasks/ approval has been completed then it is considered as completion. 

These are my 3 videos, which help you to understand the whole process.

https://youtu.be/OJ5slCwIvXo

https://youtu.be/m5cIQeGwCWU

https://youtu.be/gcvO5L_fSms