Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    18
  • Views views
    85
  • Users 0 members are here
Related
Options

Use of ActualService and MultiEntityPicker for Devices in an Offering

Emil Dutsov
 

Hi,
Is i possible, in an offering, to use MultiEntityPicker Device field related to an Actual Service field and Service component field in the same way they are connected in Incident and Change ?

The flow is like this:
The Portal user selects Actual Service in one field - EntityPick

The portal user selects Service Component. - EntityPick

The next field "Devices"  is MultiEntityPicker and allows the user to select multiple Devices, but only the ones related to the Actual Service ?


The customer has Native SCAM enabled.

It would be nice to be able to use MultiEntityPIcker fields instead of MultiList.

Kind Regards

Emil Dutsov

  • 0  

    Let's start with clarifying the terms.What you call "MultiEntityPIcker" is a Many2Many relationship.So if you are looking for replicating the same behavior, you need to expose one (either OOB or custom) onto the relevant Portal form.

    Best regards,

    Brindusa

  • 0   in reply to   

    Hi Brindusa,

    If you open InvolvedCis form for Incident or Change the first field is of type MutyEntityPicker. (AffectedDevices)

    We can add this field to the Service Request  in Studio and hide the field for all offerings where it's not relevant. Yes I know this not exactly best practice as it will require extra business rule, but it works.

    We want to also expose Actual Service and Service Components and simulate same behaviour as in Incident and Change.

    Cheers!

    Emil

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.