Variables in Catalog Task Short Description

[Blue]

Not sure if I am posting in the right place however, I am curious what are the various perspectives on adding Variables to the short description field of a Catalog Task?

We are revamping our request management structure and are close to making a decision on if we allow short description of catalog tasks to include variables which them makes each task unique.

How does that impact reporting and metrics for catalog tasks?

[Goran WitchDoc]

Not that it is an "instance" issue, but I feel worried that the best way technicians sort their records is by having prefixes in the short description. Aren't there other fields that could be used for this? And scripts/config to handle the short description field, feel like tech debt that shouldn't need to be there.

[Mike_R]

@Goran WitchDoc There aren't really any other fields that would be useful in the Catalog Tasks list view. You can't add variables to the list view..

I didn't recommend creating scripts or anything. He can configure this right in the flow for his specific catalog item. Example

Can you explain how this is tech debt?? Because now I'm very confused!

[Goran WitchDoc]

Technical Debt may not be the optimal word here since there must be something else behind that isn't well thought out. And when there was a time in the future to think it through, then you would need to redo this the future, or you add/remove variables for the catalog item, which then is used in the short description. Also, depending on how the variables are set up, you might need complex logic or different flows to handle which variables are going in the short description.

What values in the variables are that are being put in the short description? Perhaps a simple solution is showing the RITM's item field in the task list. If it's the ability to sort tasks depending on the catalog item, they are looking for. Or it's the setup of groups that needs more split up. There can be a lot of reasons and solutions for this. And who knows, perhaps adding variables in the short description is the only way, but I can't see that right now.

[Mike_R]

@Goran WitchDoc Appreciate the perspective! It's not my go-to approach but there are definitely times where it's just necessary, opposed to another customization (or more granular catalog items and assignment groups).
I know many others have the same experience too.

But like you said there are so many factors and there isn't a simple yes or no answer. It should be evaluated case by case but I certainly do not see any harm, especially if the catalog item "owner" requires this.

If you are building a more standardized or reusable flow that is used across hundreds or thousands of catalog items, then my answer would be totally different. 

[ersureshbe]

Hi, You can achieve under description field. But If you are assignment referring the report based on the variables then you will see the impact with existing reports and you will face the complexities to get the report for variables. You should complex script to get the relevant info.

I'm not sure, what issue faced in variable design. How it impacted to think above idea.