Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We have a system where programs are given a unique ID and further classified by module. We have four modules Finance,Suppy Chain,n2, n3.. And for each program we need to store Technical and Functional Design docs.. Example ID are:
FIR8745 (Finance Report to display expenses xxxx)
SCR6734(Supply chain Report to display inbound PO)
How would we store these in confluence?
I would say your best starting point is to read up on Labels -- this Atlassian page is a good read. Labels help you contextualise the content, and then you can use several macros to pull back content containing specific labels.
I've always found this the easiest way to look after content and stop things getting misfiled. You do get issues where people forget to add labels, so often what I end up doing is creating templates that have the labels I want on, and then using the Create From Template macro as a button on documentation pages to reduce the chance of people not using the right labels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Paul Dymecki,
These seem like clear metadata for your files/pages to me. I would recommend you to take a look into the page properties macro to add those structured data to your pages.
In short, the macro lets you add a table with property names and values to the top of your page. See this example to illustrate:
You can even create a separate page that may act as a table of contents. Using the page properties report macro, you can list those properties of all pages like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.