Home› Service Manager Portal Feature Requests
We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Show Request Offering link atop WI forms (like SCSM console)

Leigh_KildayLeigh_Kilday Member Ninja IT Monkey ✭✭✭✭
in Service Manager Portal Feature Requests

We often get asked to identify the RO from which a SR was generated. At present we are having to look at the console to identify the relationship. There are other methods such as running T-SQL or PowerShell scripts, but none are suitable for end users.

4
Up Down
4 votes

Submitted · Last Updated

Comments

  • joivan_hedrickjoivan_hedrick Cireson Consultant Advanced IT Monkey ✭✭✭
    OOB, this should be a read-only relationship that can be added to a field on any work item. For example, adding the following line should create a read-only text box revealing the parent WI.
    { DataType: "ObjectPicker", PropertyDisplayName: "Source Request Offering", ColSpan: 2, PropertyName: "RequestOffering", ClassId: "8fc1cd4a-b39e-2879-2ba8-b7036f9d8ee7", Disabled: true },
    Add this to your work item js file (e.g. ServiceRequest.js) and you should get a result that looks something like the following:

    ss_1.PNG 239.6K
  • Leigh_KildayLeigh_Kilday Member Ninja IT Monkey ✭✭✭✭

    Thanks Joivan!

    Is there a list somewhere of the fields available for us to use on these forms?

  • joivan_hedrickjoivan_hedrick Cireson Consultant Advanced IT Monkey ✭✭✭
    Not written down per se. But a lot of the information is on the page https://support.cireson.com/KnowledgeBase/View/1174#/ . 

    For the request offering field, you can take the OOB ServiceRequest type projection, which includes a relationship for request offering. Then you can add this relationship to the form. Similarly, if you have created a custom relationship (e.g. Service Request Has Preferred Contact User), you could configure the Portal to show those relationships as well. 
  • Chris_JordanChris_Jordan Customer Adept IT Monkey ✭✭
    Awesome information here, is there any reason this wouldn't work for Incidents as well?
  • joivan_hedrickjoivan_hedrick Cireson Consultant Advanced IT Monkey ✭✭✭
    This can work for incidents, but the process is a bit more complex. Since the OOB incident type projection does not have a component for request offering, you won't be able to grab that relationship without some extra work. Using the link above as a guideline, you would need to do something like:

    1. Create a custom Incident Type Projection in an MP. It should reference the relationship class "System.WorkItemRelatesToRequestOffering".
    2. Create a custom incident Template which uses this type projection.
    3. Seal and import the MP containing your new template and Type Projection. 
    4. Edit your Incident.js file to include the new form.
    5. In the Portal, edit the section "Assign forms to active directory groups" to use your Form ID defined in Incident.js, as well as your Form Projection ID, which is the GUID of your custom type projection.
Sign In or Register to comment.