Configuration
Last updated
Last updated
All settings are related to a specific Boomi Account, as well as all links are saved per Boomi Account in your personal browser local storage.
It is highly recommended to setup a Boomi API Token for Linked-Pages for Boomi Integration!
It is highly recommended (even if not required) to setup a Boomi API Token for Linked-Pages for Boomi Integration so that it can query component metadata information from Boomi AtomSphere.
If you don't provide an API token Linked-Pages for Boomi Integration cannot display component names, neither can it query or display path (component directory) information or component types.
The Team Token is used to synchronize the local links with an Azure Web-Service - per Boomi Account - so that all team members with the same Team Token on the same Boomi Account can use these links (shared documentation)
Confluence requires special handling because Confluence-Links to documents are not permanent. Means: Confluence links to a document page can become orphaned and be replaced by new ones. Linked-Pages for Boomi Integration is able to handle this behaviour, if you provide a semi-colon separated list of Confluence roots.
Link titles are read from the browser url, and such titles can become very long, containing unwanted information. Use the Title Cleansing RegEx to advise Linked-Pages for Boomi Integration to remove part of (recurring) titles.
I recommend using (\s-\sConfluence) to strip off unnecessary Confluence information.
Linked-Pages for Boomi Integration stores all links in the browser's local storage. If you want to synchronize your links - share your documentation - with other team members, you will need to obtain a Team Token.
