The user-created section headers should be removed from the system

Revathi B

There are two issues reported.

The client has reported with Redundant columns in backup sheet.
The user-created section headers should be removed from the system if they are no longer containing any content for any question.

Ticket ID : 64139

Find more posts tagged with

Needs review

Status: Needs review

Comments

Khalees V

@Revathi B Need more details

Can you share screenshot of what you are referring to as redundant columns?
Can you also share screnshot of what you are referring to as user created section headers?
Can you share the customer name?

support

@Khalees V , This is an enhancement for Google.

It is number one priority for them becuase it is causing. lot of manual work for them each time they try to feed the librarry back up file into their home grown AI RFP Accelarator tool they use for Projects.

Please note we are aware that Google is not using Responsive for for project and has it's own AI Project Management platform.

Responsive is used as a Knowledge Management toll for Google Proposal teams.

Here is recording of a zoom call where Google explains to Revathi the challenge https://rfpio.zoom.us/rec/share/QBcncYIxlW5QHK1vYuTQAq9AYsUdDokiaHvZnQamC7lc0XARqH2kVKJ7OwlxDhUb.MqimoGn3EL4zwdWl

Passcode: 7ZIpU?w0

Can you please review and advise?

support

Support ticket https://responsiveio.zendesk.com/agent/tickets/64139

Khalees V

@Revathi B Moving to Content Library team.

FYI: @sathish s

Khalees V

@sathish s FYI

sathish s

Adding @karthikumar FYI @Khalees V

sathish s

@karthikumar I reviewed the recording. This is neither S4 nor a bug.

User Expectation: While generating the back up from org setting, the additional response header not related to selected collection should not be exported
Actual Behavior: While generating the back up from org setting, the additional response header is shown in step 1 and collection is selected in step 2. Since the user choose the collection in step 2, the application will not ignore the additional response header during export.

Recommendation to the user:

Option 1: Uncheck all the irrelevant response header in step 1 while generating back up

Option 2: Delete the additional response header from all content so that the additional response headers will not be shown in org settings. Right now the additional response headers are only removed from "CAIQ" collection. But other org level content has additional response headers.

FYI @Gosia Rios @Khalees V