Query Prompt (Related Incident) Help Needed
I'm creating a fairly simple ARO for another department. One of the prompts they want to have is "Related Issue ID" which should be a way for them to type in IRxxxxxxx and then link the result(s) as a related item.
I'm a little unsure how to configure this prompt once I add it. Please help if you can. Let me know if you need more information than what I've provided.
Best Answers
-
Geoff_Ross Cireson Consultant O.G.Hey Chris / Adam
I didn't expect this to work but I configured it all up and... BOOM! it just worked.
I selected the option 'Add user-selected objects to template object as related items' which technically doesn't mention the Config Item Relates to Work Item.
The other option 'Add user-selected objects to template object as affected configuration items' was greyed out which makes sense as that is not relevant.
It appears is it clever enough to use the right 'related item' relationship as once I completed the RO, the selected IR was linked and Related Work Item.
This was with an ARO with Portal v 6.0.2.
In summary, add a Query Results prompt, and configure it by selecting Incident as the class, choose any criteria of which ones the user can pick from, choose the columns to display to help their selection and then finally, on the 4th tab tick 'Add user-selected objects to template object as related items'.
Good luck,
Geoff6 -
Geoff_Ross Cireson Consultant O.G.@Chris_Keander In that case, you'll probably be best of just having a text prompt and then using a RBA to add the relationship. The portal itself won;t be able to turn a string into a related object as its just too vague.
I can help with some PowerShell for the Runbook, but in the morning...6
Answers
That said, the GUI prevents you from establishing this relationship successfully so I've for the longest time been under the impression that this can't be done. I hope someone can prove us wrong!
Worst case scenario - I can multi-map it as text to the Description field.
I didn't expect this to work but I configured it all up and... BOOM! it just worked.
I selected the option 'Add user-selected objects to template object as related items' which technically doesn't mention the Config Item Relates to Work Item.
The other option 'Add user-selected objects to template object as affected configuration items' was greyed out which makes sense as that is not relevant.
It appears is it clever enough to use the right 'related item' relationship as once I completed the RO, the selected IR was linked and Related Work Item.
This was with an ARO with Portal v 6.0.2.
In summary, add a Query Results prompt, and configure it by selecting Incident as the class, choose any criteria of which ones the user can pick from, choose the columns to display to help their selection and then finally, on the 4th tab tick 'Add user-selected objects to template object as related items'.
Good luck,
Geoff
In relation to the "crash" scenario I mentioned, I did this with the stock Request Offering mechanism and the portal refuses to load that new work item. But to be fair, this was in the 2.x, 3.x days of the portal. Curious if that this means it's resolved as a result of ARO or 4.x/5.x/6.x
I just don't know how to configure the criteria for this:
The scenario I originally configured used the Incident combination class, and showed a list of Incidents where the affected users was the current signed in user (i.e. Use the Set Token and grab the user's username).
Then it only showed their incidents and they could pick/filter on theirs. Just to sit/think on the page you're on for a second, you're trying to show a list of Incidents to a user to pick. What's the criteria for an Incident being in this selectable list? The title contains something? The Affected User is the currently signed in user? The status is resolved/closed?
I suggest using a different criteria and possibly a different Class to generate a list of Incidents here.
This is going to be a form used by select individuals to submit bug reports for our PeopleSoft developers.
Perhaps they'll always be classified the same?
They'll always be Active/pending?
The source will always be something?
I'm typing outloud as you can probably tell.
Certainly there has to be some kind of shape to this data?
I can help with some PowerShell for the Runbook, but in the morning...
What will be confusing is having that extra filter text box above the built in filter text box in the Query Result part on the form.
Your question has helped me realize you can link more stuff to even more other stuff. Thanks for that.