Record Producer or other method to Update Catalog Items

[ChadWilhelm]

I would like to do a POC on the following use case.   We get a lot of enhancement requests to update variable values across catalog items including delete and I was thinking it would be fantastic to have a record producer or other method to update values  once the cat item owner approves of the change.  I would envision that the user would select the catalog item then the variables would be listed for that item they would select add, modify or delete.   If add is selected then single text appears asking user to put in new value.   For Modify I show current values then ask what needs to be modified.   For delete just delete.   Has anyone ever tried anything like this.   Is this is too big of a ask or not worth the trouble?   Any ideas are welcomed.   

Thanks,

Chad

[Dr Atul G- LNG]

Hi @ChadWilhelm 

As a process consultant, let me share my thoughts. You can track this through a Story instead of creating a completely new record type. Ask the user to add details within the story.

If you still want to proceed, first check how you want to give visibility to the user—to see all catalog items, respective variables, and operations. If that variable is being used elsewhere, then I’d suggest adding an approval step in between before taking any final action.

Otherwise, it’s better to handle this as part of your enhancement model under Agile—using a Story—instead of going through the longer REQ/RP route.

[ChadWilhelm]

Hello, appreciate the feedback.   My thought doing through Request and Approval gives the customer the power to change the catalog data without the need to wait for the developer to make the changes.   Once the approval is completed, the change is automatically done thus no story needed.

I just don't know if anyone has ever attempted something like this or is even worth it.

Thanks,

Chad 

[RaghavSh · Accepted solution]

@ChadWilhelm Updating catalog item short description/ description is fine but updating/deleting variables is going to be very risky. 

Variables are used in flows/workflows and have some logic around them which can break.

There are client script/ui policies based on variables which can break

Also, variable set has to be explored.

So lot of coding and not recommended.

[ChadWilhelm]

Thanks.  That is what I thought.   Just wanted to get feedback.   Perhaps we can still use add and modify if client script are using the sys_id instead of name.