Skip to main content

I have logged an idea for this, but am wondering whether anyone may have a better idea of achieving this?

We have a custom logging form that has a custom item lookup, and what I would like to be able to do is provide the user with a short summary of what that item is/does. It doesn’t look like the we are able to amend the column profile that appears in the item lookup so it includes a remarks field from the CMDB, so the only way currently to achieve this is to create a caption field and manually enter the text - but for 100’s of items, this is not feasible. 

Ideally, what I would like to happen is when an item is selected, the next custom is a caption that is configured dynamically pull through the information stored in the remarks field of that item in the CMDB - only needing 1 caption field instead of 100’s. This currently isn’t possible, and logged an idea for this 5 months ago, still with no solution.

Is anyone able to advise if there is a better way to achieve this? 

Any help is appreciated - thanks in advance

I don’t think that this is what you are looking for but it might be helpful:

 

https://wiki.axiossystems.com/assyst11-8Wiki/index.php/Dropdown_Trigger_For_Item_Lookup_System_Parameter

 

This System Parameter identifies the minimum number of characters that must be typed before a type ahead drop-down will appear under the input field in Item record searches. This applies to the assyst Portal only (not Self-Service Portal).


Hi Chris, 

It’s not available right now however we do currently have a story in the backlog for 11.9.0 that would implement dynamic captions as you suggest above. The idea being that you can refer to one or more attributes from an entity in the form (the selected item in your example) and use the caption field to display information from it. 

The development for the story hasn’t started yet however we do aim to have this included in the 11.9.0 release in Q4.

Cheers,
Robert


Hi Chris, 

It’s not available right now however we do currently have a story in the backlog for 11.9.0 that would implement dynamic captions as you suggest above. The idea being that you can refer to one or more attributes from an entity in the form (the selected item in your example) and use the caption field to display information from it. 

The development for the story hasn’t started yet however we do aim to have this included in the 11.9.0 release in Q4.

Cheers,
Robert


We would love this. Especially if you can manipulate the data in the dynamic caption. 

Required by: 2024-09-26

caption: Remember CAB deadline: 2024-09-19

(requiredby_date - 7)


Hi Chris, 

It’s not available right now however we do currently have a story in the backlog for 11.9.0 that would implement dynamic captions as you suggest above. The idea being that you can refer to one or more attributes from an entity in the form (the selected item in your example) and use the caption field to display information from it. 

The development for the story hasn’t started yet however we do aim to have this included in the 11.9.0 release in Q4.

Cheers,
Robert

Hi ​@Robert Wood,

Is the development story you’re referring to here related to this idea?

Just wondering if there’s any news or updates on this?


The reason I ask is that it or a similar dynamic presentation of related data could help unblock several improvements we’ve been looking to implement, both for our end users in the Self-Service Portal and for our IT users. And I’m wondering what the scope of the feature is, and if input is desired. 

To expand a bit on the IT users from our side: our IT users often need to navigate across multiple related resources to get the full picture when working with an item which cause frustration and time wasted. It would be a big help if we could add dynamically generated captions, like a table of information, to an item form (This is inspired by what’s possible using Velocity Templating Language (VTL) and action templates) and thus give user groups such as technicians the information they need in a single location.

While adding information to custom fields could be an option, it risks breaking the single source of truth if not properly maintained. This way a less maintenance heavy solution could still let users get the relevant context from a supplier, related item, or item system etc, without having to rely on us or them to maintain user-group specific integrations as to not get outdated information in the CMDB.
 

Best regards,
Richard