Schedule Job and Flow designer

[Community Alums]

Hi,

I want a catalog tasks to be created on a weekly basis for all the server CIs where the owner's account got deactivated. Catalog tasks should be assigned to owner's manager and all CI's related to one particular owner (Inactive) should come under the affected CI list of that catalog tasks.

Thanks in advance.

Regards,

Muskan Jain

[Mark Manders]

Your question is titled 'Schedule Job and Flow designer'. How is that related to your 'question'?

Also: you aren't asking anything. You are making a statement/putting in a requirement. What have you already done and where are you stuck? Or do you think the community is just a free resource to do your work for you?

This is all easily done through the flow designer.

[Community Alums]

Hi,

This is the first time I am posting something on community may be that is the reason I am not fully aware about this.

I want to mention here that I have already tried with the schedule job and flow designer. Below are the steps I followed for this requirement:

1. I have created 1 catalog item and triggering the catalog through schedule job.

2. Then, I have also created 1 flow which creates the catalog task but I got stuck in the assignment of catalog task as Flow designer is new to me.

3. Next I am not sure if it is possible to fetch the list of all affected CIs in the related list of catalog task through Flow designer.

Apologies for the confusion and Thanks for your response.

[Mark Manders · Accepted solution]

Get rid of your scheduled job, because you can also schedule flows. Also: a catalog task usually is related to a requested item which is related to a request, so you may want to reconsider user catalog tasks for this, but that's up to you.

After the scheduled trigger do a look up records to all users that got inactivated. Then a 'for each' to look up the CI's with that user as owned by. Create a task record (again: check on which table this makes sense) and assign it to the owner's manager with the info needed and do a 'for each' on the ci to put it into the affected ci list of the task.

[Community Alums]

Thanks Mark. It worked for me.