New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Absent Member.. Absent Member..
Absent Member..
699 views

Interactions Category details Modifications

Jump to solution

Hello , We have CIT scenario Email Fetching in our environment and we wanted to figure out if there is any way we could be able to modify Category, Area,Subarea details of  Interactions which are registred through Email fetching Scenario -with open_idle status. Looks like its OOB behaviour  in 9.30 that after a Interaction registered or escalated regardless of status ie. open-linked or open-idle, Category ,Area,Subarea fields  goes greayed out.

 

Regards

Shailendra

0 Likes
1 Solution

Accepted Solutions
Highlighted
Admiral Admiral
Admiral

Hi Shailendra,

 

In OOB system, when escalating an interaction to incident, the fields: Category, Area and Sub Area are read only with the read only condition that is defined in Form Designer. So if you want to make these fields editable, you should change in Form Designer, uncheck at the Read Only and remove the Read Only condition:

 


Regards,

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

4 Replies
Highlighted
Admiral Admiral
Admiral

Hi Shailendra,

 

In OOB system, when escalating an interaction to incident, the fields: Category, Area and Sub Area are read only with the read only condition that is defined in Form Designer. So if you want to make these fields editable, you should change in Form Designer, uncheck at the Read Only and remove the Read Only condition:

 


Regards,

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.

View solution in original post

Highlighted
Absent Member.. Absent Member..
Absent Member..

The out of box read only controls on the SD.update.interaction format use variables set in the cc.edit.incident displayscreen. Those controls allow for an ESS-submitted ticket to be reviewed and updated before most fields are set to read only.

 

The challenge is that you need to provide similar capablities for a ticket submitted via email. You can do this by:

  • trying to extend the existing controls for edit to allow editing of tickets submitted by email (assuming you have some way to identify them, or can add a field to do so).
  • add an additional condition to the existing read-only expression on the form to enable editing of a email-submitted interaction.
----------------------------------------------------
Kudos - what, where, how, and why
Want Good Answers? Ask Good Questions...
Highlighted
Absent Member.
Absent Member.

Hi,

 

You can always set a custom flag to true in the CIT scenario for the interactions which are logged through email.

 

After that you can write a condition in incidents format control to check if the flag is true and set the read only/editable conditions accordingly.


Assign Kudos by clicking on Star on your left ,if this post helped you in any manner...Thanks...

Gaurav
Highlighted
Absent Member.. Absent Member..
Absent Member..

removing readonly condition from SD.update.interaction has helped.  Thanks everyone for your help.

 

-regards

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.