Alternatively, let us change the editor options to meet our customer's brand guidelines similarly to how we do it within a portal. If we can change the header, paragraph, bulleted and numbered list, special content box, etc. within the editor, we wouldn't have to rely so heavily on custom HTML within the articles.
We also have this issue and would like a solution ASAP. Our KAs are client facing and are accessed through a Power Pages portal. We have extensive references between articles and urls outside of the portal. Articles outside of the portal are fine since the url is static. Referencing the current, published article by article number would be ideal for our use case.
there should be an option to have a default endpoint which we currently have but in the template also have a separate link that triggers to look at if failed in VIES. this is a major issue and needs to be looked at. its pointless having to disable this feature because VIES website doesn't have a parameter to validate.
I totally agree with this idea. It better to have at least an API to utilize to have a process automated either to notify the team that there is an upcoming auto-update, if it is active or paused, and giving an option to pause the auto-updates.
It is highly likely that one might miss out on checking the auto-update dates, extremely common human error.