Catalog Builder approval frustration

[matthew_magee1]

Hey all,

Having a heck of a time trying to configure the subflow that fires when a catalog item is submitted.

Per the docs, I made a copy of Catalog Builder - Item review subflow and I've verified the subflow is being hit because I've added log statements.

I also watched the video on the docs site but I'm not able to follow what they did and apply it to my own process.

BTW, I'm new to flow designer so that doesn't help.

Here's what I want to do:

1. Catalog Builder user creates or edits a catalog item via Builder
2. User submits item in Builder
3. Group X is notified when a catalog item has been submitted via Builder
4. User in Group X reviews changes and either Approves or Rejects changes 
5. If approved, item is published
6. If rejected, user in Group X has to supply comments. Item goes back to draft and Catalog Builder user/updater is notified 
7. Catalog Builder user makes changes and submits item in Builder.
8. Jump to step 3

This seems very simple to do in my head but I struggling. If anyone has screenshots or previous experience they can share, I'd love to hear it-

Thanks

[Akos Szilagyi]

Thanks for this David! What I fail to understand though, is what sets the Catalog Item built with Builder to the state of In Review / Reviewed. Is this not missing, in any of the flows that were built?

[DavidB-ADT]

When you build something in catalog builder, the last tab/action is to ‘Submit’. If you have the catalog item review property set, then submitting the catalog item initiates the approval flow.

[Javad Nasserifa]

Hi @DavidB-ADT 

Thanks for your guide, unfortunately, the video is not available on YouTube anymore (removed or in private!). 

By any chance, could you please share the subflow screenshot and steps here?  

Thank you in advance.

[Julie Benningf1]

Thank you for all of this. Are you running this subflow in Prod and letting owners make their updates in Prod? Our original thought was to do it in a lower instance, but for small changes, I could see doing it in Prod. 

[Community Alums]

It's a pain isn't it! 

There are more nuanced solutions, which are mostly addressed by other replies in this thread. I just thought I'd share a simple workaround we're using until I set it up correctly. 

I simply created a UI Action called 'Approve review' (I have it sitting next to the 'Cancel review' OOTB one) which shows on the Cat Item which is in the 'In review' state. The UI Action updates the state to published and marks the catalog item as active. 

We're not pumping out catalog items, so if we receive a request to 'approve' a new cat item is straight forward; we review the catalogue item in the console and hit the new UI Action if we're satisfied with it.