Basic rich text to be configured during Jaggaer file import.

Current behavior:

The response answer type of a Jaggaer file is automatically set to text upon import; as a result, the user is unable to add Merge tags under the Text answer type.

Expected behavior:

Basic rich text support merge tags to be included when importing Jaggaer files.

Jaggaer file is attached.

Reported company: Saviynt

Ticket: 53517

answerTo_rfq_502.xlsx

Find more posts tagged with

Fixed/Implemented

Status: Fixed/Implemented

Comments

Sunitha

@ashaa @Khalees V Since the user is dissatisfied with the workaround of having the support user manually configure everything, this needs to be addressed on priority. I've included their feedback below for your reference:

"Thank you for the update. While I appreciate your "workaround", this is not acceptable. We have Confidential documents during the RFP process that only we are allowed to work with. We are not to share these documents with anyone outside of our small RFP team. However, your technical issues are preventing us from being able to honor that confidentiality. This is something that should have been caught during your transition from the Classic UI. So the only way at this time for us to comply with customer confidentiality, and do the job correctly, is to copy and paste the entire RFP into an acceptable format that will allow import into Responsive, then once the project is complete, we must export the response, and then tediously copy and paste each answer back into its original format, one by one. This is a huge step backwards, and is now a serious issue for us to complete our work in a timely manner. "

Khalees V

@sunitha Few questions and Clarifications

Can you help me understand this statement - This is something that should have been caught during your transition from the Classic UI.
Why do they want to manually configure the Jaggaer?
Do you know how many Jaggaer files they import in a week or month?

Sunitha

@Khalees V :

Can you help me understand this statement - This is something that should have been caught during your transition from the Classic UI.- The main problem is that the merge tag value is not supported for Jaggaer files. This is not what the user is attempting to convey, and we should have recognized this when we retired the Classic UI.
Why do they want to manually configure the Jaggaer?- manual configuring of Jaggaer file is not an option because the file automatically configures itself upon import; only support users are able to modify the configuration. They are not happy with the workaround offered because Merge tags can only be included when we manually configure them.
Do you know how many Jaggaer files they import in a week or month?- Although it looks like they upload Jaggaer files regularly on their instance, I will need to verify this data.

Khalees V

@sunitha Can we connect on this. I am kind of not clear on the ask. I will schedule a call today.

ashaa

This is now implemented and available in production, hence changing the status.