- Check to ensure the citation, including stub citations if applicable, matches exactly.
- Tip: use Research and the suggested match(es) Citation ID(s) to determine if suggested are an exact match.
- Select the citation if it matches.
Multiple matches
Multiple Mandate Citations
The Citation will need to be entered a follow up time for the amount of mandates, and matched to a different mandate each time to ensure all multiple mandates are captured.
Identifying multiple mandates citations: You can tell a citation match is multiple mandates, if it has the same AD ID, same CT Reference number, and different Common Controls (CC ID).
Multiple Citations with different Common Control Matches
If you encounter a situation, where there are matching citations that are not multiple mandates, any of the matches can be selected. Use your best discretionary judgement to determine which one to select.
Identifying multiple differentiated citations: You can determine these are NOT multiple mandate citation, if they have different CT Reference numbers and/or different AD IDs.
Comments
What does the above actually mean? It sounds like we should not be using this feature? Our assumption was that if two controls have the same wording, the same mandates, the same mapping, etc. across two different private documents, one could select the referenced control from another private document to save the time it would take to replicate the work.
For Example: Control "ABC1_PrivateDocument2" is *exactly the same* as Control "ABC1_PrivateDocument1", in every single way *except* that it is logically represented as its own unique control in Private Document 2, Private Document 1 has already been published. Our assumption was that this feature could be selected for the second control, and would replicate all the work done for the first control, saving us the time of performing every step except for the initial control entry. This would be of value to us and save us time.
What seems to have actually happened when we selected this option, instead, is that all subsequent steps for the second control are auto-completed, and the control has disappeared from our citation hierarchy. Rather than saving time, or even doing nothing, this is actually an inconvenience. We will now have to re-create the second, duplicate control in its entirety, from scratch, and find a way to deprecate/delete the citation steps that were auto-completed when we initially used this feature to map the control to its doppelganger in one of our previously imported private documents.
Please educate us if this is completely incorrect. Alternatively, please deprecate this feature, at least until it works properly, and/or warn other users not to use it in the interim. Thank you very much!!!
Hello Quinn,
This function will allow you to leverage mapping from published private documents within your subsequent private document projects.
This only works for Citations that are the same.
The system leverages the tagging and the control match from the previous mapping. The system automatically completes the tagging phase, then generates the Citation in a Matching Task to prompt the mapping team to verify the tagging and control matching from the previous mapping are still relevant and accurate for the current project.
However, for multiple mandate citations, the system currently requires each mandate to be handled separately.
The control should not disappear from the citation hierarchy.
A bug fix pushed yesterday might be related to the issue you have outlined; see release notes here: https://www.unifiedcompliance.com/release-notes-06-21-21/
If this recent fix does not resolve the issue you are encountering, our support team can help investigate and troubleshoot your specific issue. If you haven't already opened up a ticket with our support team, you can reach them at support@commoncontrolshub.com
Best,
Vicki
Please sign in to leave a comment.