As "Currency rates" are mentioned, I wonder if the could that be used to store a tracker of "semi-hard" values that need to be reused in other places ?
If we could declare system tracker, we could use a system.tracker.company to store and manage wiki variable like a company name (displayed on documents, invoices)
{system.company.name} = "Bernard Sfez, inc."
Or also VAT rate need to be used in many places (displayed on documents, invoices, etc and used as value in calculation)
{system vat.rate} = "17%"
This would make things more solid than they are so VAT is not changeable by mistake on a tracker accessible to editors (role)
To complete the Rates and VAT case, the value should be changeable BUT with garantie that previous document stay with the previous value.
IE: We have a calculation and display of VAT for documents (invoices) before February 2022 with {system vat.rate} = 17% and we have calculation and display of VAT for documents (invoices) after February 2022 with {system vat.rate} = 18%
What about using a system tracker to manage signatures ?
This is also (in some aspect) a "upper data" with its own properties and attributes that is to be attached to objects (like currency)
The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.
Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.
As "Currency rates" are mentioned, I wonder if the could that be used to store a tracker of "semi-hard" values that need to be reused in other places ?
If we could declare system tracker, we could use a system.tracker.company to store and manage wiki variable like a company name (displayed on documents, invoices)
Or also VAT rate need to be used in many places (displayed on documents, invoices, etc and used as value in calculation)
This would make things more solid than they are so VAT is not changeable by mistake on a tracker accessible to editors (role)
To complete the Rates and VAT case, the value should be changeable BUT with garantie that previous document stay with the previous value.
IE: We have a calculation and display of VAT for documents (invoices) before February 2022 with {system vat.rate} = 17% and we have calculation and display of VAT for documents (invoices) after February 2022 with {system vat.rate} = 18%
A bit like the "strange" union of the Plugin Attributes (https://doc.tiki.org/PluginAttributes) and the Dynamic-Variable (https://doc.tiki.org/Dynamic-Variable) ?
Those exist but rarely used as they are quite not user-friendly and hard to control once set.