Options
How have you configured cost for Request Offerings?
Leigh_Kilday
Member Ninja IT Monkey ✭✭✭✭
We've been asked to look into showback against some ROs. The requestor is expected to see a dollar value against the RO in the portal.
I have seen plenty of examples (but no code) of cost being associated with a related CI, but we don't operate this way.
I don't want to add the cost to the description - sadly, nobody reads that.
I have seen plenty of examples (but no code) of cost being associated with a related CI, but we don't operate this way.
I don't want to add the cost to the description - sadly, nobody reads that.
0
Best Answers
-
Options
Tony_Collett
Cireson Support Super IT Monkey ✭✭✭✭✭
It could be attached to the title using ARO Multi Mapping Feature or possibly included as a seperate field. Perhaps something that is run automatically if there is no question asking for cost. If you have a bunch of attached Catalog items which have costs associated, a runbook could grab each cost, add it up and then add it to the title or description.
It could also be included as part of the notification (use <H1> if people aren't seeing it straight away
) 5 -
Options
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
Hi @Leigh_Kilday
Having the value attached to a CI is a good way of identifying a cost associated with a particular service.
Another way you could do it for the Request Offering, before the user clicks save, is to use the Display Only tag for an Input option. This will display the text on the screen as the user is in the request offering.
If you wanted a certain cost to appear based on the name of a service or a value from a drop down list, you could use the value to show\hide the Display control.
The other way you could work this in is by using the ROToolbox (https://github.com/doyle-johnpaul/ROToolbox) and use the @AddInformation control to add additional text inside the RO.
Also remember, if you enter HTML code in the RO controls, that HTML will be rendered in the portal so you can also use this in creative ways.
Keen to see how you end up doing it.
Kind regards,
Brett Moffett5
Answers
It could also be included as part of the notification (use <H1> if people aren't seeing it straight away
Is there a guide for how to configure these? E.g. Model is mandatory but I don't know where to set it.
Finally, how would you go about presenting this to the user in the portal prior to making the request?
Having the value attached to a CI is a good way of identifying a cost associated with a particular service.
Another way you could do it for the Request Offering, before the user clicks save, is to use the Display Only tag for an Input option. This will display the text on the screen as the user is in the request offering.
If you wanted a certain cost to appear based on the name of a service or a value from a drop down list, you could use the value to show\hide the Display control.
The other way you could work this in is by using the ROToolbox (https://github.com/doyle-johnpaul/ROToolbox) and use the @AddInformation control to add additional text inside the RO.
Also remember, if you enter HTML code in the RO controls, that HTML will be rendered in the portal so you can also use this in creative ways.
Keen to see how you end up doing it.
Kind regards,
Brett Moffett