15 articles
Flow Config
A Tour of Flow ConfigSix views, each with one job — where everything in Infohub is configured and why it is split up that way.The Model TreeFolders, metrics, measures, and event schemes — what each level is for and why the distinction matters.Folder Structure Best PracticesNaming and hierarchy conventions that keep a model navigable after it has quadrupled in size.The ToolboxThe Toolbox holds everything defined once and used everywhere — time schemes, shifts, limits, functions, enumerations, model attributes and palettes.Object Operations in Flow ConfigThe commands that appear on objects across every Flow Config view — what each does, and which objects it applies to.The Deployment ViewWhere Infohub's running components are defined — platforms, servers, engines, connections and consumers — and the rules about what can be added where.Flow Config's Toolbars and IndicatorsThe Flow Zone, the Defaults toolbar, and what the coloured marks on a template entity are telling you.Model AttributesNamed values attached to the tree and inherited downward — the mechanism that lets one template serve dozens of instances.Deploying ConfigurationConfiguration is inert until deployed. What the deployment states mean and why "Different" is the one to watch.Importing and Exporting ModelsMoving model content between instances with .flowMdl files — what travels, what does not, and how mapping works.Templates: ConceptsA template is a class and a model entity is an instance — Infohub's templating is genuine object orientation over the model.Templates: Instantiating and UpdatingThe operations in order — release, instantiate, update, link, delink — and what to verify after each.Template TroubleshootingDecoding the errors template updates actually throw — key not present, duplicates, stray measures, and instances that fault after an update.Templates Across CalendarsOne template, instances on different time schemes — the mapping rules, what breaks, and the pattern that works.Template Servers and FederationPublish templates from one instance and consume them at many — how the link, the tokens, and the derive operation work.