nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ability to reject QA pair creation while unarchiving and completing a project.

Dinesh A

Nick from Netsmart Technologies requested an option to reject QA pair creation while unarchiving and completing a project.

When users complete a project for the first time, QA pair with Save in AL enabled will be pushed to moderation. They will then accept some QA pairs and reject some. Based on this actions, client mentioned a use case.

Accepted QA pairs will move to the Library queue.
1. Unarchiving the Project and then completing it again, the duplicate check will capture the existing QA Pair matches and will provide us the option to skip it.
Rejected QA pairs will remain in the Trash and then be deleted permanently.
1. Now, when the project is unarchived and completed again, users would have to again review the QA pairs in the Moderation queue and reject them again which they already did while completing the project the first time.

This is where client wants a feature to reject QA pair creation completely while unarchiving and completing a project.

DR ticket ID: TKT-212949

Find more posts tagged with

Future consideration

Response Projects

Status: Future consideration

Comments

Dinesh A

@Tyler Richard Can you please take this forward from here?

support

@Dinesh A Got - it. Thank you Dinesh!

support

@Khalees V Hello Khalees - Netsmart is running into issues where when they complete a project, go through the Save to Library workflow and then complete the moderation process. The issue arises if/when they ever unarchive a project and then complete it again, they are being prompted all over again for moderation on a project that they already addressed. Can we create a feature that would prevent this from occurring again?

Khalees V

Hi, Understood the problem. Duplicate check is not required upon subsequent completion of project if there are no changes to the save to answer library setting. We will keep you informed when we prioritize in future.