"Submit Catalog Item Request"-Action for Flow - does it even work?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2021 12:30 PM
Hi everyone,
I am having a lot of issues on a fresh Paris instance with the "Submit Catalog Item Request"-Action for Flow Designer.
Two examples:
- Global: I created a demo Item "Software Order" with a list collector variable on the Software Model table. When I order the item directly, I can select one or more models and submit. When I order the item from the Flow with the new "Submit Catalog Item Request"-Action, I can't populate the variable at all. I just cannot select any record to put into the list.
- Scoped: I created a demo item "Create Exchange Mailbox" with the new Requested For Variable Type (set to mandatory). Again, when I order the item directly, I can select a user and submit. When I order the item from the Flow with the new "Submit Catalog Item Request"-Action, I can populate the variable with a user but when the flow is executed, i get an error message "The value for mandatory field 'Requested For?' is empty or invalid". The flow execution log in contrast clearly shows that the "requested for" variable has a valid value.
Is anyone already using the Action and can that it works as intended? So far I can only use it without errors on items which require string inputs or no inputs at all..
Thank you for any help,
Thilo
- Labels:
-
Request Management
- 2,958 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2021 12:19 PM
Experiencing the exact same thing, but in Quebec. Have you found any ways around this that aren't a lot of work?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2021 04:13 AM
I appreciate your feedback but unfortunately the answer is NO. I really like the Flow Designer approach and all the integration hub extensions. It still feels crippled for advanced orchestration scenarios though. Missing flow variables on subflows does not help either 😉

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2021 01:05 PM
After some decent digging I found this: KB0962980. It seems like one or more of the complex variable types are not supported for this action. Why this info is not in the Docs site (for Paris or Quebec), is beyond me. But the Docs site sucks on most things, so I guess I shouldn't be surprised.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2022 10:31 AM
I'm looking for the same info - which is starting to rank up there with a search for Bigfoot or something else 'heard of often, never seen'!
According to the page - last updated 07/22/2021 - SN reports that the following Info in Rome:
Note: The following Service Catalog variable types are not supported.
- list collector
- lookup multiple choice
- lookup select box
For the case I'm working on, I will need to draw from 1 single and 2 mulit-line text fields and 3 Select Boxes (Not Lookup Select boxes). I followed to email request item example and it didn't work for my item. I know how to use the action to generate change tickets from a request flow, but this example took me nowhere.