6.2 Interface golden rules

#1 if there was an error yesterday in interface, we need to check that specific macro first thing in the morning

#2 NEVER do any technical modification (modify a Macro, scenario, query) while ‘dynasys_tech’ is performing the batchs (Import -Static or dynamic- or Export - Export DR-). However, it’s possible to do technical modifications when no batch is running, we are not blocked by users.

#3 NEVER do any modelling action/modification (add a datafield, condition, open master tables, open workspaces) while ‘dynasys_tech’ is performing the batchs (Import -Static or dynamic- or Export - Export DR-)

#4 When ‘dynasys_tech’ is performing exports (Export DR), it’s possible to work in the system, open workspaces, datafields etc BUT NOT POSSIBLE to do any technical/modelling modification or open any Export datafield (U99 - Export - OUT)

#5 If the error in Static is high impact & users not connected yet -> you lock connections after static, wait for Exports to be done, run manually the parts missing, and unlock connections (In DP1, not possible to launch static because it takes 3h)

If error is low impact & duration less that 10’ -> you wait after exports and if no users, you run manually the diff parts Our case is low impact

#6 When using a ‘TMP’ scenario, need to check the next day that no error in the Static + comment again the line

#7 Always try to use an existing query (specially if the file is already existing => surely we will already have a query). Same for scenario 

 #8 Information to request when asked to do a new scenario:
Source (BW file / DiP / DP?), Target (Master table / Datafield), Frequency (Daily / Weekly)
Then need to try to use existing scenario/query