A) Files from custom file fields in Classic Knowledge articles are moved to the standard Files object. After migration, view and attach files in the Files related list.
B) Visualforce pages that refer to old article types
NOT C) Data model: "Custom article types" are migrated to "Standard record types", BUT if you map them! The problem here is the word "MUST".
NOT D) Approval process history doesn’t migrate to Lightning Knowledge.
E) For orgs with multiple article types, article numbers change during migration. Because Article Number is a standard auto-number field, you can’t retain the numbers when migrating to Lightning Knowledge.
Approval Process History does not migrate to Lightning Knowledge. Article Number is a standard auto-number field, you can’t retain the numbers when migrating to Lightning Knowledge. So answer is ACD.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
oalexandrino
11Â months, 3Â weeks agoVir56
1Â year, 2Â months agoBolumighty
1Â year, 3Â months agoNaskarbhai
1Â year, 7Â months agoEliasSF
1Â year, 8Â months agoJoe1Sf
1Â year, 5Â months ago