-
5.01-01 Naming Convention
Use numeric prefixes to signify the order within the process (e.g. 1.1 Import Products, 1.2 Import Product details). There is no need to include the technical module name in the description Related to Rule: 5.02-01 Naming Convention Best Practice article: Naming Convention Questions on this topic? See 5.01-01 Naming…
-
5.02-01 Naming Convention
Use "friendly" names for user facing processes. For data hubs or administrative processes use numeric prefixes to signify the order of the processes Related to Rule: 5.01-01 Naming Convention Best Practice article: Naming Convention Questions on this topic? See 5.02-01 Naming Convention in our Planual forum.
-
5.03-01 Remove unwanted sources
For one off imports, or when source models are no longer required, delete the source model to keep the list tidy Questions on this topic? See 5.03-01 Remove unwanted sources in our Planual forum.
-
5.04-01 From source system, create a code defining all attributes
Ideally, this would be a separate file that is unique vs. using the same file for the transactional load Exception: 5.04-01a Code is >60 characters: If the code is >60 characters, you will have to use combination of properties Related to Rule: 5.04-02 Create separate files for attributes and data Best Practice article:…
-
5.05-01 Naming Convention
Keep it simple. Export, Build etc. There is no need to include the module name in the view name Best Practice article: Naming Convention Questions on this topic? See 5.05-01 Naming Convention in our Planual forum.
-
5.06-01 Naming Convention
Rename the import sources as soon as possible. For a saved view include the module name (e.g. module.saved view). For model imports, include a shorted version of the model name (e.g. model_module.saved view) Best Practice article: Naming Convention Questions on this topic? See 5.06-01 Naming Convention in our Planual forum.
-
5.07-01 No Hierarchies
There should be no need for composite list hierarchies in the Hub. They can be built to "test" the actions, but after testing they should be deleted Exceptions: 5.07-01a Validation purposes: If data is needed to be consolidated to check against source systems, although the flat modules with attributes can be used to sum…
-
5.01-02 User Facing Actions in a process
Import and Export actions need to be republished if modified or replaced, whereas Process Actions are always consistent with whatever is held within the Process, making management easier Exception: 5.01-02a Numbered list actions: Actions involving numbered lists (Create, Assign, Copy Branch and Delete Branch) cannot be…
-
5.02-02 Keep actions in a process to a minimum
Each action in a process triggers a recalculation so try and minimize the number of actions Questions on this topic? See 5.02-02 Keep actions in a process to a minimum in our Planual forum.
-
5.04-02 Create separate files for attributes and data
The data file should have the key and values based on the dimensions. Non dimensional data should be in a different file Related to Rule: 5.04-01 From source system, create a code defining all attributes Best Practice article: Data Hubs: Purpose and Peak Performance Questions on this topic? See 5.04-02 Create separate…
